Once the IP address is retrieved, a telnet connection to port 1255 can be opened to access the HEOS CLI and control the HEOS system. Through discovery, the IP address of the HEOS products can be retrieved. The HEOS products can be discovered using the UPnP SSDP protocol. The commands and responses for browsing music servers and services use a RESTFUL like approach while other commands and responses are more static. The command is a text string and the responses are in JSON format. The CLI commands and responses are in human readable (ascii) format. The Command Line Interface (CLI) protocol, which allowes external seystem to control systems to manage, browse, play, and get status from the Denon HEOS products. The control system sends commands and receives responses over the this speaker has also an USB and analog aux input and the app can connect to several online stations, like Spotify, TuneIn, Soundcloud as well to a local network music server, etc.Ĭontrolling the music via the app is nice, but we want to check and control what is going on, from our home automation system. I started with the HEOS 3 HS2, which should for for smaller and medium sized rooms.Īfter 2 weeks of owning this speaker, I’m very positive of it and didn’t expect the high quality of played music, from severa sources. Most people in my neighourhood do have Sonos all around the house, but for multiple purpose solutions, Sonos is not the best option for me, therefor I did a lot of comparisons and HEOS had a match.īecause I’d never experience with a wireless speaker for longer than a few listening minutes, I didn’t know when size of speaker the best choice was. I barely used it the last years and the WAF for all the external speaker is below zero… Wireless speakers like Sonos are booming and other manufactures want to join the ride as well. The oversized audio/video receiver Pioneer VSX-922 with 6 surround speakers is too much. The station ultimately plays but I thought I would report the errors in case there is something that I'm not doing correctly:įeb-02 8:24:46 AM Sonos Error Type = Learnedįeb-02 8:24:46 AM Sonos Error MetaData = 181.FM Lite 80'_RINCONXXXXX_įeb-02 8:24:46 AM Sonos Error URI = x-sonosapi-stream:s90410?sid=254&flags=8224&sn=0įeb-02 8:24:46 AM Sonos Error Name = Learned - 181.FM Lite 80'sįeb-02 8:24:46 AM Sonos Error UpdateRadioStationsInfo unable write this record for zoneplayer = Family Room with error - database is locked database is lockedįeb-02 8:24:16 AM Sonos Error Type = Learnedįeb-02 8:24:16 AM Sonos Error MetaData = 181.FM Lite 80'_RINCONXXXXX_įeb-02 8:24:16 AM Sonos Error URI = x-sonosapi-stream:s90410?sid=254&flags=8224&sn=0įeb-02 8:24:16 AM Sonos Error Name = Learned - 181.FM Lite 80'sįeb-02 8:24:16 AM Sonos Error UpdateRadioStationsInfo unable write this record for zoneplayer = Family Room with error - database is locked database is lockedįeb-02 8:23:46 AM Sonos Error Type = Learnedįeb-02 8:23:46 AM Sonos Error MetaData = 181.FM Lite 80'_RINCONXXXXX_įeb-02 8:23:46 AM Sonos Error URI = x-sonosapi-stream:s90410?sid=254&flags=8224&sn=0įeb-02 8:23:46 AM Sonos Error Name = Learned - 181.FM Lite 80'sįeb-02 8:23:46 AM Sonos Error UpdateRadioStationsInfo unable write this record for zoneplayer = Family Room with error - database is locked database is lockedįeb-02 8:23:16 AM Sonos Error Type = Learnedįeb-02 8:23:16 AM Sonos Error MetaData = 181.FM Lite 80'_RINCONXXXXX_įeb-02 8:23:16 AM Sonos Error URI = x-sonosapi-stream:s90410?sid=254&flags=8224&sn=0įeb-02 8:23:16 AM Sonos Error Name = Learned - 181.A new house, a new setup of almost everything. I have an event that plays one of the learned stations from the DB but for some reason, every time it's triggered I get the below errors in the HS log. If it is the right event, check the settings on the speaker client itself like voice used, output used etc.ĭirkHey Dirk! Hope everything with you is going well! Possible?Ĭlear the log on the speakerclient, activate the event you posted, does it cause an error? The text in the event in the error seems different as well. So the error in the speaker client, at first glance, I would think is coming from another event. Are you sure the error in the speaker client is related to the events you are showing? With the setup you show, the PI calls a SpeakToFile component which I learned not that long ago, is actually NOT going to the speakclient anymore (maybe never did ).