I have a Garage Door Tilt Sensor (from Monoprice) that I use to help monitor the Open/Closed status of the door. The sensor worked fine in OH1, but unsure where something could be wrong in OH2. A little background on what I have done.
I moved all devices over to a new Aeon Gen5 Controller, repairing all devices to the new controller. In Habmin, the Garage Door Tilt Sensor shows initialized just fine, Nice green check mark, shows the channels, etc. I have even added the sensor into my items file, and that ‘new’ item shows linked to the sensor in Habmin as well.
And in Habmin I see the sensor shows an 'Unknown State and a battery of 100. But I can’t get anything to show in a sitemap.
My items file looks like below and appears to correct.
Contact FF_Sensor_ZGarageDoor "Garage Door Status [MAP(en.map):%s]" (Garage) { channel="zwave:device:158135ef039:node17:sensor_binary" }
Number FF_Sensor_ZGDBattery "Garage Door Battery Level [%d %%]" (Garage) { channel="zwave:device:158135ef039:node17:battery_level" }
And i a sitemap, i have:
Text item=FF_Sensor_ZGarageDoor
Text item=FF_Sensor_ZGDBattery
I have enabled the Map Transformation as well. Just can’t figure out why both the Door Status and Battery show as Blank in site map.
So I did a little bit searching and after seeing this in my log
[quote] Could not transform ‘-’ with the file ‘en.map’ : Target value not found in map for ‘-’
[/quote]
Then added this my en.map file: -=undefined
Now, I at least see the status as Undefined in the BasicUI sitemap. But can’t figure why no Open or Closed state unless something maybe wrong with the Database Entry?
And also the battery is still showing blank as well, but I believe the item file is defined properly.
In turning on the zwave logging, I see this in the log. But also no reference to the battery level. It appears the Alarm is returning the ON|OFF value and not the sensor.
I also did try and show the Alarm Value in a SiteMap, but it only returns an “err” value
07:00:00.572 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 17: Application Command Request (ALIVE:DETAILS)
2016-11-06 07:00:00.573 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 17: Incoming command class ALARM
2016-11-06 07:00:00.573 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 17: Received ALARM command V2
2016-11-06 07:00:00.573 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 17: Process NOTIFICATION_REPORT V2
2016-11-06 07:00:00.573 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 17: NOTIFICATION report - 7 = 255, event=2, status=255
2016-11-06 07:00:00.574 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 17: Alarm Type = BURGLAR (7)
2016-11-06 07:00:00.574 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2016-11-06 07:00:00.574 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 17: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2016-11-06 07:00:00.575 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 17: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2016-11-06 07:00:00.575 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2016-11-06 07:00:00.575 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 2, type OnOffType
2016-11-06 07:00:00.575 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 17: Updating channel state zwave:device:158135ef039:node17:alarm_burglar to ON [OnOffType]
I opened an Issue, may be seeing similar behavior from the Aeon Door Sensor as well. I’ll post a separate topic on that but getting ‘err’ for a value in a sitemap.
I believe this is still an open bug in the database as I see the bug report still open. But I was trying and thinking that I still should be able to get the sensor to report correctly in OH2.
The issue appears to be the binary sensor is triggers, the Alarm_Burglar is sending an ON or OFF command. And the binary_sensor reports as Triggered or Untriggered.
So in my items file I have this. But in a sitemap, both the Door Status always return as undefined and the Alarm Switch in a sitemap is not changing from ON to OFF either?
Contact FF_Sensor_GarageDoorStatus "Garage Door Status [MAP(en.map):%s]" <garagedoor> (Garage) { channel="zwave:device:1587fb1d72a:node17:binary_sensor" }
Switch FF_Sensor_GarageDoorAlarm "Garage Door Alarm [MAP(en.map):%s]" <garagedoor> (Garage) { channel="zwave:device:1587fb1d72a:node17:alarm_burglar" }
Number FF_Sensor_GarageDoorBattery "Garage Door Battery [%d %%]" <garagedoor> (Garage) { channel="zwave:device:1587fb1d72a:node17:battery-level" }
Actually, watching the sitemap in browser and debug log, I see the alarm is updated to ON when you tilt the sensor either horizontal or vertical. So the Alarm state will never trigger to OFF.
But i may be able to trick things with a rule and gonna experiment.
NODE 15: Updating channel state zwave:device:40d94185:node15:sensor_binary to ON [OnOffType]
NODE 15: Updating channel state zwave:device:40d94185:node15:sensor_binary to OFF [OnOffType]
NODE 15: Updating channel state zwave:device:40d94185:node15:sensor_binary to ON [OnOffType]
NODE 15: Updating channel state zwave:device:40d94185:node15:sensor_binary to OFF [OnOffType]
NODE 15: Updating channel state zwave:device:40d94185:node15:sensor_binary to ON [OnOffType]
NODE 15: Updating channel state zwave:device:40d94185:node15:sensor_binary to OFF [OnOffType]
NODE 15: Updating channel state zwave:device:40d94185:node15:sensor_binary to ON [OnOffType]
NODE 15: Updating channel state zwave:device:40d94185:node15:sensor_binary to OFF [OnOffType]
Would you mind posting your working config? As described in the bug report, I updated my sensor_door Item to Contact but I still don’t see anything in the zwave debug logs.
I’m unsure if you have the same Sensor, but you should check in PaperUI, Habmin and your logs how the sensor is reacting. I would just hold the sensor in my hand inside my own and turn it to see what it did before I mounted on the door.
But in my items file, my (Monoprice) Zwave Door Tilt Sensor is setup as follows. Note, I don’t use the Alarm_Burglar, but it is one of the channels included on the sensor.
Contact FF_Sensor_GarageDoorStatus "Garage Door Status [%s]" <garagedoor> (Garage) { channel="zwave:device:1587fb1d72a:node17:sensor_door" }
Switch FF_Sensor_GarageDoorAlarm "Garage Door Alarm [MAP(en.map):%s]" <garagedoor> (Garage) { channel="zwave:device:1587fb1d72a:node17:alarm_burglar" }
Number FF_Sensor_GarageDoorBattery "Garage Door Battery [%d %%]" <garagedoor> (Garage) { channel="zwave:device:1587fb1d72a:node17:battery-level" }
Thanks @ptmuldoon
I have the monoprice garage door sensor as well. It shows as ZG8101 Garage Door Tilt Sensor.
I asked for your settings as I only see alarm updates in the debug log but never see the status/sensor_door updates. I have tried tilting the unit forward and back a few times but only the alarm updates come through:
Your items file info looks correct from what I can tell.
Can you confirm you do see all 3 channels in PaperUI and Habmin? What Zwave controller are you using and perhaps remove the device from the controller, then readd back to the controller and scan in OH2?
I confirmed all 3 channels were in PaperUI and I tried unpairing and repairing, but still had the same issue. I ended up buying a second unit from Monoprice. So far, the logs look better, I see multiple command classes in use (earlier I was only seeing ALARM):
I have four monoprice garage door sensors and they all work well. I’m on the snapshot release of openhab. Keep in mind that you don’t need to unpair the z-wave devices from your controller after doing an update. You only need to remove them and re-add them in Habmin.
Here is my items for one of them.
Contact FF_Garage_Door_Front_Sensor "Garage Door Front [%s]" <garagedoor> (FF_Garage, Door) {channel="zwave:device:cab10335:node18:sensor_door"}
Number FF_Garage_Door_Front_Battery "Garage Door Front Battery [%d %%]" <batterylevel> (Battery) {channel="zwave:device:cab10335:node18:battery-level"}
Switch FF_Garage_Door_Front_Alarm "Garage Door Front Alarm [%s]" <siren> (Alarm) {channel="zwave:device:cab10335:node18:alarm_burglar"}
I actually just ordered a new/different sensor. For some reason, after 2 good years with the monoprice sensor, it has simply stopped responding and seems stuck in the ‘open’ position even after multiple wakeups and manual tilts of the sensor.
So I added the new monoprice garage door sensor to my sitemap and… nothing. The status always shows dashes. When I tilt the sense back and forth, I see the items in the zwave debug log:
Contact Sensor_Garage_Door_Open_Closed "Garage Door Status [%s]" <garagedoor> (Garage) { channel="zwave:device:5bfa0704b9:node33:sensor_door" }
Switch Alarm_Garage_Door "Garage Door Alarm [%s]" <garagedoor> { channel="zwave:device:5bfa0704b9:node33:alarm_burglar" }
Number Battery_Garage_Door_Tilt "Garage Door Tilt Sensor Battery [%d %%]" <battery> (gBattery, gHistory) { channel="zwave:device:15bfa0704b9:node33:battery-level" }
I did notice that I don’t see anything in the event.log when I move the sensor back and forth, that seems like a clue. Can someone who has this working confirm that they do see tile sensor related items in their event.log file?