ThermoFloor HEATIT Z-TEMP2 - Error getting configurationCommandClass

frnck · January 10, 2023, 4:27pm

Updating the (thing) configuration using openHAB 3.4.0 fails.
It seems that changing any value fails.

2023-01-10 17:27:33.942 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update received
2023-01-10 17:27:33.944 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored config_10_1 to 5 (BigDecimal)
2023-01-10 17:27:33.945 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored group_1 to [controller] (ArrayList)
2023-01-10 17:27:33.945 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored group_3 to [node_3, node_5] (ArrayList)
2023-01-10 17:27:33.945 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored group_2 to [] (EmptyList)
2023-01-10 17:27:33.946 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored config_1_1 to 644 (BigDecimal)
2023-01-10 17:27:33.946 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored config_6_2 to 10 (BigDecimal)
2023-01-10 17:27:33.946 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update set config_7_1 to 0 (BigDecimal)
2023-01-10 17:27:33.946 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Error getting configurationCommandClass
2023-01-10 17:27:33.946 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored config_8_1 to 50 (BigDecimal)
2023-01-10 17:27:33.946 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored config_12_2 to 5 (BigDecimal)
2023-01-10 17:27:33.946 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored config_11_2 to 50 (BigDecimal)
2023-01-10 17:27:33.947 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored config_9_2 to 3 (BigDecimal)
2023-01-10 17:27:33.947 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored config_2_2 to 10 (BigDecimal)
2023-01-10 17:27:33.947 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored config_3_2 to 10 (BigDecimal)
2023-01-10 17:27:33.947 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored config_13_2 to 0 (BigDecimal)
2023-01-10 17:27:33.947 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored config_14_1 to 0 (BigDecimal)
2023-01-10 17:27:33.947 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored config_4_2 to 0 (BigDecimal)
2023-01-10 17:27:33.947 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored config_5_2 to 0 (BigDecimal)
2023-01-10 17:27:33.948 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update ignored node_id to 6 (BigDecimal)

A snippet from the configuration:

And because I am not allowed to upload a file, this is the full xml in /var/lib/openhab/zwave/…

