HS3SA-Z Smart Smoke Detector shows up as unknown device

jeroenB · July 8, 2022, 9:49am

Is there a solution for my issue? My device is not recognised. Thing type: unknown device
I have bought a Heiman HS3SA-Z (ZWave) Smart Smoke Alarm and on the internet i found HS1SA-Z/HS3SA-Z is recognised by the last binding versions.
I use Openhab 3.3.0
382 │ Active │ 80 │ 3.3.0 │ openHAB Add-ons :: Bundles :: ZWave Binding

In the documentation i found:
openhab 3.3.0: Things Summary - ZWave | openHAB
Heiman Technology Co. Ltd HS1SA-Z heiman_hs1sa_00_000 Smoke Detector

During the include process i get the message in the log:
NODE 10: Device discovery could not resolve to a thingType! Manufacturer data not known.

Can some one help me to solve this problem?

chris · July 8, 2022, 10:14am

Try waking the device up so that the binding can complete the discovery. At the moment, the information used to work out what device type this is has not been retrieved from the device so the binding is unable to identify it.

apella12 · July 8, 2022, 6:51pm

First welcome

May want to take a picture of the Thing properties (expand with dropdown arrow) on the UI page to see if anything interesting is there regarding properties.

Also turning on the Zwave Debug when you wake the device will give some insight as to what is going on (where it is in the initialization process). There is a log viewer here that provides a friendlier view.

Bob

jeroenB · July 9, 2022, 10:15am

Here 2 screen print of the log and the setting:

chris · July 9, 2022, 10:48am

As mentioned above - you need to wake the device up - have you tried this? The binding will not (ie can not) communicate with the device until it is woken up.

jeroenB · July 9, 2022, 11:21am

I push with the pin several times in the little hole on the push button. Nothing changed.
Do you have an other procedure to wake up this device?

apella12 · July 9, 2022, 3:09pm

According to the manual in the device DB Are you seeing the green LED confirmation for include/exclude?
smoke

Separately your log file looks like you are pressing “removed failed” on the device UI page. If yes, that will not work. To exclude, go to the controller UI page “Exclude Devices” then press the networking button for 5 seconds (per picture) If you get the green flashes, set the Zwave debug, go to inbox/zwave/scan and hold for 2 seconds. There should be significant log activity.

Bob

jeroenB · July 9, 2022, 4:23pm

I don’t know why it this time works after a week doing the same.
My inclusion procedure is:
Inclusion

-Click [Add] icon in Z-Wave PC Controller Program.-Press the Net_Button 3 times within 1.5s, Green LED is Blinking 3 times within 1 second.-If Inclusion Process is successful, Green led will turn off.

Read more: https://manuals.plus/heiman/smart-smoke-sensor-manual#ixzz7YYqxXhov

Result:

Thanks for everything.

jeroenB · July 9, 2022, 5:43pm

I read this in my log:
2022-07-09 19:41:50.867 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling deferred until initialisation complete

jeroenB · July 9, 2022, 6:15pm

How do I get the initialization process completed, see the last lines in the log.

2022-07-09 20:01:37.481 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Controller is ONLINE. Starting device initialisation.

2022-07-09 20:01:37.482 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating node properties.

2022-07-09 20:01:37.482 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating node properties. MAN=2147483647

2022-07-09 20:01:37.490 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Properties synchronised

2022-07-09 20:01:37.495 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Initialising Thing Node…

2022-07-09 20:01:37.496 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Initialising cmd channel zwave:device:dd0866aac8:node11:sensor_binary for OnOffType

2022-07-09 20:01:37.498 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Initialising state channel zwave:device:dd0866aac8:node11:sensor_binary for OnOffType

2022-07-09 20:01:37.499 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Initialising cmd channel zwave:device:dd0866aac8:node11:alarm_smoke for OnOffType

2022-07-09 20:01:37.500 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Initialising state channel zwave:device:dd0866aac8:node11:alarm_smoke for OnOffType

2022-07-09 20:01:37.503 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Initialising state channel zwave:device:dd0866aac8:node11:alarm_smoke for OnOffType

2022-07-09 20:01:37.516 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Initialising cmd channel zwave:device:dd0866aac8:node11:battery-level for PercentType

2022-07-09 20:01:37.519 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Initialising state channel zwave:device:dd0866aac8:node11:battery-level for PercentType

2022-07-09 20:01:37.520 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling initialised at 60 seconds - start in 23160 milliseconds.

2022-07-09 20:01:37.533 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Device initialisation complete.

2022-07-09 20:02:00.680 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling…

2022-07-09 20:02:00.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling deferred until initialisation complete

2022-07-09 20:03:00.680 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling…

2022-07-09 20:03:00.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling deferred until initialisation complete

2022-07-09 20:04:00.680 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling…

2022-07-09 20:04:00.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling deferred until initialisation complete

