Hopping from one problem to another, I recently setup my Fhem-Server which controls my Cinema-Light in my room. I created a notify in the Fhem Controlcenter, which automatically detects KODI commands such as ‘play’ ‘pause’ and ‘stop’. This gives me some very convenient and cool experience on filmstart and at the end of any movie, or during a short break.
Altough, the Vero loses connection continuously and everytime the device reappears in the Fhem-Server, it turns on the lights. That should not happen since i dont want to have lights turned on every 2 min…
Has anyone an idea why this could happen? It seems the device loses websocket connection.
On my RPi Libreelec builds on Kodi V17 this wasn´t a problem at all. Fhem-Log says ‘lost connection to KODI device for 120 sec’, after that the Vero appears again and it says ‘lost connection to KODI device for 120 sec’ again, and so on and on… This happens as long as I connect the Vero4K to the Fhem-Server.
What makes you sure of this if Chorus and Kodi’s JSON-RPC is working OK?
Unfortunately I don’t know anything about this, so it may be hard to track down here. I assume Pi and Vero 4K are both connected in the same way to the network (wired) and running the exact same version of OSMC and Kodi?
Trying OSMC on RPi soon, then we can compare things. Not saying its completely broken since Yatse and Chorus are working fine.
Also asking in the Fhem-forum, maybe someone knows if there was a change in server settings…
Just tested Chorus again, NOT working as expected, seems it loses connection too. I started playing a file, then paused the video. As I wanted to continue, the unpause button didn´t work anymore.
Is there a proper way to find out if Chorus works?