<node>
  <homeId>0xf3bf0e49</homeId>
  <nodeId>6</nodeId>
  <version>4</version>
  <manufacturer>0x19b</manufacturer>
  <deviceId>0x204</deviceId>
  <deviceType>0x4</deviceType>
  <listening>false</listening>
  <frequentlyListening>true</frequentlyListening>
  <routing>true</routing>
  <security>false</security>
  <beaming>true</beaming>
  <maxBaudRate>40000</maxBaudRate>
  <sleepDelay>500</sleepDelay>
  <nodeInformationFrame>
    <commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
    <commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
    <commandClass>COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION</commandClass>
    <commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
    <commandClass>COMMAND_CLASS_TRANSPORT_SERVICE</commandClass>
    <commandClass>COMMAND_CLASS_VERSION</commandClass>
    <commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
    <commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
    <commandClass>COMMAND_CLASS_INDICATOR</commandClass>
    <commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
    <commandClass>COMMAND_CLASS_BATTERY</commandClass>
    <commandClass>COMMAND_CLASS_SECURITY</commandClass>
    <commandClass>COMMAND_CLASS_SECURITY_2</commandClass>
    <commandClass>COMMAND_CLASS_ALARM</commandClass>
    <commandClass>COMMAND_CLASS_SUPERVISION</commandClass>
    <commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>
    <commandClass>COMMAND_CLASS_THERMOSTAT_MODE</commandClass>
    <commandClass>COMMAND_CLASS_THERMOSTAT_SETPOINT</commandClass>
    <commandClass>COMMAND_CLASS_THERMOSTAT_OPERATING_STATE</commandClass>
    <commandClass>COMMAND_CLASS_PROTECTION</commandClass>
  </nodeInformationFrame>
  <associationGroups class="concurrent-hash-map">
    <entry>
      <int>1</int>
      <associationGroup>
        <index>1</index>
        <maxNodes>0</maxNodes>
        <associations>
          <associationMember>
            <node>1</node>
          </associationMember>
        </associations>
      </associationGroup>
    </entry>
    <entry>
      <int>2</int>
      <associationGroup>
        <index>2</index>
        <maxNodes>0</maxNodes>
        <associations/>
      </associationGroup>
    </entry>
    <entry>
      <int>3</int>
      <associationGroup>
        <index>3</index>
        <maxNodes>0</maxNodes>
        <associations>
          <associationMember>
            <node>3</node>
          </associationMember>
          <associationMember>
            <node>5</node>
          </associationMember>
        </associations>
      </associationGroup>
    </entry>
  </associationGroups>
  <endpoints class="concurrent-hash-map">
    <entry>
      <int>0</int>
      <endPoint>
        <deviceClass>
          <basicDeviceClass>BASIC_TYPE_ROUTING_SLAVE</basicDeviceClass>
          <genericDeviceClass>GENERIC_TYPE_THERMOSTAT</genericDeviceClass>
          <specificDeviceClass>SPECIFIC_TYPE_THERMOSTAT_GENERAL_V2</specificDeviceClass>
        </deviceClass>
        <endpointId>0</endpointId>
        <secureCommandClasses/>
        <supportedCommandClasses class="concurrent-hash-map">
          <entry>
            <commandClass>COMMAND_CLASS_NO_OPERATION</commandClass>
            <COMMAND__CLASS__NO__OPERATION>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
            </COMMAND__CLASS__NO__OPERATION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_BASIC</commandClass>
            <COMMAND__CLASS__BASIC>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__BASIC>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_SENSOR_MULTILEVEL</commandClass>
            <COMMAND__CLASS__SENSOR__MULTILEVEL>
              <version>0</version>
              <instances>0</instances>
              <control>false</control>
              <versionSupported>0</versionSupported>
              <sensors>
                <entry>
                  <multilevelSensorType>TEMPERATURE</multilevelSensorType>
                  <multilevelSensor>
                    <sensorType>TEMPERATURE</sensorType>
                    <initialised>true</initialised>
                  </multilevelSensor>
                </entry>
                <entry>
                  <multilevelSensorType>RELATIVE_HUMIDITY</multilevelSensorType>
                  <multilevelSensor>
                    <sensorType>RELATIVE_HUMIDITY</sensorType>
                    <initialised>true</initialised>
                  </multilevelSensor>
                </entry>
              </sensors>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__SENSOR__MULTILEVEL>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_THERMOSTAT_MODE</commandClass>
            <COMMAND__CLASS__THERMOSTAT__MODE>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>3</versionSupported>
              <modeTypes>
                <modeType>OFF</modeType>
                <modeType>HEAT</modeType>
              </modeTypes>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__THERMOSTAT__MODE>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_THERMOSTAT_OPERATING_STATE</commandClass>
            <COMMAND__CLASS__THERMOSTAT__OPERATING__STATE>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__THERMOSTAT__OPERATING__STATE>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_THERMOSTAT_SETPOINT</commandClass>
            <COMMAND__CLASS__THERMOSTAT__SETPOINT>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>3</versionSupported>
              <setpoints>
                <entry>
                  <setpointType>HEATING</setpointType>
                  <setpoint>
                    <setpointType>HEATING</setpointType>
                    <initialised>true</initialised>
                    <initCount>0</initCount>
                    <outer-class reference="../../../.."/>
                  </setpoint>
                </entry>
              </setpoints>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__THERMOSTAT__SETPOINT>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
            <COMMAND__CLASS__ASSOCIATION__GRP__INFO>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>3</versionSupported>
              <autoSubscribeGroups/>
            </COMMAND__CLASS__ASSOCIATION__GRP__INFO>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
            <COMMAND__CLASS__DEVICE__RESET__LOCALLY>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
            </COMMAND__CLASS__DEVICE__RESET__LOCALLY>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
            <COMMAND__CLASS__ZWAVEPLUS__INFO>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <zwPlusVersion>2</zwPlusVersion>
              <zwPlusRole>ROLE_TYPE_SLAVE_SLEEPING_LISTENING</zwPlusRole>
              <zwPlusNodeType>NODE_TYPE_ZWAVEPLUS_NODE</zwPlusNodeType>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__ZWAVEPLUS__INFO>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_ALARM</commandClass>
            <COMMAND__CLASS__ALARM>
              <version>8</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>8</versionSupported>
              <alarms>
                <entry>
                  <alarmType>POWER_MANAGEMENT</alarmType>
                  <alarmState>
                    <alarmType>POWER_MANAGEMENT</alarmType>
                    <reportedEvents/>
                    <outer-class reference="../../../.."/>
                  </alarmState>
                </entry>
              </alarms>
              <v1Supported>true</v1Supported>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__ALARM>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
            <COMMAND__CLASS__MANUFACTURER__SPECIFIC>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <initSerialNumber>false</initSerialNumber>
              <deviceManufacturer>411</deviceManufacturer>
              <deviceType>4</deviceType>
              <deviceId>516</deviceId>
            </COMMAND__CLASS__MANUFACTURER__SPECIFIC>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
            <COMMAND__CLASS__POWERLEVEL>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
              <powerLevel>0</powerLevel>
              <powerTimeout>0</powerTimeout>
            </COMMAND__CLASS__POWERLEVEL>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_PROTECTION</commandClass>
            <COMMAND__CLASS__PROTECTION>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
              <localModes/>
              <rfModes/>
            </COMMAND__CLASS__PROTECTION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>
            <COMMAND__CLASS__FIRMWARE__UPDATE__MD>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>5</versionSupported>
            </COMMAND__CLASS__FIRMWARE__UPDATE__MD>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_BATTERY</commandClass>
            <COMMAND__CLASS__BATTERY>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
              <batteryLevel>100</batteryLevel>
              <batteryLow>false</batteryLow>
              <isGetSupported>true</isGetSupported>
            </COMMAND__CLASS__BATTERY>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
            <COMMAND__CLASS__ASSOCIATION>
              <version>2</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>2</versionSupported>
              <maxGroups>3</maxGroups>
            </COMMAND__CLASS__ASSOCIATION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_VERSION</commandClass>
            <COMMAND__CLASS__VERSION>
              <version>2</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>3</versionSupported>
              <libraryType>LIB_SLAVE_ENHANCED</libraryType>
              <protocolVersion>7.11</protocolVersion>
              <applicationVersion>1.2</applicationVersion>
              <hardwareVersion>1</hardwareVersion>
            </COMMAND__CLASS__VERSION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_INDICATOR</commandClass>
            <COMMAND__CLASS__INDICATOR>
              <version>3</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>3</versionSupported>
              <isGetSupported>true</isGetSupported>
              <supportedIndicatorsInitialised>true</supportedIndicatorsInitialised>
              <supportedIndicators>
                <ZWaveIndicator>
                  <type>NODE_IDENTIFY</type>
                </ZWaveIndicator>
              </supportedIndicators>
            </COMMAND__CLASS__INDICATOR>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION</commandClass>
            <COMMAND__CLASS__MULTI__CHANNEL__ASSOCIATION>
              <version>3</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>3</versionSupported>
              <maxGroups>3</maxGroups>
            </COMMAND__CLASS__MULTI__CHANNEL__ASSOCIATION>
          </entry>
          <entry>
            <commandClass>COMMAND_CLASS_SECURITY</commandClass>
            <COMMAND__CLASS__SECURITY>
              <version>1</version>
              <instances>1</instances>
              <control>false</control>
              <versionSupported>1</versionSupported>
            </COMMAND__CLASS__SECURITY>
          </entry>
        </supportedCommandClasses>
      </endPoint>
    </entry>
  </endpoints>
  <nodeNeighbors>
    <int>1</int>
    <int>3</int>
    <int>4</int>
    <int>5</int>
  </nodeNeighbors>
  <lastReceived>2023-01-10 16:24:25.121 UTC</lastReceived>
