-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frient/Develco smoke detector - can't turn off alarm with switch #8321
Comments
Updated to 1.21.0-dev commit: f9451ff which has several fixes to the smoke detector Koenkk/zigbee-herdsman-converters#2895, however it didn't solve the HA switch. @TheStigh (sorry for tagging you on all my Develco/Frient issues), do you run Home assistant? Have you experienced the same? |
Yes, using Home Assistant. It appear as a switch in the Z2M UI -> exposes but does the same here. @Koenkk How can I resolve this? Remember earlier where a binary became a switch, can this be related to that change? |
Since I have several siren entities my plan is to put everyone in the same HA area. Then I think I would be able to use the service The switch in Z2M UI works just fine. |
Or you could use an automation to trigger all if a singe one are triggered (just work with actual smoke alarm, not the "alarm" :"START") |
Develco HESZB-120 fire detector doesn't expose siren as a switch in HA.. Am i missing something? Converters where updated only for the develco smoke detector? |
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 |
I think the |
Obviously it is possible to run both |
@rindlerblabla Can I ask how often your smoke sensors are reporting to zigbee2mqtt? One sensor (grep enrolled): info 2021-10-01 15:53:05: MQTT publish: topic 'zigbee2mqtt/FrientSmokeAlarm1/enrolled',
info 2021-10-01 16:19:46: MQTT publish: topic 'zigbee2mqtt/FrientSmokeAlarm1/enrolled', payload 'true' |
@artur3 Guess mine are updating with about the same interval. Set up a counter and in one hour it updated 21 times. |
@rindlerblabla No problems with battery life? |
Dot know yet. Have only had them for about 3 months. The one reporting lowest value is now at 2900V. |
Maybe the temperature of the area you installed them changes too
frequently.. Check that. You can change minimum interval and/or temperature
change
…On Fri, 1 Oct 2021, 20:38 rindlerblabla, ***@***.***> wrote:
Dot know yet. Have only had them for about 3 months. The one reporting
lowest value is now at 2900V.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8321 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANVCNGFDQWIWWFSVFRM2DNTUEXWZBANCNFSM5B32ZWTA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Obviously this is fixed. nurikk/zigbee2mqtt-frontend#874 |
@mamrai1 Many reports have same temperature. zigbee-herdsman-converters/devices/develco.js |
Can this be changed directly in zigbee2mqtt configuration file? |
Zigbee2MQTT has a built-in webbased frontend. To enable the frontend add the following to your configuration.yaml: frontend: Optional, default 8080port: 8080 Optional, default 0.0.0.0host: 0.0.0.0 Optional, enables authentication, disabled by defaultauth_token: your-secret-token |
Thanks. |
min max change Result, reports every 5min or less, regardless of settings:
Should I submit a bug report? |
It is also sending keep alive messages every 15 minute https://www.develcoproducts.com/media/1742/smszb-120-technical-manual-smoke-alarm.pdf
Maybe @TheStigh knows more about whether it's a bug or not. |
This discussion past days obviously has nothing to do with the name of the thread. If you want me to check something, please make a question. Regarding Frient - I assume it is exactly same HW and uses same firmware as original Develco. What I don't know (as I don't have a Frient device, only original Develco's) are how it checks for firmware update and can read a Develco-firmware file. When it comes to the Keep Alive, this is part of the IAS, and as @rindlerblabla referenced, it tells the PAN coordinator it is still there. When it comes to reporting, you can always customize these for your personal taste through the Z2M UI. |
@TheStigh No, sorry for not being clear, and it's off topic in this issue, but the question being raised is whether it is a bug that the device is updated more often than what the interval is set to even if no value has changed, see #8321 (comment). |
@TheStigh I tried changing the reporting interval in the Z2M UI. Now it is less frequent, but far from configured. Please see my post above. I will have another Frient smoke detector soon. I can send it to you. @rindlerblabla Keep alive should be 15 minutes, mine reports every 5 minutes. |
I worked around this by calling the MQTT_PUBLISH service. So my button is
Change the payload to OFF to turn off the alarm. The reason behind this I think is the device does not publish the alarm status as per the docs. |
And as stated in #8321 (comment) it is possible to to it like this in HA as well. |
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 |
I have the same Problem... |
What happened
Since recently sirens are exposed to Home assistant as switches. Tried that function right now with some Frient smoke detectors. When I toggle the switch in Home assistant, the switch just toggles back directly to off. The alarm goes on, but I cannot turn it off with the switch, since it's already off according to the UI. Have some Tuya sirens as well, and they behave just fine.
Debug Received MQTT message on 'zigbee2mqtt/Brandvarnare hall/set/alarm' with data 'START'
Debug info
Zigbee2MQTT version: 1.21.0-dev commit: 33ee9f7
Adapter hardware: Zzh
Adapter firmware version: 20210120
The text was updated successfully, but these errors were encountered: