Z-Wave Everspring Motion Sensor HSP-02 misidentification

Tags: #<Tag:0x00007f2fc08547a0>
  • Platform information:
    • Hardware: RaspberryPi 3 B+
    • OS: OpenHabian
    • openHAB version: 2.4.0-1
  • Issue of the topic:

I am trying to add a thing for my Z-Wave Motion sensor. It is an Everspring HSP02. It worked fine for years on my vera, but I’m thinking of switching my whole system to Openhab. I’m using an Aeotec Z-Stick as my Z-Wave serial controller via USB. I included the motion sensor to the z-stick and as far as I know that completed successfully. I connect the z-stick to the Pi and reboot it. When I then open up PaperUI, I see the sensor in the Inbox, but it does not properly show up as a HSP02.

Typically at first it shows up as an unknown device, but after waking up the sensor a few times, it collects additional data from the device and it then shows up as a Everspring SM103 door/window sensor. Since both of these devices (HSP02 and SM103) are both supported by OpenHab, i’m not really sure why it would misidentify my motion sensor as a door/window contact. Also, important info… I do not own an SM103 so its not like if its picking up another device in my house. I’ve tried adding the device via Paper and HabMin but neither adds it as the appropriate device and neither gives me the ability to manually add this device or tweak the device type.

I dont have much of any experience with anything but the UI (have only created a couple items files via VS Code) so I’m a bit out of my element as to how autodiscovered z-wave devices are store in a device list so that I can edit the device type. I’ve tried editing the “org.eclipse.smarthome.core.thing.link.ItemChannelLink.json” file to at least change the device label, but I obviously dont know what I’m doing because changes to this file do not actually persist or show up in either UI.

I’d rather stick to this motion sensor since its worked well enough for years, but I’m tempted to just buy something a bit newer (maybe an aeotec multi sensor).

I’ve added some logs of my boot up incase that helps. If additional logs would help, please let me know.

edit: meant to mention that my HSP-02 motion sensor is currently registered as node7 on my z-stick.

2019-06-08 14:40:46.864 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node7' changed from UNINITIALIZED to UNINITIALIZED (BRIDGE_UNINITIALIZED)

2019-06-08 14:40:47.184 [hingStatusInfoChangedEvent] - 'zwave:serial_zstick:aa0d35eb' changed from UNINITIALIZED to INITIALIZING

2019-06-08 14:40:47.213 [hingStatusInfoChangedEvent] - 'zwave:serial_zstick:aa0d35eb' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline

==> /var/log/openhab2/openhab.log <==

2019-06-08 14:40:47.220 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyACM0'

==> /var/log/openhab2/events.log <==

2019-06-08 14:40:47.323 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node6' changed from UNINITIALIZED to INITIALIZING

2019-06-08 14:40:47.330 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node6' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline

2019-06-08 14:40:47.356 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node3' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING

2019-06-08 14:40:47.361 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node7' changed from UNINITIALIZED (BRIDGE_UNINITIALIZED) to INITIALIZING

2019-06-08 14:40:47.366 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node3' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline

2019-06-08 14:40:47.371 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node5' changed from UNINITIALIZED to INITIALIZING

2019-06-08 14:40:47.374 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node7' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline

2019-06-08 14:40:47.377 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node5' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline

==> /var/log/openhab2/openhab.log <==

2019-06-08 14:40:47.381 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized

2019-06-08 14:40:47.431 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller

2019-06-08 14:40:47.433 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.

==> /var/log/openhab2/events.log <==

2019-06-08 14:41:01.097 [hingStatusInfoChangedEvent] - 'ntp:ntp:local' changed from UNINITIALIZED to INITIALIZING

2019-06-08 14:41:01.199 [hingStatusInfoChangedEvent] - 'zwave:serial_zstick:aa0d35eb' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE

2019-06-08 14:41:01.213 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node3' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE

2019-06-08 14:41:01.230 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node5' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE

2019-06-08 14:41:01.247 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node7' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE

2019-06-08 14:41:01.255 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node6' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE

2019-06-08 14:41:01.300 [me.event.ThingUpdatedEvent] - Thing 'zwave:serial_zstick:aa0d35eb' has been updated.

2019-06-08 14:41:31.296 [hingStatusInfoChangedEvent] - 'ntp:ntp:local' changed from INITIALIZING to OFFLINE (COMMUNICATION_ERROR): The network connection to the timeserver 0.pool.ntp.org cannot be established -> returning current sytem time instead.

2019-06-08 14:41:31.308 [vent.ItemStateChangedEvent] - LocalTime_Date changed from NULL to 2019-06-08T14:41:31.293-0500

2019-06-08 14:41:31.311 [vent.ItemStateChangedEvent] - LocalTime_Date changed from 2019-06-08T14:41:31.293-0500 to 2019-06-08T14:41:31.299-0500

