The starting sequence for the affected activity sends a IR Power Toggle to the VU+ Box to wake it from deep sleep. After this, a http get command will be send with a discrete power on command (if the box was in normal standby before activity start already the first IR command Toggle would have send it to standby).
If the box was in normal standby mode already and is reachable in the network everything works fine and the sequence works 'til the end as it should be. But if the box was in deep standby and is not reachable in the network (due to itās longer booting time of 45 seconds) the http command gives a timeout error and the starting sequence aborts with error. I have to wait then til the box finished booting and start the start sequence from beginning again.
What I really donāt understand and what should be changes in future updates is the fact that the integration is waiting for network response from the box even if I turned on the āfire and forgetā function. Other devices that are able to send http commands donāt show this behaviour.
Ok, now I can see what happened here. The internal server error is actually a request timeout (408) from the receiver.
Since your receiver didnāt responded within the set timeout of 10 seconds while booting a timeout error was sent to the remote. The Fire and Forget mode still needs to reach the device to fire the command. It just doesnāt wait for a response or ignores it. The mode is intended for devices that donāt send a response or terminate the connection after they received a command.
But I released a new version that includes timeouts in fire and forget mode and also should solve the websockets disconnects because of a failed websockets heartbeat.
I had time today to check āText over TCPā and it worked on first tryš I can control my old Epson TV7300 projector with this option. I added power on/off but I am sure that I could add all other commands if needed.
Here is the power on command if anyone else has an Epson projector ā192.168.178.66:4352,ā%1POWR 1\r"" 192.168.178.66 is the IP of my projector, 4352 is the default port and ā%1POWR 1\rā is the command. As the Epson supports the PJLink protocol it should also work with several other brands.
New release with support for custom entities. More details in the redme file. If you have configurations that could be integrated into a future version that adds profiles please send them to me
Sorry to revive this old thread, but Iām having trouble configuring this integration (v0.8.7). I canāt complete any of the setup actions. No matter what option I select (Configure advanced settings, Configure custom entities, Finish setup), I get an error āDriver not connected. Failed to connect to host: Connection refused (os error 111)ā. Iāve tried re-installing and rebooting with the same results.
Iām brand new to the UC system, trying to program the Remote 3 for the first time. Perhaps there is some dependency that I havenāt installed, but I donāt see anything like that in the instructions. Any ideas?
Thanks Kenny. Iāve deleted and reinstalled it, but get the same result. Iāve tried this a few times. Iām curious about the instruction to delete the integration twice. It disappears when I delete it once, so Iām not sure how to delete it twice. Is there some specific method for deleting it twice?
Yes. I just did it again. Deleted the integration. Rebooted. Reinstalled. Then same result. There doesnāt seem to be much to troubleshoot with, but it might just be may lack of familiarity with the UC system. Is there a log somewhere?
Which firmware have you installed? There was an issue with copying additional files from custom integrations that was solved with 2.6.9 so you need to be at least on this firmware as I removed the workaround in newer versions of the integration.
Looks like that was it! I was on 2.6.1, and the configurator said it was up to date. Once I checked āauto updateā, it loaded 2.6.12. After a reboot, it looks like Iām in. Thanks for your help!