HSP-02 misidentification

Tags: #<Tag:0x00007efec7bd6510> #<Tag:0x00007efec7bd6330> #<Tag:0x00007efec7bd6038>
  • Platform information:
    • Raspberry pie 4B 8gb
    • OS: Openhabian
    • openHAB version: 03.11.2020
  • Issue of the topic: I’ve got a new Everspring HSP02 motion sensor, i’m very new to OH2 so I try to find the thing with the UI. That work, it create a node 7 but the system think to find a SM103 (contact sensor). I found in others post some similar problems but after some tries they work good.
    I try some times with no different result, I try to modify the .xml file but OH2 continues to ovverride.

Some one has an Idea how to solve it?
When I try to activate the sensor from real… no result.

log:> 2020-11-10 22:00:24.857 [home.event.InboxAddedEvent] - Discovery Result with UID ‘zwave:device:0b045602:node6’ has been added.

2020-11-10 22:00:24.869 [home.event.InboxAddedEvent] - Discovery Result with UID ‘zwave:device:0b045602:node7’ has been added.

2020-11-10 22:00:41.905 [me.event.InboxRemovedEvent] - Discovery Result with UID ‘zwave:device:0b045602:node6’ has been removed.

2020-11-10 22:00:48.651 [me.event.InboxRemovedEvent] - Discovery Result with UID ‘zwave:device:0b045602:node7’ has been removed.

2020-11-10 22:00:48.671 [hingStatusInfoChangedEvent] - ‘zwave:device:0b045602:node7’ changed from UNINITIALIZED to INITIALIZING

2020-11-10 22:00:48.694 [hingStatusInfoChangedEvent] - ‘zwave:device:0b045602:node7’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline

2020-11-10 22:00:48.711 [hingStatusInfoChangedEvent] - ‘zwave:device:0b045602:node7’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE

2020-11-10 22:00:48.732 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0b045602:node7’ has been updated.

2020-11-10 22:00:48.738 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0b045602:node7’ has been updated.

2020-11-10 22:00:48.745 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0b045602:node7’ has been updated.

2020-11-10 22:00:48.753 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0b045602:node7’ has been updated.

2020-11-10 22:00:48.755 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]

2020-11-10 22:01:36.244 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0b045602:node7’ has been updated.

2020-11-10 22:17:31.319 [hingStatusInfoChangedEvent] - ‘zwave:device:0b045602:node7’ changed from ONLINE to REMOVING

2020-11-10 22:17:31.325 [hingStatusInfoChangedEvent] - ‘zwave:device:0b045602:node7’ changed from REMOVING to REMOVED

2020-11-10 22:17:31.337 [hingStatusInfoChangedEvent] - ‘zwave:device:0b045602:node7’ changed from REMOVED to UNINITIALIZED

2020-11-10 22:17:31.512 [hingStatusInfoChangedEvent] - ‘zwave:device:0b045602:node7’ changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)

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

2020-11-10 22:17:38.467 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! Manufacturer data not known.

2020-11-10 22:17:38.472 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:0b045602:node6’ to inbox.

2020-11-10 22:17:38.483 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:0b045602:node7’ to inbox.

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

2020-11-10 22:17:38.473 [home.event.InboxAddedEvent] - Discovery Result with UID ‘zwave:device:0b045602:node6’ has been added.

2020-11-10 22:17:38.484 [home.event.InboxAddedEvent] - Discovery Result with UID ‘zwave:device:0b045602:node7’ has been added.

2020-11-10 22:17:51.471 [me.event.InboxRemovedEvent] - Discovery Result with UID ‘zwave:device:0b045602:node7’ has been removed.

2020-11-10 22:17:51.487 [hingStatusInfoChangedEvent] - ‘zwave:device:0b045602:node7’ changed from UNINITIALIZED to INITIALIZING

2020-11-10 22:17:51.520 [hingStatusInfoChangedEvent] - ‘zwave:device:0b045602:node7’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline

2020-11-10 22:17:51.527 [hingStatusInfoChangedEvent] - ‘zwave:device:0b045602:node7’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE

2020-11-10 22:17:51.537 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0b045602:node7’ has been updated.

2020-11-10 22:17:51.551 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0b045602:node7’ has been updated.

2020-11-10 22:17:51.557 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0b045602:node7’ has been updated.

2020-11-10 22:17:51.564 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:0b045602:node7’ has been updated.

2020-11-10 22:17:51.567 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]

2020-11-10 22:27:41.124 [ome.event.ItemUpdatedEvent] - Item ‘Batteria_sensore_movimento_PT’ has been updated.

2020-11-10 22:27:54.470 [.ItemChannelLinkAddedEvent] - Link ‘Batteria_sensore_movimento_PT-zwave:device:0b045602:node7:battery-level’ has been added.

2020-11-10 22:29:06.010 [.ItemChannelLinkAddedEvent] - Link ‘Atrio_sensore_movimento_PT-zwave:device:0b045602:node7:sensor_binary’ has been added.

2020-11-10 22:29:09.748 [.ItemChannelLinkAddedEvent] - Link ‘Atrio_sensore_movimento_PT-zwave:device:0b045602:node7:alarm_general’ has been added.

Blockquote

What does the xml file produced by the device say? According to our database those 2 devices have differing identification.

Very likely we will need debug logs at stated in the binding documentation.

Hi Bruce,

today I can’t access as I have habitude with VNC server… (strange).
So,…

Here what I found to identify the thing:

dbReference 428
defaultAssociations 1,2
manufacturerId 0116
manufacturerRef 0001:0001
modelId SM103
vendor Chromagic Technologies Corporation
zwave_beaming true
zwave_class_basic BASIC_TYPE_ROUTING_SLAVE
zwave_class_generic GENERIC_TYPE_SENSOR_BINARY
zwave_class_specific SPECIFIC_TYPE_ROUTING_SENSOR_BINARY
zwave_deviceid 1
zwave_devicetype 1
zwave_frequent false
zwave_lastwakeup 2020-11-11T20:29:00Z
zwave_listening false
zwave_manufacturer 278
zwave_neighbours
zwave_nodeid 8
zwave_routing true
zwave_secure false
zwave_version 1.2

As you see the system recognised another thing that exist on the database.

Today I success activate a light with this sensor, but is very dull and I cannot regulate it because of the wrong ID…

If I cannot access to the log file directly… with the SSH how I can give you this file?

The HSP-02 has a manufacturer id of 0060. your device firmware is reporting a manufacturer id of 0116.

The binding only knows what the device provides.

Hi Bruce,

you are right, but the device that I bought is the HSP-02 not the SM103.

HSP-02 : https://www.openhab.org/addons/bindings/zwave/thing.html?manufacturer=everspring&file=hsp02_0_0.html

SM103: https://www.openhab.org/addons/bindings/zwave/thing.html?manufacturer=chromagic&file=sm103_0_0.html

and my problem is that today the sensor work with the basic configuartion.
But, considered that my system didnt recognised the HSP02 I cannot configure it.

I tried to update my OH2, with the result that I cannot enter anymore with a VNC virtual Screen (is blocked in the new version?).
So now I don’t know how to reach the .xml file :slight_smile:

You’ve got any suggestion?

Are you running openHAB 3? That version number looks strange to me. The current bersions are snapshots with build numbers.

openHAB 3 is only in testing right now but the SM103 is in the binding and has not changed since openHAB 2.5.0.

sorry the last openhabian.

Teorically not.
I’ve just re-installed my system with the last version of Openhabian. If i saw correctly is yet a OH 2.5.

There is a way to manually force a thing?

1 Like

I have sometimes found deleting the Thing from openHAB and re-discovering it helps in some situations. You do NOT need to exclude from the Z-Wave network.