Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
11.48k stars 1.62k forks source link

Centralite 3400 Keypad #4613

Closed niekveldhuizen closed 3 years ago

niekveldhuizen commented 3 years ago

What happened

I Orderd a Centralite 3400 Keypad, after some investigation I saw that the supported device is named 3400-D. I don't know that is a compleet differten model? I could pair the device but now i get the message "unsupported device with Zigbeee model '3400'

What did you expect to happen

I did expect it to pair and be supported

How to reproduce it (minimal and precise)

Try to pair the device again.

Debug info

Zigbee2MQTT version: V1.15.0 Adapter hardware: CC2531 Adapter firmware version:

fermentfan commented 3 years ago

Does someone here use the newest dev version of z2m with the Centralite 3400-D? I saw a commit changing the key invalid_code to exit_delay, but my keypad doesn't reliably respond to that code. Also my keypad does never change the system status LED from green to red or something. Could it be the implementation of the device is lacking most functionality?

misteriks commented 3 years ago

Indeed something seems to be changed/broken with the last update.

Invalid_code is no longer accepted as valid and behavior of the other actions changed and broke my automations.

github-actions[bot] commented 3 years ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

Dinth commented 3 years ago

Still doesn't work for me. Unless I'm doing the automation wrong

github-actions[bot] commented 3 years ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

hvddrift commented 2 years ago

Ive got mine very nearly working, use Node Red instead of HA automations because its ... easier to debug :) If anyone wants what i think is a pretty comprehensive node red flow, please let me know!

I can arm it, pass a response back to the keypad via MQTT and i get a "different" beep, which to me suggests no error.

However i cant get the LED status to change -- its always green suggesting not armed.

Im struggling to get it to disarm, and I assume thats because the keypad wont detect that its armed.

{"action":"arm_day_zones","action_code":"1234","action_transaction":22,"action_zone":23,"battery":42,"last_seen":1613201896570,"linkquality":114,"temperature":25.3,"voltage":2900}

I send this response back {"arm_mode": {"zone":"23", "transaction":"22", "mode": "arm_day_zones"}}

The keypad gives a beep as soon as it receives the response, a long beep if nothing is received, and a REALLY long beep if invalid_code is received.

There does seem to be a large number of version of these. I think I have what is called the 3400-C, or "3 series security keypad"

EDIT:: Turns out i was wrong. I can send arm and disarm commands. Just i dont know if i am arming the alarm, or disarming the alarm as the keypad has no indication.

Hi

I would like to see your node red solution for this. Are your able to share it with me?

Regards

Hans

kevincaradant commented 2 years ago

Hi guys.

I don't know what I broken... but since I migrated from 1.21.0 to 1.21.2. My 3400-D doesn't work anymore as expected :( I got always "null' as value for the action_code. And I try to unpair and pair it again but now nothing works as expected (occupancy ect stays at OFF ) ... image I don't know what happens but that seems broken on my side :/

On the Z2M logs, I can see that I have a successful pairing but after that I never had again logs about centralite. No logs on disarm, arm ect. I'm a little frustrated. I don't know if I should rollback version of Z2M. I think somethung change somewhere but I don't know what.

The only logs I have once every 2 or 5 minutes

Zigbee2MQTT:info  2021-10-02 10:03:33: MQTT publish: topic 'zigbee2mqtt/8a5646', payload '{"action":null,"action_code":null,"action_transaction":null,"action_zone":null,"battery":27,"linkquality":105,"occupancy":null,"temperature":29.93,"voltage":2800}'

Edit: after to revert at 1.20.0, everything works well again. What have been changed about centralite ? :)

kevincaradant commented 2 years ago

Any news on it ? Still have issue @Koenkk on the latest 1.22.1 version ;)

ebug Received Zigbee message from 'centralite', type 'commandGetPanelStatus', cluster 'ssIasAce', data '{}' from endpoint 1 with groupID 0
Debug Received Zigbee message from 'centralite', type 'commandGetPanelStatus', cluster 'ssIasAce', data '{}' from endpoint 1 with groupID 0
Info MQTT publish: topic 'zigbee2mqtt/centralite', payload '{"action":null,"action_code":null,"action_transaction":null,"action_zone":null,"battery":42,"linkquality":108,"occupancy":true,"temperature":20.74,"voltage":2900}'
Info MQTT publish: topic 'zigbee2mqtt/centralite', payload '{"action":null,"action_code":null,"action_transaction":null,"action_zone":null,"battery":42,"linkquality":108,"occupancy":true,"temperature":20.74,"voltage":2900}'