</node>

The device seems to be listed here:

with a CONFIG COMMAND which is missing locally.

anon71759204 · January 10, 2023, 5:57pm

COMMAND_CLASS_ASSOCIATON isn’t missing, but the Z-Wave Binding doesn’t configure the association groups either. IMHO a strong indication that the missing COMMAND_CLASS_CONFIGURATION isn’t the root cause.

As your device is battery operated:
Try to wake it up many times (assuming that it is not fully configured yet).

apella12 · January 10, 2023, 6:32pm

I would be a little more concerned about the missing CC Configuration in the NIF section of the XML. I believe the NIF frame from the node takes priority over what is in the DB. It could be the device needs to wake per the above post, if you do not have the five lines on the UI page
Five Lines of configured node
However, if those lines are there, then you might try to delete the thing (not exclude) then go to the inbox/zwave/scan then press the action button per an inclusion (The inclusion protocol typically send a NIF) and that may get the missing CC added. I do not think either the OH3.4 or Zwave binding is cause

frnck · January 10, 2023, 7:08pm

@apella12
This is the result after clicking on ‘Delete Thing’. It has no effect. Same error and no CONF* in xml.

2023-01-10 20:04:57.727 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 6: Serializing to file /var/lib/openhab/zwave/network_f3bf0e49__node_6.xml
2023-01-10 20:05:07.779 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery completed
2023-01-10 20:05:07.782 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery resolved to thingType zwave:thermofloor_HeatIt4512666_00_000
2023-01-10 20:05:10.555 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Controller status changed to ONLINE.
2023-01-10 20:05:10.555 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Controller is ONLINE. Starting device initialisation.
2023-01-10 20:05:10.561 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Updating node properties.
2023-01-10 20:05:10.564 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Updating node properties. MAN=411
2023-01-10 20:05:10.564 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Updating node properties. MAN=411. SET. Was 411
2023-01-10 20:05:10.564 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Properties synchronised
2023-01-10 20:05:10.569 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Update ASSOCIATION group_ZWaveAssociationGroup [index=1, name=null, profile1=null, profile2=null, associations=[node_1]]: Adding Controller (node_1)
2023-01-10 20:05:10.570 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Update ASSOCIATION group_ZWaveAssociationGroup [index=3, name=null, profile1=null, profile2=null, associations=[node_3, node_5]]: Adding node_3
2023-01-10 20:05:10.570 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Update ASSOCIATION group_ZWaveAssociationGroup [index=3, name=null, profile1=null, profile2=null, associations=[node_3, node_5]]: Adding node_5
2023-01-10 20:05:10.570 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration synchronised
2023-01-10 20:05:10.575 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising Thing Node…
2023-01-10 20:05:10.575 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:38eacc843e:node6:basic_thermostat_mode for OnOffType
2023-01-10 20:05:10.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:38eacc843e:node6:basic_thermostat_mode for OnOffType
2023-01-10 20:05:10.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:38eacc843e:node6:sensor_relhumidity for DecimalType
2023-01-10 20:05:10.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:38eacc843e:node6:sensor_relhumidity for DecimalType
2023-01-10 20:05:10.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:38eacc843e:node6:sensor_temperature for QuantityType
2023-01-10 20:05:10.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:38eacc843e:node6:sensor_temperature for QuantityType
2023-01-10 20:05:10.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:38eacc843e:node6:thermostat_mode for DecimalType
2023-01-10 20:05:10.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:38eacc843e:node6:thermostat_mode for DecimalType
2023-01-10 20:05:10.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:38eacc843e:node6:thermostat_state for DecimalType
2023-01-10 20:05:10.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:38eacc843e:node6:thermostat_state for DecimalType
2023-01-10 20:05:10.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:38eacc843e:node6:thermostat_setpoint_heating for QuantityType
2023-01-10 20:05:10.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:38eacc843e:node6:thermostat_setpoint_heating for QuantityType
2023-01-10 20:05:10.577 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:38eacc843e:node6:alarm_power for OnOffType
2023-01-10 20:05:10.577 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:38eacc843e:node6:alarm_power for OnOffType
2023-01-10 20:05:10.577 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:38eacc843e:node6:battery-level for PercentType
2023-01-10 20:05:10.577 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:38eacc843e:node6:battery-level for PercentType
2023-01-10 20:05:10.577 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Polling initialised at 86400 seconds - start in 31708800 milliseconds.
2023-01-10 20:05:10.577 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Device initialisation complete.

