EZMotion Express (HSM100) not reporting Temp and Luminance

Add-ons Bindings
1

Switched over to OH 2.1 about 2 weeks ago. Had a bit of a difficulty in rewriting all config files, but I am there for 90%.

I have a EZMotion Express sensor (movement, temp and luminance) that I think stopped reporting after I made the cut over, but I am not really sure. Anyway, the device is initialized, its reporting values in the log but they never end in the channel but the battery level…

for instance Temperature

2017-10-02 21:19:24.297 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 11: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V5
2017-10-02 21:19:24.298 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 11: Sensor Multi Level REPORT received
2017-10-02 21:19:24.298 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 11: Sensor Type = Temperature(1), Scale = 1
2017-10-02 21:19:24.298 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 11: Sensor Value = 71.7
2017-10-02 21:19:24.298 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2017-10-02 21:19:24.299 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 71.7
2017-10-02 21:19:24.299 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 11: No sensorType set for channel zwave:device:0042a834:node11:alarm_motion

Luminance:

2017-10-02 21:19:24.222 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 11: Incoming command class SENSOR_MULTILEVEL
2017-10-02 21:19:24.222 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 11: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V5
2017-10-02 21:19:24.222 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 11: Sensor Multi Level REPORT received
2017-10-02 21:19:24.223 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 11: Sensor Type = Luminance(3), Scale = 0
2017-10-02 21:19:24.223 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 11: Sensor Value = 35
2017-10-02 21:19:24.223 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2017-10-02 21:19:24.223 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 35
2017-10-02 21:19:24.224 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 11: No sensorType set for channel zwave:device:0042a834:node11:alarm_motion

Its reporting against the alarm_motion channel but I think that is wrong. The alarm_motion channel is working:

2017-10-02 20:41:18.208 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 11: Incoming command class BASIC
2017-10-02 20:41:18.208 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 11: Received Basic Request
2017-10-02 20:41:18.208 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 11: Basic Set sent to the controller will be processed as Basic Report
2017-10-02 20:41:18.208 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 11: Basic report, value = 0xFF
2017-10-02 20:41:18.208 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-10-02 20:41:18.208 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
2017-10-02 20:41:18.209 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating channel state zwave:device:0042a834:node11:alarm_motion to 255 [DecimalType]
2017

as is the battery report:

2017-10-02 20:50:20.271 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 11: Starting initialisation from DONE
2017-10-02 20:50:20.273 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 11: Incoming command class BATTERY
2017-10-02 20:50:20.274 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 11: Received Battery Request
2017-10-02 20:50:20.274 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 11: Battery report value = 89
2017-10-02 20:50:20.275 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-10-02 20:50:20.275 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 89
2017-10-02 20:50:20.276 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating channel state zwave:device:0042a834:node11:battery-level to 89 [DecimalType]

Anybody using this sensor and having the same experience?

regards,

Han

2

It should work ok - we spent some time getting it working properly a while back…

3

Chris,

I read the whole thread. I started having this problem last Wednesday and as far as I can remember with all the other stuff/problems I had it seemed to be working ok on OH2.1.
Because of this I deleted the node from the controller, deleted the xml filed, rebooted the system with the same result for 4 times in a row :wink:

In the debug log I can see the values coming in, but they are not put into the channels except for battery and motion.

4

The binding really can’t not put them into the channels unless the database is wrong which would mean it doesn’t work for anyone.

The most likely issue is that the link from the item to the channel is busted or something - I would check the links…

5

Chris,

you have brought me on to something:

itemfile:

Number	Sensor_VH_Keuken_Battery "Batterij (KE)[%.0f %%]" <battery> (gAll,VH_Keuken,gBatteryItems) 	{ channel="zwave:device:0042a834:node11:battery-level"}
Switch	Keuken_Motion   "Keuken bewegingssensor [MAP(motion.map):%s]" (gVoorhuis,gStatus)  { channel="zwave:device:0042a834:node11:alarm_motion" }
Number	Sensor_VH_Keuken_Temperature	"Keuken [%.2 °F]"	<temperature>	(gAll,VH_Keuken)  {channel="zwave:device:0042a834:node11:sensor_temperature3"}
Number	Sensor_VH_Keuken_Temperature_Celsius	"Temperatuur (KE)[%.2f °C]"	<temperature> (gClimateItems)
Number	Sensor_VH_Keuken_Luminance	"Helderheid (KE) [%.0f %%]"	<sun>	(gAll,VH_Keuken,gClimateItems)  {channel="zwave:device:0042a834:node11:sensor_luminance2"}

smarthome:links list delivers something else ( luminance does not have a 2 and temp not a 3)

Sensor_VH_Keuken_Battery -> zwave:device:0042a834:node11:battery-level
Keuken_Motion -> zwave:device:0042a834:node11:alarm_motion
Sensor_VH_Keuken_Temperature -> zwave:device:0042a834:node11:sensor_temperature
Sensor_VH_Keuken_Luminance -> zwave:device:0042a834:node11:sensor_luminance

I’ll keep digging :wink:

cheers!

6

Killed all the links through karaf -> smarthome:links clear. After that the list is:

openhab> smarthome:links list | grep Keuken
Sensor_VH_Keuken_Battery -> zwave:device:0042a834:node11:battery-level
Keuken_Motion -> zwave:device:0042a834:node11:alarm_motion
Sensor_VH_Keuken_Temperature -> zwave:device:0042a834:node11:sensor_temperature3
Sensor_VH_Keuken_Luminance -> zwave:device:0042a834:node11:sensor_luminance2

The result however in the logs is the same:

2017-10-02 22:32:14.622 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 11: Incoming command class SENSOR_MULTILEVEL
2017-10-02 22:32:14.622 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 11: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V5
2017-10-02 22:32:14.622 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 11: Sensor Multi Level REPORT received
2017-10-02 22:32:14.623 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 11: Sensor Type = Luminance(3), Scale = 0
2017-10-02 22:32:14.623 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 11: Sensor Value = 29
2017-10-02 22:32:14.625 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2017-10-02 22:32:14.625 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 29
2017-10-02 22:32:14.626 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 11: No sensorType set for channel zwave:device:0042a834:node11:alarm_motion

I’ll leave it over night and see if it clears up.

@RayBe, HSM100 still working for you?

cheers,

Han

7

What version of OH did you upgrade from and what are some of the problems you encountered? Is there something we could have added to the docs that would have made the process easier for you?

8

Rich,

I did an upgrade from 1.8 to 2.1. I thought it was a good time to start with a brand new system and slowly copy over all item/maps/rules and at the same time clean house. There is a lot of information in the community site, as well as binding descriptions. That helped out a great number of times.

Things I encountered; Astro I can’t get to work with the new binding, still using the old one. Zwave no things file so I had to learn to work with paper UI and habmin.

And because of the change of underlying platform (12.04->16.04) I had a lot of problems getting my nodejs for Opentherm up and running again.

Overall a good learning curve with loads of help :wink:

btw still stuck on the HSM100…

regards

Han

9

There are some known bugs with Astro in the 2.1 release that have been corrected in the 2.2 release. If you search the forum you should be able to find a posting with instructions for how to get the 2.2 SNAPSHOT version of just that binding to run in your 2.1 install. It will involve uninstalling the binding, downloading a kar file, unzipping it, and dropping the astro’s jar file into the addons folder.

Given the nature of Zwave, I’m afraid that is indeed all but required. There are a few people who have worked out how to define zwave Things in .things files, but the recommended approach these days is to let OH automatically discover Things where possible and if you prefer, define your Items in .items files.

You don’t have to use PaperUI. You can do everything you need to through the Karaf Console.

Wish I could help.

Thanks for the feedback.