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!
hopefully someone can give me some hints, how can i build custom entities with this http get integration V0.8.8 on remote 3, as iâm currently run ito problems. Installation of the integration was successful, and i build my first Entity1 to switch my Shellyâs in the network with this content:
Now Entity2 works great, but Entity1 is no longer reachable. The remote says âRessource not foundâ and in the log you can read âWARNING Cannot execute command âonâ for âremote-custom-entity1â: no configured entity foundâ. When i now add a third Entity, then the third Entity works great, but Entity1+2 are no longer reachable and so on, means, only the last createt Entity works, all others are not reachable. If i reboot the remote, the icons of the Entities get a red backslash and are marked as ânot reachableâ. Iâve also deleted the integration twice and build everything new but without success.
The only difference i can see is, that the timestamp in the log is one our behind (summertime) my system time, even i have choosen the right time Zone in remote 3 setup. Any idea what i have missed ore make wrong?
I canât reproduce this. Please post the complete log from starting the integration for the first time until you get the error. Also make sure that both enities are added to the configured entities list in the integration settings.
Timestamps in the log are always GMT so it might be diferent from you local timezone.
Thank you Kenny for your fast response and for looking at this behviour.
Iâve started today from scratch, so you see in the log file at first adding the integration, then configurating the integration (fire&forget) and then adding Entity1, switching Entity1 on/off (works), adding Entity2, switching Entity2 on/off (works), try to switch Entity1 again (wonât work anymore), adding Entity3, switching Entinity3 on/off (works), try to switch Entity2 again (wonât work anymore), try to switch Entity1 again (wonât work anymore). After restart of the remote Entity1,2 are not found, Entity3 works as befor as last added Entity. I use UC System Version 2.7.0.
Thanks for the log. You are replacing the entity with the new entity instead of adding it to the config. That will remove the old entity and the old entity will be shown as unavailable after a restart (2025-11-10 22:02:13.844895 +00:00 custom-intg-requests INFO setup INFO One or more entities have been removed from the custom entities configuration. Removing them as available and configured entity)
thank you for the hint. Now I understand that all HTTP commands must be entered together and not individually, as I had previously thought. Now it works perfectly. Thanks again for your support!