apella12 · January 10, 2023, 7:41pm

It looks like the initialization skips the parameter updates, again probably because the NIF does not contain the configuration CC. I would tend the idea that the device is bad, but maybe someone else has another idea.

The next level would be to exclude the device. Try a factory reset on the device and reinclude as a new number. You can unlink your items before excluding, so you can keep the names after reincluding and then relink the channels of the new device to the old items so your rules and persistence will not have to change. I can’t say for sure that will work but it is worth a try before buying a replacement ?

anon71759204 · January 10, 2023, 7:56pm

It makes no sense for a Z-Wave device to have configuration parameters but not support COMMAND_CLASS_CONFIGURATION. As you might expect, Product Command Classes claims that the Z-TEMP2 supports COMMAND_CLASS_CONFIGURATION V4.

We should check the NIF coming from the device.

anon71759204 · January 10, 2023, 8:05pm

Obviously related problem:

frnck · January 10, 2023, 8:53pm

Why? I have no problem associating the device with other ON/OFF switches.

frnck · January 10, 2023, 9:22pm

I have removed the device from the controller. I have reset the device (20 seconds on button). I have included the device. Below an extract from the logging. You can find there: GET_CONFIGURATION - CONFIGURATION class not supported. Could that be related and causing this issue?

2023-01-10 22:14:13.176 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node Init transaction completed with response COMPLETE
2023-01-10 22:14:13.176 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer - advancing to SET_LIFELINE
2023-01-10 22:14:13.176 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Got an event from Z-Wave network: ZWaveInitializationStateEvent
2023-01-10 22:14:13.177 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: SET_LIFELINE - Checking group 1
2023-01-10 22:14:13.177 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: SET_LIFELINE - Checking group 2
2023-01-10 22:14:13.177 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: SET_LIFELINE - Checking group 3
2023-01-10 22:14:13.178 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer - advancing to GET_CONFIGURATION
2023-01-10 22:14:13.178 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Got an event from Z-Wave network: ZWaveInitializationStateEvent
2023-01-10 22:14:13.179 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer: GET_CONFIGURATION - CONFIGURATION class not supported
2023-01-10 22:14:13.179 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Node advancer - advancing to STATIC_END
2023-01-10 22:14:13.180 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Got an event from Z-Wave network: ZWaveInitializationStateEvent
2023-01-10 22:14:13.180 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Updating node properties.
2023-01-10 22:14:13.180 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Updating node properties. MAN=411
2023-01-10 22:14:13.180 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Updating node properties. MAN=411. SET. Was 411
2023-01-10 22:14:13.181 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Properties synchronised
2023-01-10 22:14:13.186 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Update ASSOCIATION group_ZWaveAssociationGroup [index=1, name=null, profile1=null, profile2=null, associations=[node_1]]: Adding Controller (node_1)

