Insteon Bindings: a couple of issues

Hi,

I am in the process of migrating from OH 2 to OH 3.2.0 (with Zulu OpenJDK Runtime 11.54+23) on a Windows 10 platform.

I would very much like to get some help with the following two problems I am experiencing in OH 3.2.0.

  1. my Insteon 2441TH thermostat is currently set to use the Celsius temperature scale. In my OH interface I do use Celsius degrees to determine the temperature setpoint and this turns out to works OK (the set temperature is correctly received by the thermostat). However, regarding the current temperature observed by the thermostat, OH is receiving the corresponding number in Farenheit degrees. I am making available an OH log with the insteon binding set to DEBUG. In there you can identify particular references to the thermostat using the identifier “32F555”.

  2. whenever I set a dim level using an OH slider, the slider will first move to the point I indicated; then after a couple of seconds, it moves to 100%; and after a few more seconds it moves back to the point I had set it. In my log, you can see an example of that concerning dimmer “259705” starting at time 16:21.14.031.

The log can be accessed on Google drive at the following address:

https://drive.google.com/file/d/1SSkIhf6c6g25vqa-XsmMDi7L82RzvMLd/view?usp=sharing

Thanks in advance for your help.

Yes, internally the Insteon binding is using Fahrenheit, OH will convert it into Celsius for you. If you are looking at debug logs, you will need to manually convert it yourself.

What do you see in the events.log when this occurs? Here’s what I see when I tried it with one of my dimmers:

2022-02-04 07:45:02.103 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'mDiningLights' received command 43.0
2022-02-04 07:45:02.180 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'mDiningLights' predicted to become 43.0
2022-02-04 07:45:02.253 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'mDiningLights' changed from 0 to 43.0
2022-02-04 07:45:06.993 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'mDiningLights' received command 0.0
2022-02-04 07:45:07.007 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'mDiningLights' predicted to become 0.0
2022-02-04 07:45:07.040 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'mDiningLights' changed from 43 to 0.0

Thanks a lot for your response.

OK, I will see how I can effect the conversion from Farenheit to Celsius within OH.

As for the event log, I am attaching the relevant portion below. As you can see, it looks as if, a moment after I issued my command to set the level to 47, additional commands to set the level first to 100 and then back to 47 are being issued somehow. This is exactly what I am observing on my sitemap interface. Puzzling, isn’t it?
The posterior command to set the level to 0 at 16:21:24.044 was manually issued by me, but the previous two (set to 100 and then back to 47) weren’t.

022-02-03 16:21:11.270 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Absent' received command OFF
2022-02-03 16:21:14.031 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'lampe_salle_a_manger' received command 47
2022-02-03 16:21:14.032 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'lampe_salle_a_manger' predicted to become 47
2022-02-03 16:21:14.035 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'lampe_salle_a_manger' changed from 0 to 47
2022-02-03 16:21:15.642 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'paradoxalarm:panel:ip150:panel' changed from UNKNOWN to ONLINE
2022-02-03 16:21:15.657 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'paradoxalarm:partition:ip150:partition1' changed from UNKNOWN to ONLINE
2022-02-03 16:21:15.659 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'paradoxalarm:zone:ip150:ThermiqueGarage' changed from UNKNOWN to ONLINE
2022-02-03 16:21:15.660 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'paradoxalarm:zone:ip150:Fumee' changed from UNKNOWN to ONLINE
2022-02-03 16:21:15.672 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'paradoxalarm:zone:ip150:PortePatioGauche' changed from UNKNOWN to ONLINE
2022-02-03 16:21:15.674 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'paradoxalarm:zone:ip150:MouvementBureau' changed from UNKNOWN to ONLINE
2022-02-03 16:21:15.675 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'paradoxalarm:zone:ip150:MouvementSalon' changed from UNKNOWN to ONLINE
2022-02-03 16:21:15.676 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'paradoxalarm:zone:ip150:PortePatioDroite' changed from UNKNOWN to ONLINE
2022-02-03 16:21:15.677 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'paradoxalarm:zone:ip150:MouvementCinema' changed from UNKNOWN to ONLINE
2022-02-03 16:21:15.688 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'paradoxalarm:zone:ip150:MouvementChambreMaitres' changed from UNKNOWN to ONLINE
2022-02-03 16:21:15.689 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'paradoxalarm:zone:ip150:MouvementCuisine' changed from UNKNOWN to ONLINE
2022-02-03 16:21:15.690 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'paradoxalarm:zone:ip150:MouvementGarage' changed from UNKNOWN to ONLINE
2022-02-03 16:21:15.817 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'lampe_salle_a_manger' changed from 47 to 100
2022-02-03 16:21:21.935 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'lampe_salle_a_manger' changed from 100 to 47
2022-02-03 16:21:24.044 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'lampe_salle_a_manger' received command 0
2022-02-03 16:21:24.045 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'lampe_salle_a_manger' predicted to become 0
2022-02-03 16:21:24.069 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'lampe_salle_a_manger' changed from 47 to 0
2022-02-03 16:22:00.946 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ESP_Easy1_ac_vane' changed from NULL to SWING

If you look just at that item:

2022-02-03 16:21:14.031 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'lampe_salle_a_manger' received command 47
2022-02-03 16:21:14.032 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'lampe_salle_a_manger' predicted to become 47
2022-02-03 16:21:14.035 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'lampe_salle_a_manger' changed from 0 to 47
2022-02-03 16:21:15.817 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'lampe_salle_a_manger' changed from 47 to 100
2022-02-03 16:21:21.935 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'lampe_salle_a_manger' changed from 100 to 47
2022-02-03 16:21:24.044 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'lampe_salle_a_manger' received command 0
2022-02-03 16:21:24.045 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'lampe_salle_a_manger' predicted to become 0
2022-02-03 16:21:24.069 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'lampe_salle_a_manger' changed from 47 to 0

There is a 1.782 second gap between 47->100 and 6.118 second gap between 100->47 that was reported by the device back to the Insteon binding. Looks like something external to the binding is changing the values. Are you using anything besides OH to control the device?

I have been using Google Assistant with OH 2, but in my current version of OH 3 it cannot be used yet since I have not installed the OH cloud facility yet. I don’t see where those extra commands can come from. :frowning:

Thinking again about this strange problem, I realize that it might well result from a bug in my new hub. You may remember that I had to change my hub just a few weeks ago. Although I did not realize it immediately, I think the problem probably started immediately when I turned on the new hub. It happens with all my Switchlinc dimmers (2477D) but not with my Lamplinc dimmers. I wonder if doing a factory reset on the Hub could resolve the issue?
One problem I have with this theory of a hub-internal issue is that all lights are behaving normally when operated using the Insteon app rather than through OH.

It’s hard to say, its just weird that there is such a large delay between the values changing.