Your comments

Actually, i just saw it is a combined command. Look at the Specification below. The packet gives you 6 bytes. First is the channel number, second is the temperature in the "old" format. And additionally there are the 4 Bytes of the "new" temperatur float format.



I don't know if every device is sending out all the 6 bytes or some are just sending 2 bytes, but all the one's i'am testing here are doing 6 bytes.

Alexa Support for i3 pro server ??? People are asking, whats your current status?

hi, so tested your special version. is it working? yes and no.


broadcast temperatur receive is working, but only when you set the temperatur feedback channel to "read temperatur". it is not working when you set it to "read temperatur new". but when other devices on the bus doing also temperature requests, they mostly use the "read temperature new" method, also thats the standard format in iridium too. so, in my opinion there are two practical solutions:


1.) the "temperature broadcast" should always update the corresponding temperature channel of the device regardless of which method is selected "old" or "new". "temperature broadcast" messages (today) are always using the "old" temperature read format.


2.) maybe a better solution would be to not give the two options "read temperature" and "read temperature new" to be selectable, just make it "temperature response". and it should receive the "old" and the "new" temperature format and also the broadcast format too. because it doesn't make a difference in the result for the enduser. we just want the temperature.


for testing a server version, please send me a raspberry version. but i think you're doing it right.


thx!


hi, so this is the windows client right? would need it for the server too. thx.

thx, please include also the wireless devices in the hdl device list. like the 1 channel curtain module with 4 additional dry-contact inputs, or the 1 channel and 2 channel relais module.

also a temperature broadcast code E3E5 is not recognized. :-(

kind of same problem when using 1.1.8 client with 1.1.7 server. feedbacktags are only updated on the client when the client starts or a panel came back from sleep mode. but the values don't change when they changed on the server!