Hi Kenny,
I hd the chnce to play around again and get some error logs: 2024-10-19 09:20:52.597506 +00:00 core NOTICE Setting button backlight to: 0%2 - Pastebin.com
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.
Thank you very much in advance for your help.
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.
Great! Works now without errors or problems. Thank you very much for the quick release of the adopted version!
The latest 0.6.0 release includes some breaking changes if you have added additional payload data before:
1 Like
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.
perhaps it helps other people.
Ralf
1 Like