This is the event log:

023-01-10 22:13:23.737 [INFO ] [openhab.event.InboxAddedEvent       ] - Discovery Result with UID 'zwave:device:38eacc843e:node8' has been added.
2023-01-10 22:13:43.136 [INFO ] [openhab.event.InboxRemovedEvent     ] - Discovery Result with UID 'zwave:device:38eacc843e:node8' has been removed.
2023-01-10 22:13:43.140 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from UNINITIALIZED to INITIALIZING
2023-01-10 22:13:43.148 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2023-01-10 22:13:43.250 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to UNINITIALIZED
2023-01-10 22:13:43.256 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2023-01-10 22:13:43.262 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2023-01-10 22:13:43.263 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2023-01-10 22:13:43.264 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2023-01-10 22:13:54.138 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from ONLINE to ONLINE: Node initialising: ENDPOINTS
2023-01-10 22:13:54.138 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from ONLINE: Node initialising: ENDPOINTS to ONLINE: Node initialising: UPDATE_DATABASE
2023-01-10 22:13:54.140 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from ONLINE: Node initialising: UPDATE_DATABASE to ONLINE: Node initialising: STATIC_VALUES
2023-01-10 22:14:06.823 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from ONLINE: Node initialising: STATIC_VALUES to ONLINE: Node initialising: ASSOCIATIONS
2023-01-10 22:14:10.639 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from ONLINE: Node initialising: ASSOCIATIONS to ONLINE: Node initialising: SET_WAKEUP
2023-01-10 22:14:10.640 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from ONLINE: Node initialising: SET_WAKEUP to ONLINE: Node initialising: SET_ASSOCIATION
2023-01-10 22:14:13.178 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from ONLINE: Node initialising: SET_ASSOCIATION to ONLINE: Node initialising: SET_LIFELINE
2023-01-10 22:14:13.180 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from ONLINE: Node initialising: SET_LIFELINE to ONLINE: Node initialising: GET_CONFIGURATION
2023-01-10 22:14:22.110 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:38eacc843e:node8' changed from ONLINE: Node initialising: GET_CONFIGURATION to ONLINE