2019-06-08 14:42:31.327 [vent.ItemStateChangedEvent] - LocalTime_Date changed from 2019-06-08T14:41:31.299-0500 to 2019-06-08T14:42:31.299-0500

2019-06-08 14:43:31.327 [vent.ItemStateChangedEvent] - LocalTime_Date changed from 2019-06-08T14:42:31.299-0500 to 2019-06-08T14:43:31.303-0500

2019-06-08 14:44:19.548 [ome.event.ItemCommandEvent] - Item 'LocalTime_Date' received command REFRESH

2019-06-08 14:44:19.729 [hingStatusInfoChangedEvent] - 'ntp:ntp:local' changed from OFFLINE (COMMUNICATION_ERROR): The network connection to the timeserver 0.pool.ntp.org cannot be established -> returning current sytem time instead. to ONLINE

2019-06-08 14:44:19.747 [vent.ItemStateChangedEvent] - LocalTime_Date changed from 2019-06-08T14:43:31.303-0500 to 2019-06-08T14:44:19.710-0500

2019-06-08 14:44:31.328 [vent.ItemStateChangedEvent] - LocalTime_Date changed from 2019-06-08T14:44:19.710-0500 to 2019-06-08T14:44:31.294-0500

2019-06-08 14:44:55.522 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node7' changed from ONLINE to UNINITIALIZED

2019-06-08 14:44:55.667 [hingStatusInfoChangedEvent] - 'zwave:device:aa0d35eb:node7' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)

2019-06-08 14:45:31.340 [vent.ItemStateChangedEvent] - LocalTime_Date changed from 2019-06-08T14:44:31.294-0500 to 2019-06-08T14:45:31.299-0500

2019-06-08 14:46:31.336 [vent.ItemStateChangedEvent] - LocalTime_Date changed from 2019-06-08T14:45:31.299-0500 to 2019-06-08T14:46:31.302-0500

2019-06-08 14:47:31.342 [vent.ItemStateChangedEvent] - LocalTime_Date changed from 2019-06-08T14:46:31.302-0500 to 2019-06-08T14:47:31.308-0500

2019-06-08 14:48:31.351 [vent.ItemStateChangedEvent] - LocalTime_Date changed from 2019-06-08T14:47:31.308-0500 to 2019-06-08T14:48:31.313-0500

2019-06-08 14:49:25.114 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@13e9364

==> /var/log/openhab2/openhab.log <==

2019-06-08 14:49:27.297 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:aa0d35eb:node7' to inbox.

==> /var/log/openhab2/events.log <==

2019-06-08 14:49:27.299 [home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:aa0d35eb:node7' has been added.

2019-06-08 14:49:31.357 [vent.ItemStateChangedEvent] - LocalTime_Date changed from 2019-06-08T14:48:31.313-0500 to 2019-06-08T14:49:31.319-0500

Welcome to the forum, and to openHAB.

You might want to consider tagging your post with the zwave tag. A number of people watch for posts on that tag, so your post might have a better chance of being spotted.

The HSP02 is in the zwave device database here. I’m not sure why it’s being discovered as a SM103. The database lists Device Type:IDs of 0001:0001 and 0001:0003 for the HSP02.

Your device may be reporting something different. Can you look at the device properties in Paper UI or HABmin and post back here what Device Type:ID is associated with the thing? Based on what you find, we can decide where to go from there.

Thank you for the tip on the tags…

The device ID was showing up as 0001:0001, however the manufacturer was showing up as chromagic.

I was tinkering a bunch with it today and dont know what I did differently, because I’m almost certain I tried this the other day.

Not certain if its because I changed the manufacturer ID in the node xml file under openhab2-userdata\zwave for that particular node. It was showing up as 0x1116 and I changed it to 0x0060. One other thing that I did was that prior to adding the thing, with the device still in the inbox, I clicked search for new devices and I “woke up” the motion sensor (clicking the include button 3 times within 1.5 seconds) probably about 10 times in frustration. At some point after that, it started showing up in the inbox as a HSP02 motion sensor instead of a SM103 contact.

Now that its included properly, and I have the HSP02 thing added, under properties manufacturerRef shows up as 0001:0001,0001:0003.

Hello,
Sorry if I open this topic again.
I recently purchased an HSP-02 motion sensor, but I am not able to “associate” it in OH2.
As a controller I have a Nortek HUSBZB-1 key (the controller is on-line). OH2 is installed on a raspberrypi 3 B+
When activated (clicking the include button 3 times within 1.5 seconds) the sensor flashing green for about 20 seconds then stops and the search, from the Z-Wave binding, finds nothing.
What am I doing wrong?
Has anyone ever been able to use this motion sensor with the HUSZB-1 controller?
Thank you