2022-07-09 20:05:00.680 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling…

2022-07-09 20:05:00.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling deferred until initialisation complete

2022-07-09 20:06:00.680 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling…

2022-07-09 20:06:00.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling deferred until initialisation complete

2022-07-09 20:07:00.680 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling…

2022-07-09 20:07:00.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling deferred until initialisation complete

2022-07-09 20:08:00.680 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling…

2022-07-09 20:08:00.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling deferred until initialisation complete

2022-07-09 20:09:00.680 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling…

2022-07-09 20:09:00.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling deferred until initialisation complete

apella12 · July 9, 2022, 7:19pm

The standard advice is to wake the device until there are five lines on the UI page.
Five Lines of configured node

It does seem odd the binding is trying to poll every minute. What is this area of the UI page showing?

Lastly and you are not going to want to hear this; I see the device was added securely. That’s okay, except it needs to be added while the zstick is in the OH server to exchange the Network Security Key (advanced tab on the UI page). Based on your post you used the PC controller program. The only solution would be exclude then include again with the stick in the OH server (or use the PC controller, but make sure it is included without security. Maybe @chris has another idea.

Bob

chris · July 9, 2022, 7:57pm

As we keep saying - you MUST wake the device up to allow it to complete initialisation.

For secure inclusion, the device must be included using the binding - this is also clearly stated in the docs. The safest thing to do would be to exclude, and reinclude with the binding if that was no the way it was done.

Spaceman_Spiff · July 10, 2022, 5:45am

I’ve had nothing but trouble with the HS3SA-Z inclusion. I’ve created a thread some time ago where I described the errors.
In the end I returned the device and got a replacement which seems to work somehow even though I did the absolute same for inclusion.

All in all this seems to be a really bad device and I can only discourage everyone from using it.

jeroenB · July 11, 2022, 12:09pm

My problem still exist.
Is there someone with wright solving procedure/steps?
I have exclude the device again for a fresh inclusion process but this is the output of my log and the device is again an unknown thing-type device:

2022-07-11 14:02:20.776 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Got an event from Z-Wave network: ZWaveNetworkEvent

2022-07-11 14:02:34.479 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Handler disposed. Unregistering listener.

2022-07-11 14:02:34.572 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 11: Serialise aborted as static stages not complete

2022-07-11 14:03:06.051 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 11: Device discovery completed

2022-07-11 14:03:06.054 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 11: Device discovery could not resolve to a thingType! Manufacturer data not known.

2022-07-11 14:03:09.838 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: MANUFACTURER not set

2022-07-11 14:03:09.838 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Controller status changed to ONLINE.

2022-07-11 14:03:09.839 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Controller is ONLINE. Starting device initialisation.

2022-07-11 14:03:09.842 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating node properties.

2022-07-11 14:03:09.843 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Updating node properties. MAN=2147483647

2022-07-11 14:03:09.844 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Properties synchronised

2022-07-11 14:03:09.851 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Initialising Thing Node…

2022-07-11 14:03:09.853 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Polling initialised at 86400 seconds - start in 27043200 milliseconds.

2022-07-11 14:03:09.853 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Device initialisation complete.

jeroenB · July 11, 2022, 12:12pm

And when i do a health device, the log says that the device initialisation is not complete, but above it says the initialisation is complete:
2022-07-11 14:10:23.943 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Configuration update received

2022-07-11 14:10:23.945 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Configuration update set action_heal to true (Boolean)

2022-07-11 14:10:23.946 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Starting heal on node!

2022-07-11 14:10:23.946 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 11: Can not start heal as initialisation is not complete (REQUEST_NIF).

2022-07-11 14:10:23.947 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Configuration update ignored node_id to 11 (BigDecimal)

apella12 · July 11, 2022, 1:53pm

Since your logs still show Node 11 after “exclusion” it was not excluded. Not sure how you performed that task. On the reinclusion is should now be Node 12, so think the security issue is still there. You may need to factory reset the device after your exclusion process.

This just means that for an unknown manufacturer (MAN=2147483647 (7FFFFFFF)) the ZwaveThingHandler has finished.

This has nothing to do with the problem. It helps optimize the controller to device communication and will not run until the “five lines” are there.

What IMO think would be helpful is a debug level inclusion from the very moment you put the INbox/Zwave/Scan on a fully excluded device. I have attached a successful log that you can view using the log viewer to see what should be happening. Again IMO what is going wrong is happening very early. The MFG data is the very first configuration message (after the security-which should be skipped) This is at 11:01:12.355 in my file.
N8-9.5sec.txt (666.7 KB)

Bob
edit: Actually I expect the problem is in some way connected to security.

jeroenB · July 13, 2022, 1:33pm

Finally i reset my Zwave sensor/dongle. Reset the HS3SA. After that i did the inclusion proces and this works. The initialisation is completed. Openhab receives the parameters from the sensor when i push the test button.