I wrote my passcode and it's does not sent anymore :(

And sometimes I have also like a reconnection but maybe it's normal ? I can see the code but it's like 1 time on 10 since the 1.20.0 version of Z2M :/ But I didn't receive it on the HA.


Debug Received Zigbee message from 'centralite', type 'commandGetPanelStatus', cluster 'ssIasAce', data '{}' from endpoint 1 with groupID 0
Info MQTT publish: topic 'zigbee2mqtt/centralite', payload '{"action":null,"action_code":null,"action_transaction":null,"action_zone":null,"battery":42,"linkquality":102,"occupancy":true,"temperature":21.75,"voltage":2900}'
Debug Received Zigbee message from 'centralite', type 'commandGetPanelStatus', cluster 'ssIasAce', data '{}' from endpoint 1 with groupID 0
Info MQTT publish: topic 'zigbee2mqtt/centralite', payload '{"action":null,"action_code":null,"action_transaction":null,"action_zone":null,"battery":42,"linkquality":102,"occupancy":true,"temperature":21.75,"voltage":2900}'
Debug Received Zigbee message from 'centralite', type 'commandArm', cluster 'ssIasAce', data '{"armmode":3,"code":"111111","zoneid":1}' from endpoint 1 with groupID 0
Debug Device 'centralite' announced itself

i will open a new issue maybe for it, I was just waiting ( feedback ) from others if they have the same issue but no one answered to me so nevermind

Dinth commented 2 years ago

Just one thing i have noticed today. When i was playing with the 6 digit keypad (the one with a bell button), when i am entering the (wrong) code, in Zigbee2MQTT panel, "Exposes" tab, i can see action and action_code changing for a half of a second. But this doesnt get reflected via MQTT at all - nothing gets updated. Im still getting MQTT updates on temperature or link status but not on action. Maybe it changes back to the previous value too quickly to get reflected in MQTT? When im doing the same with the 4-digit keypad (the one with a moon button), the same action does get reflected in MQTT.

luisgarcia87 commented 2 years ago

To anyone having the same problem as @Dinth and myself that the Centralite 3400 would disconnect from the network and would not accept any codes until a hard reboot (removing batteries). I've successfully "unblocked" my Centralite 3400 by sending a mqtt message to the device in the "locked/blocked" state like this:

Mqtt publish to Topic: zigbee2mqtt/DEVICE NAME/set payload: { "arm_mode": { "mode": "disarm" } }

Screen Shot 2022-05-29 at 1 20 32 PM

After that my device can receive and send the action_code via mqtt even if there's no responde from the mqtt server telling the centralite if the code is right or wrong.

My use for this device was not as an alarm system, but as a gate access device.

Now when someone is at my gate they can just input the code I decide and could easily open the door.

adospinoiu commented 1 year ago

Hi all. I realize this item is closed, but maybe you can point me to some more resources. I used to have Xfinity Home Security ... got tired of paying for it so gave the main console back. Naturally, I'm now trying to DIY a home system with the door/window sensors (Visonic MCT-350 SMA) and keypad (Centralite 3400). I have a Raspberry Pi 3 Model B+ on which I have successfully installed Zigbee2MQTT (I followed the Linux installation "path") and bought a ZBDongle (CC2652P). I am able to pair the sensors ... it took me a while to find how to force them into pairing-mode; but I was able to get it. Zigbee2MQTT is picking up and pairing the sensors (on the front end).

For the life of me, I cannot figure out how to get the Centralite 3400 to get picked up by Zigbee2MQTT. I have tried every combination I have read of (i.e. remove batteries, hit button on back 10 times, replace batteries... no luck; hold reset button on back while placing batteries in ... no luck; etc).

I just cannot figure why the Centralite 3400 is not going into pairing-mode ... or why Zigbee2MQTT is not picking it up (just like it is the sensors).

Any guidance would by much appreciated.