Anyone know if this can be controlled with Zigbee2mqtt? I’d basically want to use the sensors, siren and keypad as components of my existing bwalarm/akasma74 alarm system which is custom built. So so long as I can interface with the components using a combination of mqtt and zigbee should be OK?
thanks all
I would also be really interested if this zigbee devices is or could be supported in any way in Home assistant.
Just to revive this topic.
The Open/Close sensors are working with Zigbee2MQTT.
The Motion sensor should work with Zigbee2MQTT as well. I haven’t connected it yet, so I don’t have any first hand experience. But Zigbee2MQTT supports it.
The Keypad is currently worked on by myself and @Hasshun.
Already made some progress but still need to test how is it working correctly, and make all features to be possible. (SOS, occupancy, etc…)
(And just a fair comment, the devices are not really appealing aesthetically, due to the HUGE Linkind sign on the side of the contact sensor. Consider it for the WAF!)
Ps.: The siren is built into the Hub itself. I haven’t even tried to make it work.
Hi @GSzabados and @Hasshun! I came across this thread and was wondering: will you be working on the siren or does it seem impossible to integrate in z2m? Really happy with the possibilities for the sensors and keypad, so I’ll definitely be using that once my kit arrives 
(they have a very nice sale right now!)
The siren is built into the Hub.
Here is how you can hack the Hub to have access the underlying OpenWRT.
I haven’t figured out how the siren can be triggered from the OpenWRT.
So you could hack the siren and use it in HA ?
@Twinsen68, Someone just asked the same on the github discussion, but unfortunately not. I haven’t had too much time to tinker with it since.
Hi all, did you solved the issues with the keypad? On the Z2M web site is reported that It is supporter. Do you know if it works well?
https://www.zigbee2mqtt.io/devices/ZS130000078.html
There is an issue open in Z2M that the keypad disconnects from the network after a while when connected directly to the coordinator, but otherwise it works well.
Have a look here:
Thanks for the information 
I’m not sure if I understood well, I got there is an issue open in Z2M but I didn’t understood if the blue print you suggested to me solve this problem
This is the issue:
The Blueprint works.
If the Blueprint would solve it then there wouldn’t be an issue. 
But seriously, if the keypad is connected to a repeater, but not directly to the coordinator then there seems to be no issues.
Got It 
but is there a way to force the keypad to be connected to a repeater and not to a coordinator?
In Z2M there is a way, but I am not sure about ZHA or DeConz.
Perfect, I have the conbee2 but I’m using z2m. Do you have a link to the documentation to set the use of coordinator and repeater?
All what I know as documentation.
But I am talking about the option what you see when you open the drop down in the UI.
Select any of the repeaters in the list and then press Permit to join.
Like this:
The devices paired will join the network through that repeater.
Thanks to your suggestions the keypad is perfectly integrated in my alarm system
Now I would like to reuse the hub siren, I was thinking to modify the hub in order to activate the siren through an esp32.
I saw the images where you disassemble the hub and I’ve a couple of questions.
Once removed the zigbee module are available contact through which I could activate/command the siren?
If Yes do you have an image to show It to me?
How could I disassemble the siren without destroy the case?
If you have never updated the Hub, I mean you have never connected it to Linkind services, then scroll down to the bottom of the discussion.
Someone managed to get the default password for the stock OpenWRT.
Someone else managed to trigger the siren through one of the built in services.
@Elle, I will be unable to give hands on help with this, because I don’t have the Hub in hand for a while. But if you haven’t updated the firmware of the Hub, then you should be able to log in to the OpenWRT with the password listed in the opening post of that discussion. If you have updated the firmware of the Hub, then you will need to contact one of the guys in the discussion, that how was managed to enable dropbear to access again the OpenWRT.
I am unsure that the uBoot has been locked or not, that could have been some other communication issue.
For triggering the siren, you can try first the command listed in the discussion’s end somewhere, and you can build some automation to run commands on the device from HA, so anything is possible.
I never turned on the hub, I bought the kit just for the keypad 
.
I will try to follow the discussion
Really thanks for your help.
Then you should be good. Plug in the Hub, connect to the Wifi network what it creates. (I use a mobile phone most of the time.) Use Fing (app) to check the devices on the Wifi network. Check what ports the device has open, if 80 is open, then navigate to the IP address of the device and use root as username, and the password mentioned in the discussion. To connect to your own Wifi network, just set it up with the OpenWRT what is on it.
Personally I disabled the Linkind services on the Hub to do not “call to home”.
Good luck! Please report back how you proceed. Especially with the default password, as I never tried that.
