Thansk, your answer is partially. I do not want to do it externally but automatically preferably via home assistant. And where is it stored? Stick or not?
Not possible, if I recall correctly the zwave stick backup software is windows only.
When calling the ozw.add_node service to add my Schlage lock, what value do I put for the ‘secure’ parameter? I already have a secure network key configured.
UPDATE: I got it working. The payload should be
{‘secure’: True}
has anyone been able to use a custom device xml file with the add-on? No matter what I do if i set a custom device type xml when i refreshnode or exclude and re-add the device it crashes the daemon and continues to crash it until I remove the custom device type xml. The same XML works perfectly outside the add-on (using ozw-admin in local server mode it works perfect).
just wondering if anyone has been able to add an xml device type? (using the add-on)
Today i added my Homeseer HSM100 multisensor.
The device worked under the “old” integration, i had to enable polling to get the temp end luminance values.
To get motion events i had a automation setup to listen to the node event BASIC-LEVEL value changing from 0 to 255.
I have been fiddling for hours to get this sensor to report motion without any luck.
Does anybody have any clues or tips to get the motion sensor part to report?
Any help is much appreciated.
Thanks,
br,
Raymond
1 Like
Hi all,
I have one questions perhaps a little out of context.
Im a Homeassistant / Zwave beginner and is currently strugling to get the Aeotech Doorbell 6 to send messages to my homeassistant on the “old” 1.4 zwave software. The Doorbell is connected but im not able to pickup the push of the button in automations.
I’ve tried to use the guide in this post Aeotech ZW162 Doorbell but failed to get to work.
So here is my questions - is Zwave software version 1.6 having a way to detect the push of the button?
(here 1.4 needs a workaround)
sidenote: im using “venv” on ubuntu (running on ESXi) - and the Aeotech USB zwave stick (pass through from ESXi)
Sorry for noob question 
I have the same problem, so the same question
I’m currently working with @Fishwaldo on my own personal setup and the solution may fix this problem. It seems v1.6 of OpenZwave has this issue with many old devices. Stay tuned.
1 Like
@petro, @Fishwaldo
A few years back i tried Openhab as a domotica solution. Back then my homeseer hsm100 sensors also didn’t show their motion sensor states.
Chris Jackson who maintains their ZWave implementation helped me and got the sensors working.
In Openhab its called express control: https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/140
Maybe its helpful for you guys.
If i can do anything to help/test, let me know.
Thanks for all your hard work,
br,
Raymond
One thing you could do is download MQTT explorer. Using that you can easily see what the sensor sends when it detects motion. You could use HA to trigger off that MQTT topic or maybe even figure out what the device XML changes would need to be to get it to report properly
Thanks for your reply but i have done that.
The problem is the HSM100 sensor doesn’t send anything over MQTT.
I also was thinking among the lines of checking out the XML-files.
Its all new to me so i don’t have a good clue as were to start looking.
And what to look for.
br,
Raymond
That’s unlikely, the MQTT topics update, check all the command class topics.
I drilled down every instance, topic and whatnot, but i am sorry there is nothing showing at the timestamp that i triggered the motion sensor.
When swinging my arm infant of the sensor i just can’t see any topic updates, usually they appear in grey in MQTT Explorer.
Either i am completely looking in the wrong direction or the sensor isn’t sending a MQTT message when motion is triggered.
Its a very old sensor.
With the ozb 1.4 implementation i also had to look for a basic_level event.
Watch the zwave logs. If nothing is occurring in the logs, it’s the same issue that I’m working with @Fishwaldo on. You’ll have to be patient.
1 Like
the OZW is showing the following when i trigger the motion sensor:
9 Detail Received 0x01, 0x09, 0x00, 0x04, 0x00, 0x09, 0x03, 0x20, 0x01, 0xff, 0x26
9 Info Received Basic set from node 9: level=255: Sending event notification.
9 Detail Notification:NodeEvent
EDIT: this is what is showing in the OZW Logs section of ozwadmin
Can it be that the XML is up to date for the HSM100 sensor?
My knowledge about creating a XML file for a device is non existing, but i am learning (and willing to do so)
Maybe this document shows what is missing for the Homeseer HSM100 sensor.
https://doc.eedomus.com/files/EZMotionSDK.pdf
Could you please shine a light on the matter?
thanks up front,
BR,
Raymond
Basic Set is not supported. Might need to enable some workaround, but that doesn’t work yet either. https://github.com/OpenZWave/qt-openzwave/issues/60
Edit: The workaround in that issue might work for your device if it is sending different basic set values, e.g. 0 for motion off, then 255 for motion on. It currently doesn’t work for cases where the same value is sent repeatedly.
If Polling is enabled OZW queues a SwitchBinaryCmd_Get (Node=x). Is it possible to call that from MQTT, so I could initiate a sort of Poll Once event from Hass?
Thanks
You can call requestnodedynamic with a node number to update the values for the that node on demand. I use that approach with old devices to poll on-demand when HA initiates a state change rather than polling constantly. It won’t work great for switches you interact with physically, but works well for ones controlled mostly through HA.
Example:
- alias: "Refresh Old Zwave livingroom_lamp_right_level"
trigger:
platform: state
entity_id:
- light.livingroom_lamp_right_level
action:
- delay:
milliseconds: "{{ range(500, 1500) | random }}"
- service: mqtt.publish
data:
topic: "OpenZWave/1/command/requestnodedynamic/"
payload: "{\"node\":5}"
The delay is in there to not flood the network with a bunch of requests at the same instant when multiple devices change state at the same time.
1 Like