Domoticz

Don't know if this is the correct sub-forum.
I've just updated to Domoticz V 3.6033.

This message used to appear just once at startup - now it is appearing every few minutes -

OpenZWave: Value_Added: Node: 15 (0x0f), CommandClass: THERMOSTAT OPERATING STATE, Label: Operating State, Instance: 1
OpenZWave: Unhandled class: 0x42 (THERMOSTAT OPERATING STATE), NodeID: 15 (0x0f), Index: 0, Instance: 1

same here
OpenZWave: Value_Added: Node: 44 (0x2c), CommandClass: CLIMATE CONTROL SCHEDULE, Label: Override State, Instance: 1
OpenZWave: Value_Added: Node: 44 (0x2c), CommandClass: CLIMATE CONTROL SCHEDULE, Label: Override Setback, Instance: 1

mine is a: Danfoss Z Thermostat 014G0013 Danfoss 0x0004 0x0005

+1, noticed this. Not a big deal, though.

It has become a larger deal for me, now.
If I follow the log in the GUI, and select the Status tab, nearly half of the entries are now "OpenZWave: Unhandled class: 0x42 ..."

Westcott wrote:It has become a larger deal for me, now.
If I follow the log in the GUI, and select the Status tab, nearly half of the entries are now "OpenZWave: Unhandled class: 0x42 ..."

Strange, no such entries here.

For me as well but with a weather station part

2016-12-19 10:52:24.005 OpenZWave: Value_Added: Node: 52 (0x34), CommandClass: SENSOR MULTILEVEL, Label: Direction, Instance: 7
2016-12-19 10:52:24.005 OpenZWave: Value_Added: Unhandled Label: Direction, Unit:

Jan

Just an idea: what happens if you remove the ozw_cfg xml? Obviously you lost all your OZW related settings, but maybe... Just a maybe: it will fix this issue.

Is this about Danfoss thermostats?
This is fixed in version 61xx, update to latest beta will probably solve it.
Instead of removing the entire ozw_cfg xml you can also edit it and just remove everything from that one node. That way you don't loose the rest.

Hi Egregius,
My original post was about Horstmann/Secure SCSC17 thermostats, although I didn't mention the exact type at the time.
I'm now on V 3.6207.
If the file is called 'ozw_cfg xml' then I definitely don't have one.

the name is something like zwcfg_0x0184e727.xml
I copy/pasted from the previous response, sorry.

Thanks!
Yes, the offending part of the config must be this -

<CommandClass id="66" name="COMMAND_CLASS_THERMOSTAT_OPERATING_STATE" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="string" genre="user" instance="1" index="0" label="Operating State" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="Idle" />
</CommandClass>

Is the suggestion just to remove this bit?
Stop Domotics - edit cfg file - restart Domoticz?

So I removed that bit, and it's OK now!
Egregius, thanks for the pointer.
Also took the opportunity to remove some bad COMMAND_CLASS_SENSOR_MULTILEVEL entries from the Fibaro FGMS001 entries

In my case this bug was more serious

I have 2 Stelpro Ki STZW402+ Zwave Baseboard Line Voltage Thermostat
(integration worked fine to add in domoticZ in a rasberrypi3b and AeotecZwave USB ZStick Gen 5 )

And after about 24 to 48 hours running on schedule build with blocky in Domoticz I got both crashing
Yes , the thermostat crash , The LCD is unresponsive and all lcd segment are lit.
The thermostat still follow the setpoint, it still drive the baseboard heater, and is still having apropriate behaviour on the Domotic Z web page , but is locally unresponsive.
They needed a hard breaker reboot to come back normal

Looking into the domoticz log , I can see alot of
2020-03-04 19:13:04.027 Status: OpenZWave: Unhandled class: 0x42 (THERMOSTAT OPERATING STATE), NodeID: 6 (0x06), Index: 0, Instance: 1

So I did Remove the folowing section :

<CommandClass id="66" name="COMMAND_CLASS_THERMOSTAT_OPERATING_STATE" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="string" genre="user" instance="1" index="0" label="Operating State" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity=$
</CommandClass>

In the /home/pi/domoticz/Config/zwcfg_0xd839c72c.xml file for only one thermostat
It stop crashing

And did for both thermostat in the config File
And they both stop crashing