@jeshab
I want to provide you with some feedback for the Insteon Binding ahead of the OH 5.0 release. Over the past two days I have spent some time using the latest Docker OH 5.0-snapshot and evaluating the Insteon Binding. Using an FT232 Serial (UART) to USB cable I connected my PLM to the server running OH 5. The PLM was recognized without issue and I was able to download the database and all of my devices/scenes were recognized and came online. Among the devices I have are dimmers, switches, I/OLinc plugin dimmers and switches, a smoke bridge, garage door openers and sensors, and finally a thermostat. From what I could see during my use, all devices functioned as expected through OH and reported status accordingly, with one exception: the Thermostat (2441TH).
Generally I would say the thermostat was functional up to a point, but there were several very strange behaviors that I think may need some additional attention. First, when switching System Modes from the OFF state to HEAT, the command would be sent properly to the thermostat and the physical thermostat would switch modes. Then after a few seconds for no apparent reason the linked Item would be UPDATED to AUTO, but the physical thermostat would not change modes, remaining in HEAT mode. That is the reason I say it was an UPDATE and NOT a command. Similarly when switching the System Mode from OFF to COOL, the command would be sent to the thermostat, the physical thermostat would switch to COOL as expected, then a few seconds later the Linked Item would UPDATE to HEAT for no apparent reason, but the physical thermostat remained in COOL mode. Further adding to the confusion, if I were to switch modes from COOL to HEAT or HEAT to COOL, or AUTO without using OFF, no random UPDATES to the Linked Item were observed. Setting the Linked Item to OFF did exactly what is expected without any issue. The Linked Item UPDATE only occurred going from the OFF state to some active HVAC MODE. FWIW I have a TRACE log that I have attached, but I didnāt see anything obvious. Then again I donāt l know exactly what to look for.
The other odd behavior I noted was the temperature reporting. For most of the time I was using the binding, the Temperature reporting/display on OH and the Thermostat were in sync and accurate. However yesterday, suddenly the OH Temperature Item was seeing a temperature of 33°F while the thermostat was showing 76°F. As you might expect all sort of low temperature alarms/rules were triggered but nothing I tried was able to reset the OH display.
Just by way of background, I am running OH 5.0-snapshot #4716 in a fresh docker container. My baseline system federates OH 3 docker with OH 4.x ( now 5.0-snapshot)docker using the excellent Remote OpenHAB Binding. The OH3 Docker is running the ISY Binding 3.0.1 which bridges to a Universal Devices ISY994i/PLM that controls my Insteon devices. This setup is very stable and works well, but is aging and I am concerned that it may soon give out. That is my primary motivation for wanting to switch to the OH Insteon Binding. (N.B. During my evaluation of the Insteon Binding, Remote OpenHAB was disabled and OH3 Docker stopped. I was running/evaluating OH 5.0 solo.) However, without a functional/stable thermostat implementation I am unwilling to commit and have reverted to my baseline setup and all is running fine.
I do believe the Insteon Binding 5.0 is likely very close to perfection, but still needs some tweaking to realize the full potential. This is reason I am doing my best to document my observations, in the hope that you may be able to make the needed adjustments ahead of OH 5.0 GA. Thanks again for your efforts.
Insteon Thermostat Trace.txt (8.7 KB)