Justin Hammond

@Ittiz I have no idea how domoticz works in this case. Maybe @petergebruers can chime in, otherwise log files are needed.

@RicardP As mentioned its a known issue and its been worked on in Dev branch. No ETA when I'll have the fix as its rather intrusive change.

@petergebruers looking at the log files, we are getting METER reports in before the interview process for the METER Class completes (in particular the Version Check). The Meter Class is...

I think in this case, it’s writing out a bogus Value to the config file in addition to the “valid” data and this getting confused. Hence why a restart is...

@gizmocuz each individual devices "interview" stage is represented by the QueryStage. Do you display that at all? That can sometimes help determine which device may still be sleeping/dead or stuck...

No. I’m talking about this method: http://openzwave.com/dev/classOpenZWave_1_1Manager.html#a30fd64eb8fa178c24a7dc7c2d4d3714f

Logs?

Another Buggy Implementation: ``` 2020-03-13 08:26:35.635 Info, Node017, UPDATE_STATE_NODE_INFO_RECEIVED from node 17 2020-03-13 08:26:35.635 Info, Node017, Optional CommandClasses for node 17: 2020-03-13 08:26:35.635 Info, Node017, COMMAND_CLASS_ZWAVEPLUS_INFO 2020-03-13 08:26:35.635 Info, Node017,...

Try this: https://github.com/OpenZWave/open-zwave/blob/d8fddb47b3ac12f495101691a42ff38f3b61f296/cpp/src/Group.cpp#L252 Add the following lines after that log message: ``` cc->Set(m_groupIdx, _nodeId, 0); cc->QueryGroup(m_groupIdx, 0); return; ```

Yes - I dont own these devices so someone needs to debug. You need to make the changes and recompile.