Cyrus Multisensor 4in1 Temperature

Setup, Configuration and Use Beginners
1

Hello folks,

after nearly half a year i came back to openhab. Some of my old problems solved, others are new.

A new problem i have is with a new sensor i got. The Cyrus 4in1 Multisensor. Battery works an shows me the state.

Temperature, humidity und motion don’t work. But in thís post i concentrate on the temperature.

My item config looks like this:

Number	eg_wz_multi_temp			"Temperatur Wohnzimmer [%.1f °C]"	<temperature>		(gWohnzimmer, gHeizenWZ)	{channel="zwave:device:a9a8d718:node2:sensor_temperature"}

In my sitemap the item looks like this:

Text	item=eg_wz_multi_temp

Is there something i am missing?

Here my systeminfos:

  • Platform information:
    • Hardware: RaspberryPi 3
    • OS: openhabian
    • openHAB version: latest
2

What is the device called in OH? I can’t find this in the database but I guess it’s there under a different name?

3

This is the entry in Paper UI:

image
image.png585×936 52.2 KB

4

There are some updates going through with this device for the alarm channels, but the temperature should be ok. I’d suggest to look at the logfile to see what is shown.

5

This is what i found in my eventlog:

2017-11-20 19:09:31.643 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from OFFLINE: Node not found in Z-Wave network to ONLINE: Node initialising: EMPTYNODE
2017-11-20 19:09:31.914 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: EMPTYNODE to ONLINE: Node initialising: PROTOINFO
2017-11-20 19:09:31.930 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: PROTOINFO to ONLINE: Node initialising: INIT_NEIGHBORS
2017-11-20 19:09:31.952 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: INIT_NEIGHBORS to ONLINE: Node initialising: FAILED_CHECK
2017-11-20 19:09:31.967 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: FAILED_CHECK to ONLINE: Node initialising: WAIT
2017-11-20 19:09:32.834 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: WAIT to ONLINE: Node initialising: DISCOVERY_COMPLETE
2017-11-20 19:09:32.838 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: DISCOVERY_COMPLETE to ONLINE: Node initialising: PROTOINFO
2017-11-20 19:09:32.849 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: PROTOINFO to ONLINE: Node initialising: INIT_NEIGHBORS
2017-11-20 19:09:32.869 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: INIT_NEIGHBORS to ONLINE: Node initialising: FAILED_CHECK
2017-11-20 19:09:32.878 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: FAILED_CHECK to ONLINE: Node initialising: WAIT
2017-11-20 19:09:36.459 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: WAIT to ONLINE
2017-11-20 19:09:36.474 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE to ONLINE: Node initialising: PING
2017-11-20 19:09:36.521 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: PING to ONLINE: Node initialising: DETAILS
2017-11-20 19:09:36.529 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: DETAILS to ONLINE: Node initialising: GET_CONFIGURATION
2017-11-20 19:09:36.566 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: GET_CONFIGURATION to ONLINE: Node initialising: DYNAMIC_VALUES
2017-11-20 19:09:36.666 [ThingUpdatedEvent         ] - Thing 'zwave:device:a9a8d718:node2' has been updated.
2017-11-20 19:09:36.684 [ConfigStatusInfoEvent     ] - ConfigStatusInfo [configStatusMessages=[]]
2017-11-20 19:09:36.757 [ItemStateChangedEvent     ] - eg_wz_multi_bat changed from NULL to 70
2017-11-20 19:09:36.759 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: DYNAMIC_VALUES to ONLINE: Node initialising: DYNAMIC_END
2017-11-20 19:09:36.796 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: DYNAMIC_END to ONLINE: Node initialising: HEAL_START
2017-11-20 19:09:36.800 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: HEAL_START to ONLINE: Node initialising: DELETE_ROUTES
2017-11-20 19:09:36.803 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: DELETE_ROUTES to ONLINE: Node initialising: RETURN_ROUTES
2017-11-20 19:09:36.812 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: RETURN_ROUTES to ONLINE: Node initialising: NEIGHBORS
2017-11-20 19:09:37.246 [ThingUpdatedEvent         ] - Thing 'zwave:device:a9a8d718:node2' has been updated.
2017-11-20 19:09:37.246 [ConfigStatusInfoEvent     ] - ConfigStatusInfo [configStatusMessages=[]]
2017-11-20 19:09:37.250 [hingStatusInfoChangedEvent] - 'zwave:device:a9a8d718:node2' changed from ONLINE: Node initialising: NEIGHBORS to ONLINE

The other entries are “removed” and “added” as i tested something.

Hope this helps.

6

I would recommend getting a debug log - the event log doesn’t really provide any useful information. Check the log using the online viewer to see what is being received.

7

Is the debug.log the openhab.log?

8

Yes - with debug logging enabled of course :wink: .

9

Ok, so i activated it for some minutes. What should i search for in the log file?

10

You want to look for any multilevel sensor command class entries. If you ignore the device initialisation where there is a lot happening, periodically you should get temperature updates and in general there should be limited communications at that time so it should hopefully stand out.

11

So here is what i get:

2017-11-22 08:09:37.290 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling...
2017-11-22 08:09:37.292 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling zwave:device:a9a8d718:node2:sensor_binary
2017-11-22 08:09:37.293 [DEBUG] [ternal.converter.ZWaveBasicConverter] - NODE 2: Generating poll message for BASIC endpoint 0
2017-11-22 08:09:37.295 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 2: Creating new message for application command BASIC_GET
2017-11-22 08:09:37.298 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling zwave:device:a9a8d718:node2:sensor_luminance
2017-11-22 08:09:37.300 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 2: Generating poll message for SENSOR_MULTILEVEL, endpoint 0
2017-11-22 08:09:37.302 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Node doesn't support get requests for MULTI_LEVEL_SENSOR
2017-11-22 08:09:37.305 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling zwave:device:a9a8d718:node2:sensor_relhumidity
2017-11-22 08:09:37.307 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 2: Generating poll message for SENSOR_MULTILEVEL, endpoint 0
2017-11-22 08:09:37.309 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Node doesn't support get requests for MULTI_LEVEL_SENSOR
2017-11-22 08:09:37.311 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling zwave:device:a9a8d718:node2:sensor_temperature
2017-11-22 08:09:37.313 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 2: Generating poll message for SENSOR_MULTILEVEL, endpoint 0
2017-11-22 08:09:37.316 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 2: Node doesn't support get requests for MULTI_LEVEL_SENSOR
2017-11-22 08:09:37.318 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling zwave:device:a9a8d718:node2:alarm_motion
2017-11-22 08:09:37.320 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling zwave:device:a9a8d718:node2:alarm_tamper
2017-11-22 08:09:37.322 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling zwave:device:a9a8d718:node2:battery-level
2017-11-22 08:09:37.325 [DEBUG] [rnal.converter.ZWaveBatteryConverter] - NODE 2: Generating poll message for BATTERY endpoint 0
2017-11-22 08:09:37.327 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 2: Creating new message for application command BATTERY_GET
2017-11-22 08:09:37.330 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Message already on the wake-up queue. Removing original.
2017-11-22 08:09:37.332 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Putting message SendData in wakeup queue.
2017-11-22 08:09:37.335 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Message already on the wake-up queue. Removing original.
2017-11-22 08:09:37.337 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 2: Putting message SendData in wakeup queue.
12

Is there a solution for the problem?