Getting temperature reading from ZMNHDD Flush Dimmer Plus from Qubino

frankose · April 24, 2016, 7:46am

I have a ZMNHDD Flush Dimmer Plus from Qubino controlling some light in my kitchen. It has a temperature sensor option when connecting a separate sensor cable to the device which I have done. I had this working in version 1.9 of the zwave binding using the following configuration:

Number	Temperature_GF_KitchenLight	"Temperature kitchen light [%.1f °C]"	<temperature>		( Temperature,KitchenArea)	{zwave="37:command=sensor_multilevel,sensor_type=1"}

However, I cannot figure out how to get this to work with the 2.0 version of the binding. Sensor_multilevel seems to be missing from the database, but it is present in my configuration file (attached, rename the extension to xml, I change it to PDF to get it uploaded.). I guess this is the reason why cannot find it on the channel page. I tried to update the database with my device file a couple of weeks ago, but it does not seem at that update has taken. Did I do something wrong?

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/210

node37.pdf (28.9 KB)

chris · April 24, 2016, 8:42am

The database is missing this configuration. I suspect that the Qubino only reports the multilevel_sensor class if you have the temperature sensor plugged in (as Fibaro also does in their sensors). So, probably the person who loaded the original XML for this device didn’t have it…

I’ll update it shortly.

frankose · April 24, 2016, 9:03am

Great, thanks. Why didn’t it take what I tried to update the database with that configuration file a few weeks ago? I don’t remember exactly the messages it returned, but to my untrained eye it looked successful, but just had to be committed by someone else?

chris · April 24, 2016, 9:23am

I would need to look back through the history to be sure, but if someone else has already uploaded an XML for this device, the database will only look at certain parameters - it won’t add command classes for instance. This is to try and prevent errors, but it should have reported that if it was the case.

chris · April 24, 2016, 9:26am

I just checked the logs, and your upload on 10th April was rejected for this reason. It only checked the type and id.

Anyway, I’ve now updated the database with this so it should be in the next build.

frankose · April 24, 2016, 1:22pm

Quick question, how is the new build distributed, and how will I know when it is available? I installed it internally in OH2. With auto update? I have never seen any button there to manually install an update.

chris · April 24, 2016, 1:38pm

You need to use PaperUI to uninstall the ZWave binding, and then install again. When it reinstalls, it should grab the latest version.

You will need to wait till tomorrow though as it’s built in the early hours of the morning (EU time) and I didn’t get this merged last night…

frankose · April 24, 2016, 1:41pm

Got it, thanks.

frankose · April 25, 2016, 8:15am

I was looking forward to updating the binding today (around 8 o’clock UTC), but either it didn’t work or I did something wrong. I uninstalled and reinstalled the binding and deleted the configuration file. After restarting OH2 it fetched updated configuration for the device (I believe), I have included some of the log for this below. It still doesn’t seem to be too happy about the sensor_multilevel, and I still have not got any channel like this for the device.

2016-04-25 10:04:45.679 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: MANUFACTURER to ONLINE: APP_VERSION
2016-04-25 10:04:46.751 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: APP_VERSION to ONLINE: DISCOVERY_COMPLETE
2016-04-25 10:04:46.751 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: DISCOVERY_COMPLETE to ONLINE: DISCOVERY_WAIT
2016-04-25 10:04:46.756 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: DISCOVERY_WAIT to ONLINE: VERSION
2016-04-25 10:04:47.898 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: VERSION to ONLINE: ENDPOINTS
2016-04-25 10:04:48.351 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Unsupported command class MULTI_INSTANCE_ASSOCIATION
2016-04-25 10:04:48.351 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Unsupported command class ASSOCIATION_GROUP_INFO
2016-04-25 10:04:48.630 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Unsupported command class MULTI_INSTANCE_ASSOCIATION
2016-04-25 10:04:48.630 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Unsupported command class ASSOCIATION_GROUP_INFO
2016-04-25 10:04:48.860 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Unsupported command class MULTI_INSTANCE_ASSOCIATION
2016-04-25 10:04:48.860 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Unsupported command class ASSOCIATION_GROUP_INFO
2016-04-25 10:04:49.049 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 37: Unsupported command class MULTI_INSTANCE_ASSOCIATION
2016-04-25 10:04:49.051 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: ENDPOINTS to ONLINE: UPDATE_DATABASE
2016-04-25 10:04:49.052 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: UPDATE_DATABASE to ONLINE: STATIC_VALUES
2016-04-25 10:04:50.756 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:50.758 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@365e6d5f
2016-04-25 10:04:52.737 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:52.738 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@5ef48f25
2016-04-25 10:04:52.741 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: STATIC_VALUES to ONLINE: ASSOCIATIONS
2016-04-25 10:04:52.938 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@611ebb37
2016-04-25 10:04:52.938 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:53.207 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:53.208 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@20a29bf1
2016-04-25 10:04:53.416 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:53.416 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@2fddeab9
2016-04-25 10:04:53.629 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:53.630 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@580c638a
2016-04-25 10:04:53.864 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@707a86a3
2016-04-25 10:04:53.864 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:54.054 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:54.054 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@65d32e2f
2016-04-25 10:04:54.245 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:54.246 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@6e1aea1b
2016-04-25 10:04:54.628 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@1f241817
2016-04-25 10:04:54.628 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:54.862 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:54.863 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@2e525d43
2016-04-25 10:04:55.043 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:55.043 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@15f97b30
2016-04-25 10:04:55.240 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@3192b8b2
2016-04-25 10:04:55.240 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:55.242 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: ASSOCIATIONS to ONLINE: SET_WAKEUP
2016-04-25 10:04:55.248 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: SET_WAKEUP to ONLINE: SET_ASSOCIATION
2016-04-25 10:04:55.249 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: SET_ASSOCIATION to ONLINE: STATIC_END
2016-04-25 10:04:55.250 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: STATIC_END to ONLINE: SESSION_START
2016-04-25 10:04:55.251 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: SESSION_START to ONLINE: GET_CONFIGURATION
2016-04-25 10:04:55.447 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:55.449 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@8e1d6a9
2016-04-25 10:04:55.666 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:55.666 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@b77cfc7
2016-04-25 10:04:55.973 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:55.974 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@34e53ab3
2016-04-25 10:04:56.178 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:56.180 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@6a9be7e4
2016-04-25 10:04:56.378 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@4ee8952d
2016-04-25 10:04:56.379 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:56.599 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@483a56c7
2016-04-25 10:04:56.599 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:56.839 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@3fbea04b
2016-04-25 10:04:56.840 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:57.064 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:57.065 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@436043c5
2016-04-25 10:04:57.273 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:57.274 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@5517ddd1
2016-04-25 10:04:57.499 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:57.499 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@6006a450
2016-04-25 10:04:57.712 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:57.712 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@6a4d1480
2016-04-25 10:04:57.933 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:57.933 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@7c3b1f1e
2016-04-25 10:04:58.177 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:58.178 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@70dbfb60
2016-04-25 10:04:58.373 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:58.374 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@4987eea9
2016-04-25 10:04:58.590 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:58.590 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@1b4959ff
2016-04-25 10:04:58.808 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:58.809 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@371b32a
2016-04-25 10:04:59.004 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:59.004 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@42ceb6ea
2016-04-25 10:04:59.236 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@66a99242
2016-04-25 10:04:59.236 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:59.438 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:59.438 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@10adda98
2016-04-25 10:04:59.643 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@1e4bd344
2016-04-25 10:04:59.643 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:04:59.851 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@4e385ae2
2016-04-25 10:04:59.853 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:00.311 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@29054f81
2016-04-25 10:05:00.311 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:00.316 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: GET_CONFIGURATION to ONLINE: DYNAMIC_VALUES
2016-04-25 10:05:00.833 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:00.835 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@394f361
2016-04-25 10:05:01.354 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:01.354 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@4cd3aeb1
2016-04-25 10:05:01.848 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:01.848 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@7d938091
2016-04-25 10:05:01.852 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_fdd70699_node37_meter_kwh1 changed from NULL to 44.9
2016-04-25 10:05:02.064 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:02.065 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@3d02bd94
2016-04-25 10:05:02.067 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_fdd70699_node37_meter_watts1 changed from NULL to 18.4
2016-04-25 10:05:03.457 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;Received RSSI: -44
2016-04-25 10:05:03.462 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;read: 3-3-0     s=1,c=1,t=17,pt=5,l=4,sg=0:9283
2016-04-25 10:05:03.463 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 3;1;1;0;17;9283
2016-04-25 10:05:03.465 [INFO ] [marthome.event.ItemStateChangedEvent] - CurrentTotalPower changed from 9230 to 9283
2016-04-25 10:05:03.479 [INFO ] [marthome.event.ItemStateChangedEvent] - AverageTotalPower changed from 5338.415254237288536387495696544647216796875 to 5365.0423728813557318062521517276763916015625
2016-04-25 10:05:03.588 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;Received RSSI: -46
2016-04-25 10:05:03.593 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;read: 3-3-0     s=1,c=1,t=24,pt=5,l=4,sg=0:113606
2016-04-25 10:05:03.595 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 3;1;1;0;24;113606
2016-04-25 10:05:03.720 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;Received RSSI: -47
2016-04-25 10:05:03.725 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 0;255;3;0;9;read: 3-3-0     s=1,c=1,t=18,pt=7,l=5,sg=0:113.6060 after restarting 
2016-04-25 10:05:03.727 [DEBUG] [g.mysensors.protocol.MySensorsReader] - 3;1;1;0;18;113.6060
2016-04-25 10:05:03.728 [INFO ] [marthome.event.ItemStateChangedEvent] - TotalEnergy changed from 113.5550 to 113.6060
2016-04-25 10:05:07.066 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 37: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-25 10:05:07.067 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 37: Got an error while sending data. Resending message.
2016-04-25 10:05:07.285 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:07.285 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@637c5cb0
2016-04-25 10:05:07.298 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_fdd70699_node37_switch_dimmer1 changed from NULL to 100
2016-04-25 10:05:07.505 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:07.506 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@32ab6781
2016-04-25 10:05:07.748 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:07.748 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@3ec8d47c
2016-04-25 10:05:07.751 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_fdd70699_node37_switch_binary1 changed from NULL to ON
2016-04-25 10:05:08.002 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:08.004 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@6fbf5332
2016-04-25 10:05:08.007 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_fdd70699_node37_sensor_binary2 changed from NULL to OFF
2016-04-25 10:05:08.248 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:08.255 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_fdd70699_node37_sensor_binary3 changed from NULL to OFF
2016-04-25 10:05:08.294 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@6e270ba9
2016-04-25 10:05:08.399 [WARN ] [class.ZWaveMultiInstanceCommandClass] - NODE 37: CommandClass SENSOR_MULTILEVEL (0x31) not implemented by endpoint 3, fallback to main node.
2016-04-25 10:05:08.450 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@759ee83
2016-04-25 10:05:08.450 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:08.691 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:08.692 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@7f4ab120
2016-04-25 10:05:08.694 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_fdd70699_node37_switch_binary changed from NULL to ON
2016-04-25 10:05:08.915 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:08.915 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@6a795b38
2016-04-25 10:05:08.917 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_fdd70699_node37_sensor_binary changed from NULL to OFF
2016-04-25 10:05:09.059 [WARN ] [class.ZWaveMultiInstanceCommandClass] - NODE 37: CommandClass SENSOR_MULTILEVEL (0x31) not implemented by endpoint 3, fallback to main node.
2016-04-25 10:05:09.115 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@3cd56f9d
2016-04-25 10:05:09.115 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:09.269 [WARN ] [class.ZWaveMultiInstanceCommandClass] - NODE 37: CommandClass SENSOR_MULTILEVEL (0x31) not implemented by endpoint 3, fallback to main node.
2016-04-25 10:05:09.322 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:09.325 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@7430a372
2016-04-25 10:05:09.479 [WARN ] [class.ZWaveMultiInstanceCommandClass] - NODE 37: CommandClass SENSOR_MULTILEVEL (0x31) not implemented by endpoint 3, fallback to main node.
2016-04-25 10:05:09.547 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:09.548 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@5ed9df65
2016-04-25 10:05:13.283 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'rfxcom:temperaturehumidity:9a0b230b:29194' changed from OFFLINE to ONLINE
2016-04-25 10:05:14.549 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 37: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-25 10:05:14.549 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 37: Got an error while sending data. Resending message.
2016-04-25 10:05:14.699 [WARN ] [class.ZWaveMultiInstanceCommandClass] - NODE 37: CommandClass SENSOR_MULTILEVEL (0x31) not implemented by endpoint 3, fallback to main node.
2016-04-25 10:05:14.755 [INFO ] [smarthome.event.ThingUpdatedEvent   ] - Thing 'zwave:device:fdd70699:node37' has been updated.
2016-04-25 10:05:14.756 [INFO ] [marthome.event.ConfigStatusInfoEvent] - org.eclipse.smarthome.config.core.status.events.ConfigStatusInfoEvent@3e7894f2
2016-04-25 10:05:14.756 [ERROR] [nitialization.ZWaveNodeStageAdvancer] - NODE 37: Node advancer: Retries exceeded at DYNAMIC_VALUES
2016-04-25 10:05:14.771 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:fdd70699:node37' changed from ONLINE: DYNAMIC_VALUES to ONLINE

