[XTension] XT and Hubitat (C-8) - units get out of sync

[james at sentman.com]

I definitely see some of my units that display an incorrect value after being controlled. For me I THINK it’s limited to some ZWave 1 devices I have and a couple of ZWave 2 capable ones that are off brands or the first generation of that and probably need a firmware update or something.

In my case though just because the device is in the database at the wrong value, sending it a command does still work. In XTension the commands will be sent to the plugin regardless of the state so I’m fairly sure that this is not a problem in XTension itself, but it is still possible. The communications going the other way are different and if the Hubitat sends a value to a Unit and it’s the same value as what XTension thinks the unit is then it will not run the Unit scripts as it thinks it’s just an update.

To test to see if you’re seeing the same issue that I do sometimes rather than something new please do this for me:

At some point walk through your list of hubitat units and if you can find one that is out of sync, please issue it a query command. You can do that from the command line in XTension or just by control clicking on it in the list and selecting “send query” from the contextual menu. Does it then update with the correct value? Or does it continue to display the incorrect value?

For some of mine that are particularly troublesome I added in a doLater command that just calls back to a handler that does nothing but a query about 5 minutes after the on or off script is run. This has 100% cleared up the issue for me and I’m going to build that into the plugin itself at some later date. It already does this in some circumstances, but I think that the range of circumstaces needs to be larger and the length of time it waits to do it needs to be longer as the 5 minutes seems to work well for me and the plugin does it only a few seconds later at this moment. I have not experimented to see what the proper time frame is for this, but you can temporarily implement this if the query causes the value to update properly.

If the query doesn’t cause it to then be in sync something even more interesting is happening, and it never pays to be that interesting...



> On Mar 30, 2023, at 11:39 AM, Brian Williams <brwill at me.com> wrote:
> 
> One of the issues that is frustrating me is that I can issue an OFF command for a lamp that I can see as being on, and nothing happens, because either XT or Hubitat believes that the unit is already off. The same in reverse where an ON command goes nowhere because either HT or Hubitat believe the unit to already be on (not just dimmed). I don't recall this disconnect between Vera and XT.
> 
> I have read that it can take a few weeks for Hubitat to 'settle down.'
> 
> I am wondering if others have a similar experience, or knowledge of it, and also if a solution is known, other than scripting every device's On script with Brighten to 100, and every Off script to Dim to 0.

Thanks,
 James


James Sentman                       http://www.PlanetaryGear.org		http://MacHomeAutomation.com



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://machomeautomation.com/pipermail/xtensionlist_machomeautomation.com/attachments/20230407/d9195883/attachment.htm>