frnck · January 10, 2023, 9:25pm

Also, the values I see in Openhab do not align with the defaults in https://manuals.thermo-floor.no/PDF/Heatit%20Z-Temp2/Manual_Heatit_Z-Temp2_FW%201.1_Ver2020-D_ENG.pdf.

apella12 · January 10, 2023, 9:42pm

I believe so, but that message means that the node doesn’t support it, not the binding. It seems to me the device has failed, but we can see if @chris has a moment to weigh in.

On a side note the XML in the OH zwave folder is from the device. That is the artifact that helps to build an entry for a new device. Since the Configuration CC is in the DB, it was there on an XML from the device for someone.

Lastly

I wouldn’t worry too much about this as they are stale from sometime before the Configuration CC disappeared.

edit: one last thing (and possibly should have asked earlier, but it is unlikely) What do you see in the karaf console with bundle:list |grep ZWave

chris · January 10, 2023, 10:16pm

Correct.

As I think eluded to above, if the class is not specified in the NIF, then the binding won’t provide support for it even though the database does have it defined. We can force it to add added by adding a config to the database that tells the binding to add it even if it’s not in the NIF. This is probably the solution here.

To force this to be added, we need to add the ccAdd option to the command class options as below -:

Note that this might be case sensitive from what I can see in the exporter…

frnck · January 10, 2023, 10:20pm

This is the output of karaf:

openhab> bundle:list |grep ZWave                                                                                                                                        
241 │ Active │  80 │ 3.4.0                  │ openHAB Add-ons :: Bundles :: ZWave Binding
openhab>

apella12 · January 10, 2023, 10:25pm

No problem there. Do you have DB access to make the change Chris suggests?

frnck · January 10, 2023, 10:33pm

I don´t know which database you are referring to. So the answer is probably no. Also I do not fully understand the proposed change.

apella12 · January 10, 2023, 10:50pm

I didn’t know this was possible. Chris is the expert

What the change will do will force the binding to ask about the configuration even though there is no Configuration CC in the NIF. Of course the node will still have to respond with the parameters 1-14.

It is the DB you referenced in your first post Anyway I will add the ADD. It could be a few days before it is merged into the binding

chris · January 11, 2023, 12:41am

Thanks @apella12 . I’m doing a database export now…

anon71759204 · January 11, 2023, 2:58am

I can’t quite believe that the device doesn’t claim to support COMMAND_CLASS_CONFIGURATION. I would really like to see the NIF … Even if the fix solves the problem, something (the device itself?) seems to be severely broken.

chris · January 11, 2023, 3:45am

Sometimes devices don’t report all their command classes in the NIF. This isn’t too uncommon (sadly). There may be other requirements that mean the binding should always assume some of these classes are supported even if not reported (eg the device class reqjuirements).

frnck · January 11, 2023, 10:15am

I have installed openhab through a repository. Please let me know how and when I can test.

cat /etc/apt/sources.list.d/openhab.list 
deb [signed-by=/usr/share/keyrings/openhab.gpg] https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable main

apt list --installed | grep openhab
openhab/stable,stable,now 3.4.0-1 all [geïnstalleerd,opwaardeerbaar naar: 3.4.1-1]