Seaside · January 9, 2017, 9:21am

@chris

Any update on this?

I’ve added a temperature sensor to my ZMNHDD Flush Dimmer Plus, done a hardware reset and included it again, but without getting temperature values. I don’t have any specific error messages either in the logs except:

2017-01-09 08:35:19.466 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 37: Got an error while sending data. Resending message.
2017-01-09 08:35:19.771 [INFO ] [l.commandclass.ZWavePlusCommandClass] - NODE 37: unknown ZWavePlus device type: 7168
2017-01-09 08:35:22.590 [INFO ] [l.commandclass.ZWavePlusCommandClass] - NODE 37: unknown ZWavePlus device type: 7168
2017-01-09 08:35:27.898 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 37: Timeout while sending message. Requeueing - 2 attempts left!

Can enable debug and try if you think it helps?

Not 100% sure the temperature cable is working either.

Regards, S

chris · January 9, 2017, 1:08pm

Can you attach the XML file for the device with the temperature sensor included and I’ll have a look to see what is reported…

Seaside · January 9, 2017, 7:35pm

Hi!

pastebin.com

http://pastebin.com/raw/rhCvT4Z7

<node>
  <deviceClass>
    <basicDeviceClass>ROUTING_SLAVE</basicDeviceClass>
    <genericDeviceClass>MULTILEVEL_SWITCH</genericDeviceClass>
    <specificDeviceClass>POWER_SWITCH_MULTILEVEL</specificDeviceClass>
  </deviceClass>
  <homeId>0xc90b8c78</homeId>
  <nodeId>37</nodeId>
  <version>4</version>
  <manufacturer>0x159</manufacturer>

This paste has been truncated. show original

Regards, S

Seaside · January 25, 2017, 9:54am

@chris

Anything new about this, I know you have been away.

I get these messages as well:

2017-01-25 10:43:09.492 [WARN ] [class.ZWaveMultiInstanceCommandClass] - NODE 37: CommandClass SENSOR_MULTILEVEL (0x31) not implemented by endpoint 1, fallback to main node.

But not when I run with DEBUG on, which is weird.

Log when starting at
http://www.zoidberg.se/pub/openhablog.zip

Regards, S

TheNetStriker · April 8, 2017, 1:14pm

Did you manage to solve this problem? I also got one ZMNHDD and I’am also not getting any temperature sensor readings on OH2.

chris · April 8, 2017, 1:22pm

I think this has now been added to the database, but as there are currently no updates being built I’m not looked at it yet. Once this is resolved I’ll update the binding.

fyrstyk · July 2, 2017, 8:49am

Hi

I installed Qubino flush dimmer and temperature sensor yesterday, and this is still in the logs:

2017-07-02 10:44:13.529 [INFO ] [l.commandclass.ZWavePlusCommandClass] - NODE 16: unknown ZWavePlus device type: 7168

I’m on the latest snapshot, did this get resolved?

Regards

Glen

chris · July 2, 2017, 8:56am

If it’s still in the logs, then it’s probably not resolve

Don’t worry about it though - this information is not used for anything important. It’s used for display purposes only.

fyrstyk · July 2, 2017, 9:02am

Hi Chris

Does that issue relate to the temperature reading from the Qubino flush dimmer, as I have also been unable to get readings from the module?

Regards

Glen

chris · July 2, 2017, 9:04am

No - the zwave plus class is only used for information - it has no impact on command classes such as temperature or switches etc.

W3B · March 26, 2019, 8:40pm

Is the issue with the temperature already resolved for the Flush Dimmer? I have multiple temperature sensors on double relays and they all work fine. The only issue i have is with the sensor on the Flush Dimmer. i noticed in your Database that the dimmer (ZMNHDD) has the status Information complete requires review.

Would it be a option to just reffer to the ZMNHDA in my things file for the dimmer?

Or is some additional testing required to get this issue resolved.

Thank you in advance.

Regards