Or ask a community developer to add the fingerprint to a custom edge driver with the right command sets.
Yes, given it looks like its a unique manufacturer code for Boundary then that sounds like the way to go.
Any suggestion on where I’d ask such a question, now I have the full fingerprint?
(thank you for your help today by the way, very much appreciated).
1 Like
I’d ask @philh30 to add it to his Z-Wave sensor driver. It seems to have the capabilities your device needs.
name: generic-sensor
components:
- id: main
capabilities:
# Notification CC based capabilities
- id: contactSensor
version: 1
- id: motionSensor
version: 1
- id: tamperAlert
version: 1
# Sensor Multilevel CC based capabilities
- id: illuminanceMeasurement
version: 1
- id: relativeHumidityMeasurement
version: 1
- id: temperatureMeasurement
version: 1
# Other
- id: platemusic11009.deviceNetworkId
version: 1
- id: battery
version: 1
categories:
- name: GenericSensor
3 Likes
In general, those requests go in the following topic
Post Requests for Zwave Edge Drivers Here (community-created)
But if you see a specific edge driver thread that looks good, you can just ask in that one.
To find custom drivers, check the quick browse lists in the community-created wiki
https://thingsthataresmart.wiki/index.php?title=Quick_Browse_Lists_for_Edge_Drivers
1 Like
The driver zwave sensor there is profile for motion, tamperalert and battery.
If you want, then when I get home, add the fingerprints and try it
5 Likes
Yes please, that would be amazing. I’ve just paired the contact sensor too, so the two drivers I need are:
Contact sensor
zw:Ss2a type:0701 mfr:044A prod:0004 model:0007 ver:1.08 zwv:7.14 lib:03 cc:5E,85,8E,59,55,86,72,5A,87,73,80,70,31,9F,71,84,6C,7A
Capabilities: contact, tamper alert, battery, temperature
Motion sensor
zw:Ss2a type:0701 mfr:044A prod:0004 model:0003 ver:1.08 zwv:7.14 lib:03 cc:5E,55,9F,6C sec:86,85,8E,59,72,5A,87,73,80,70,31,71,84,7A
Capabilities: motion, tamper alert, battery, temperature
1 Like
@sipuncher
Added to this driver version
────────────────────────────────────────────────────
Name Z-Wave Sensor and Child Thermostat Mc
Version 2023-03-02T20:55:35.167642868
────────────────────────────────────────────────────
- id: 044A/0004/0003
deviceLabel: Boundary Motion Sensor
manufacturerId: 0x044A
productType: 0x0004
productId: 0x0003
deviceProfileName: motion-battery-tamper
- id: 044A/0004/0007
deviceLabel: Boundary Contact Sensor
manufacturerId: 0x044A
productType: 0x0004
productId: 0x0007
deviceProfileName: contact-battery-tamperalert-temperature
1 Like
Amazing, thank you. I’ve paired 3 motion sensors and 1 contact sensor and they’ve matched with this driver and picked up the correct label so definitely matching the fingerprints.
I’ve only had them paired a few minutes so will wait a bit longer to see whether all of the information comes through correctly, and do some proper testing over the next few days and then report back.
All being well, the final job will be the outdoor siren! 
1 Like
All 6 motions sensors and 3 contact sensors successfully paired and working, thanks @Mariano_Colmenarejo.
The one thing that doesn’t seem to work is the tamper sensor, but that’s a minor issue.
Two other questions if you don’t mind;
-
These sensors have always had an issue where if a change state message (motion/no-motion) doesn’t get to the hub, the sensor reports the last state until triggered again. Does the refresh capability on this driver do anything? Would be hopeful to be able to poll them eg once an hour to return to the correct state if they ever get out of sync.
-
Boundary had an option to turn the light off on the sensors that flashes when motion detected/door opened. This was good for the sensor in our bedroom that is surprisingly bright at night. I assume this isn’t a standard feature on other motion sensors for the driver to support it?
2 Likes
Hi @sipuncher
I’m glad they work!
The handling of tamperAlert is done with the default handlers, if it doesn’t work it means that device sends some non-standard or custom command.
The refresh does work, a GET command is sent for each command class or capabilities supported, but if the device is asleep, it may not respond.
The way in which the status is updated from time to time is with the wakeUp configured on the device. It will have a wakeUp by default and I don’t know if it would be convenient to change it. If device doesn’t disconnect, offline status, it means that it sends reports every x time and it should send the status it really has.
The light will be configured with a parameter, if you find in the documentation what parameter and value is sent to turn it off I can try to do it
1 Like
Thanks for providing some explanation, that does help.
The devices aren’t going offline so I think they are sending reports every few minutes… I contacted Boundary about this issue before, and I remember them saying that the devices send updates to things like Temperature, but not the motion/contact status for some reason. They were looking into changing it, but sounds like a device firmware thing I suspect rather than anything that can be done with a driver.
With regards the light, unfortunately they don’t provide any documentation to this level of detail as it was a black-box product. It would be great if they (the liquidators) would open-source the software so that others could try to get some continued value out of the platform now, but seems unlikely. I’ll make some enquiries anyway.
Thanks again for your help, I really appreciate it.
I’ll save the siren for another day when I feel like climbing a ladder and risking a very loud alarm going off!
1 Like
If they got permission to use the z wave logo, they should have filed a “Z wave conformance statement” and that should list all command sets and parameter values, other than the ones in the “manufacturer proprietary” category. But I haven’t been able to find it anywhere. 
There’s a small possibility that you could check with the zwave alliance and see if they have it on file.
2 Likes
Thanks - I’ve also looked through the Z Wave alliance site for Boundary, plus the third parties they had building the hardware and firmware for them, but couldn’t find anything either other than Boundary Technologies - z-wavealliance.
I’ve sent an email to them to ask the question… Given Z Wave Europe are listed on the liquidators report, they clearly have a commercial relationship with them.
1 Like
I’m on hubitat with boundary (I actually run the Boundary alarm- users group on FB… a few are asking there about ST, so it’s good to see this post) I still have my ST hub.
I added the motion sensors & contacts fine as generic zwave motion/contacts… with temps and tampers.
Did you get that siren down?? lol. I have mine open and it reveals a ZGM130S Z-wave 700 sip module. I can get the siren to sound, but any other function like the LED glow is dead, and the red LED on the siren is constantly on, even after clear/refresh.
2 Likes
Nope I’ve not had the time to tackle that yet… My sensors have been stable the past few days which is great, although are prone (as they were connected directly to Boundary) to getting stuck in the last state (eg motion detected) until next triggered - assuming because that particular message doesn’t get to the hub, and there is no handshake/guaranteed delivery.
I’m hoping Z-Wave Alliance will get back to me to provide more specifications of the sensors to see if I can poll them occasionally to fix this.
On the siren, it sounds like there are some parameters on it that need to be set, that were lost when you reset it to pair it to your Hubitat hub. The LED glow for example was on for fixed hours in the evening, which must have been set by the Boundary hub based upon it’s clock.
It would be nice if ex Boundary employees wanted to help us out here, but given they’ve left all comms to their liquidators, and their CEO blocked me on Twitter when I called him out on it, I’m not hopeful 
1 Like
LOL, blocked! I’ve messaged the head of customer services who used to be in my Boundary group on FB before they all left for the obvious. Weirdly, I had a brand new siren arrive just the week before, and they didn’t bother to collect the old one! It only had broken side catches which I can 3d print if I can get it working a bit more. It would be a terrible shame for it just to be a dumb siren switch, but I’ve no idea why I can’t get the constant red led off.
Phil was very helpful on the numerous times I had to contact support.
I’ve contacted the liquidators to ask who owns the IP of the software for Boundary at this point… if no-one has wanted to buy it, I don’t quite know where ownership goes… but certainly couldn’t stay with the owners as they have no rights over any of the assets now. I’d buy it for £1 to put it on github!
On the Siren, does it also have a state of armed? As in, the siren will sound if tampered when armed, but not when disarmed? I wouldn’t be too popular with a 100db siren going off at home!
1 Like
It would be nice if ex Boundary employees wanted to help us out here, but given they’ve left all comms to their liquidators I’m not hopeful
Oh I’d imagine some of them would want to help you but are unsure of the legalities around that since the ‘company’ is in insolvency. 
2 Likes
True. Apparently the company still owns the software (not sure how that works for an insolvent company) but the liquidators are discussing whether they can make specific documentation available to us, specifically how the sensors and the siren communicates over Z-Wave.
1 Like
I had a reply today from the liquidators about my ‘will this be open-sourced’ query… and the slightly hopeful response is “We are currently working to determine the feasibility of releasing the source code.”
…so wait and see!
2 Likes