Skip to content

Updated Develco SMSZB-120 to 4.0.5 #220

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

Merged
merged 1 commit into from
Dec 28, 2022
Merged

Updated Develco SMSZB-120 to 4.0.5 #220

merged 1 commit into from
Dec 28, 2022

Conversation

TheStigh
Copy link
Contributor

Updated Develco SMSZB-120 to 4.0.5

@Koenkk
Copy link
Owner

Koenkk commented Dec 28, 2022

Thanks!

@Krzysztonek
Copy link

Krzysztonek commented Dec 29, 2022

HI @Koenkk ,
I've just updated my Frient SMSZB-120 to 4.0.5. However, since then I see many false positives(?) on this device.
I tried to remove this device from my Z2M list, and join it again from scratch. It brings no result: the siren is being activated from time to time (once per 3-4 minutes) without any visible reason. From now on, the only thing I can do is pressing the cover knob of the device to stop the siren for a while, but only for a while. After a few minutes, the siren is blaring again.
This is what I never met in the past, before installing this firmware 4.0.5 update.

Can you, please, advise?

I also noticed one possible discrepancy: firmware version (4.0.5) VS firmware build date (20.08.2021)
image
Is that OK?

@Koenkk
Copy link
Owner

Koenkk commented Dec 30, 2022

@TheStigh do you experience the same issues with this fw?

@RonniHolst
Copy link

I have the same as @Krzysztonek wrote here!! Not good for the wife factor :(

@TheStigh
Copy link
Contributor Author

@Krzysztonek @RonniHolst

Can you please confirm if you tested the warning before this did happen?
Or did you simply do the update and did not touch anything and the siren suddenly started?

There was introduced a "bug" where the {alarm:OFF} didnt' work. This is fixed and there are a PR for this.

Also, can you please inform what coordinator you guys are using?

@TheStigh
Copy link
Contributor Author

@TheStigh do you experience the same issues with this fw?

No, I dont. Though, I have an original Develco SMSZB-120.
I've talked to others last night with Frient where this did not happen, unless they tried the warning first hand (similar to pressing START from exposes).

@Krzysztonek
Copy link

I also haven't tested the warning before, just simply did the update, touching nothing else.
My coordinator is: usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DExxxxxxx-if00

@TheStigh
Copy link
Contributor Author

Conbee II again. I dont have this coordinator and cannot test. I test on a zzh & Sonoff coordinator.
I cannot conclude, but in my mind the Conbee II causes many issues with Z2M users. I might be wrong. But the initial thought when these errors was written was "they probably got a Conbee II".

@Koenkk Any thoughts or comments on Conbee II?

Have in mind - I don't make the firmware, I just publish it after receiveing the file from Develco.

@RonniHolst
Copy link

@Krzysztonek @RonniHolst

Can you please confirm if you tested the warning before this did happen? Or did you simply do the update and did not touch anything and the siren suddenly started?

There was introduced a "bug" where the {alarm:OFF} didnt' work. This is fixed and there are a PR for this.

Also, can you please inform what coordinator you guys are using?

Yes I did test the warning - and was able to stop it again. But then I have had another device, and that just started beeping doing the night, and the only way I was to stop it was clicking on device. But a few minutes after it did start again..

So I am trying to downscale the firmware again, because I am also using the sirene for alarm at my house

@Krzysztonek
Copy link

Hi @RonniHolst

So I am trying to downscale the firmware again

How to perform the firmware downgrade? How should it be done? Never did it before... I even don't see such option in Z2M add-on. Any step-by-step hint?
I haven't saved the previous firmware... so maybe this is not feasible in this case?

@RonniHolst
Copy link

Hi @RonniHolst

So I am trying to downscale the firmware again

How to perform the firmware downgrade? How should it be done? Never did it before... I even don't see such option in Z2M add-on. Any step-by-step hint? I haven't saved the previous firmware... so maybe this is not feasible in this case?

I dont know all about it - but if you are using Home Assistant, then you can use
Koenkk/zigbee2mqtt#15795 (comment)

@waroen
Copy link

waroen commented Dec 30, 2022

@TheStigh My Frient doesn't suddenly start it's siren. It does however no longer show the firmware revision after update. Shall try tomorrow to take it down and see if a can re-interview it properly. If not I'll remove and add again and see if that fixes it.

@TheStigh
Copy link
Contributor Author

@TheStigh My Frient doesn't suddenly start it's siren. It does however no longer show the firmware revision after update. Shall try tomorrow to take it down and see if a can re-interview it properly. If not I'll remove and add again and see if that fixes it.

First everybody should do if a device change behavior are to do a re-configure. If that doesn't work, delete it from Z2M using Force, restart Z2M and re-add it.

It works now on 4.0.2, 4.0.4 and will work as normal on 4.0.5 when the January release of Z2M are out. Tested on both original Develco and Frient.

@Krzysztonek
Copy link

will work as normal on 4.0.5 when the January release of Z2M are out

This is really good news for the New Year! If so, then I won't do a firmware downgrade. For this time being, I'll temporarily remove the battery from my device, hoping that no fire will unleash by then.. ;)
Impatiently awaiting a new release of Z2M :)

@Krzysztonek
Copy link

I've just updated my Z2M to the last version 1.29.0-1. Now my Frient works fine for me. So far, so good!
Thank you! <3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants