ZHA Develco Frient Devices

Veldkornet commented 3 years ago

The problem

I’ve paired a couple of Develco Frient devices with ZHA, and while they mostly work, the experience is not great.

In general, the devices seem to work a bit buggy compared to the other devices i have on ZHA. They are either slow to react or fail completely. Below my observations for the devices I already own:

SPLZB-131 Smart Plug Mini:

Adds 4 entities of which 1 seems to be redundant
- Sensor: switch electrical measurement
- Sensor: switch smartenergy metering
- Switch: switch on off
- Switch: switch on off 2 (this switch doesn’t work, no idea what it’s supposed to do)
ZigBee2MQTT Link

WISZB-120 Entry Sensor Pro:

Adds 4 entities where the battery sensor doesn’t seem to work and for some reason also includes a random switch??? The binary sensor doesn't seem to work either, making the purpose of this device useless basically. Actually, the only thing that does seem to work properly is the temperature sensor.
- Binary Sensor: Opening Open / Close (although it doesn’t seem to work, is always set to open)
- Sensor: Power (Should be the battery, but doesn’t seem to work)
- Sensor: Temperature
- Switch: switch on off (this switch doesn’t work, no idea what it’s supposed to do, a door sensor doesn’t even have a switch)
ZigBee2MQTT Link

SMSZB-120 Intelligent Smoke Alarm:

Adds 4 entities where the battery sensor doesn’t seem to work and for some reason also includes a random switch??? As with the door sensor, it seems that the temperature entity is the only one that actually works.
- Binary Sensor: Smoke Clear / Detected (haven’t been able to test if this actually works\0
- Sensor: Power (Should be the battery, but doesn’t seem to work)
- Sensor: Temperature
- Switch: switch on off (this switch doesn’t work, no idea what it’s supposed to do, a door sensor doesn’t even have a switch)
ZigBee2MQTT Link

MOSZB-140 Motion Sensor Pro:

Adds 8 entities. Although it seems that only the illumination and temperature work, the rest constatly are set to on (or don't seem to server a purpose).
- Binary Sensor: ias_zone (seems to be always set to on)
- Binary Sensor: occupancy (seems to be always set to on)
- Binary Sensor: occupancy2 (seems to be always set to on)
- Binary Sensor: occupancy3 (seems to be always set to on)
- Switch: switch on off (this switch doesn’t work, no idea what it’s supposed to do, the device has no switches)
- Sensor: Power (Should be the battery, but doesn’t seem to work)
- Sensor: Illumination
- Sensor: Temperature
ZigBee2MQTT Link

What is version of Home Assistant Core has the issue?

core-2021.4.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

zha

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

rbnmk commented 2 years ago

Hoping to see a quirk soon. I am not used to working with Python and Zigbee terminology so looking at the contribution guide to create a quirk only raises more questions for me. Even when comparing it with the existing ones for i.e. the smoke alarm or other devices I cannot grasp how I would realize the same for the MOSZB-140 (Frient Motion Sensor Pro). Definitely not going to Z2M for this since ZHA has been a breeze the past year.

If I can do anything, like share info or do testing. I am happy to help out.

Edit: A Day later for some reason I see more activity on my sensors. Apart from some double and unknown entities it seems to have picked up some detections, LX and temp..

HA screenshot:

jverlaan commented 2 years ago

Same issue here with the frient A/S MOSZB-140, power sensor not giving any value. Happy to test a solution if needed. On the lastest HA version core-2021.12.10

oza1701 commented 2 years ago

I have done some testing with the SMSZB-120 Intelligent Smoke Alarm and it does work for detecting smoke but not when pressing the test button. The switch do nothing so it not possible to activate the siren on other SMSZB-120 in the house so you need to set up separate sirens.

Adminiuga commented 2 years ago

Last time I've checked, the zha siren service was working fine with the smoke alarm, but it was a newer firmware. Does Develco provide firmware updates?

oza1701 commented 2 years ago

Last time I've checked, the zha siren service was working fine with the smoke alarm, but it was a newer firmware. Does Develco provide firmware updates?

Yes now it does. I didn't wait enough time so new entities showed up including siren after a few hours. It works but the siren duration is only a few seconds.

nomad-cyanide commented 2 years ago

Yes now it does. I didn't wait enough time so new entities showed up including siren after a few hours. It works but the siren duration is only a few seconds.

That is just the test-signal, not a continuous siren. According to the manual that comes along with the device, you should be able to activate the test-signal on other SMSZB-120 devices on the same Zigbee network, by pressing the test-button on one of them for 6,5 seconds. Doesn't happen here though, so not really sure what to do about that.

As for firmware, where can you download the newest one?

Veldkornet commented 2 years ago

As for firmware, where can you download the newest one?

Check on zigbee2mqtt. The latest that I know of is 4.0.2.

MattWestb commented 2 years ago

Was looking on the device type on EP 1 and its:

    DeviceType.LEVEL_CONTROL_SWITCH: ([0x0007], [0x0004, 0x0005, 0x0006, 0x0008]),

So its one light switch and have the OnOff as in = it shall making one light that can being put in one light group but is missing out cluster for doing binding as one remote. My theory is the the device is sending on command with off time then doing test but its missing the group cluster for configuring it all the way.

Test making one light group and trying adding the devices in it and see if the is sending and reviving the OnOff commands and if its not working doing sniffing what the device is sending then pressing the test button.

Edit: If group adding is not working add one in group cluster on EP1 in the replace part and look if its accepting commands / attributes on it.

oza1701 commented 2 years ago

Ok on the zigbee2mqtt page they mention a configuration for duration and its seems to be missing in the configurations available in ZHA

duration: the number of seconds the alarm will be on

I am a noob on Zigbee and ZHA so forgive me if I'm asking things that might be obvious...

I can always do a work around by setting up an automation that activate the siren every 10 seconds.

Edit: I also run the latest 4.0.2 firmware

nomad-cyanide commented 2 years ago

I'm running ZHA and have added this to my configuration.yaml:

zha:
  zigpy_config:
    ota:
      otau_directory: /config/zigpy_ota

(based on this: https://www.home-assistant.io/integrations/zha/#ota-firmware-updates)

In /config/zigpy_ota/ I have placed the ED_Smoke_Sensor_SSIG_4.0.2.zigbee file. (Firmware download: https://github.com/Koenkk/zigbee-OTA/tree/master/images/Develco)

Now if I look at Device Info for one of the SMSZN-120 devices it states:

Firmware: 0x00040002

Is it correct to assume, that the device is running the 4.0.2 firmware or is there some other way I should confirm this?

byrongamatos commented 2 years ago

My frient smoke alarms are also on firmware: 0x00040002 but still nothing works. Are there steps to take to try to fix this?

mvdkleijn commented 2 years ago

I'm having the same problems with the Frient smoke alarm. Entities show up in home assistant but nothing seems to work, apart (maybe) from the battery and the temperature sensor.

Is this something someone is actively working on (no pressure, just asking) or would I be better off buying a different fire alarm?

I'd prefer not going the zigbee2mqtt route. Though that works (from what I hear), the zha route seems better for me.

Ditskys commented 2 years ago

So I have 2 of the frient smart smoke alarms and a frient heat alarm. Adding to HA via ZHA and a conbee I get as attached. I can trigger siren, a random switch and some settings that dont seem to do anything. Screenshot_20220605-163141_Home Assistant

mvdkleijn commented 2 years ago

So I have 2 of the frient smart smoke alarms and a frient heat alarm. Adding to HA via ZHA and a conbee I get as attached. I can trigger siren, a random switch and some settings that dont seem to do anything.

So basically the same as me from what I gather. I assume that triggering the siren does nothing?

Ditskys commented 2 years ago

Triggering siren works for me! But the other options and the random switch does nothing!

Ditskys commented 2 years ago

The thing I would like to do but can't is trigger it so that when one siren goes off, it triggers others to go off as well. Any ideas?

oza1701 commented 2 years ago

You need to create an automation for that.

mvdkleijn commented 2 years ago

Triggering siren works for me! But the other options and the random switch does nothing!

interesting... for me nothing works but the battery level

ark- commented 2 years ago

Not working for me and my smart heat alarm either, happy to share logs if needed. Sometimes it pairs, usually it doesn't, when it does pair options are available but do nothing, e.g. the siren trigger.

Seems like the zha-device-handlers are happy it's implemented properly, here: https://github.com/zigpy/zha-device-handlers/issues/854

zeus86 commented 2 years ago

I had the same Problem described in the initial post.

Turns out, my LQI-Value is very low on this device (zigbee-dongle at HA-Instance is only a few meters and one wall away), reporting an LQI of 30. After placing the siren directly next to the dongle, and triggered a reconfiguration, i noticed that actually some of the checkmarks turned from yellow to green (by far not all of them), and even more interesting, after doing so, the siren-toggleswitch actually works now and the LQI has risen to ~66 (i am on homeassistant docker 2022.8.6).

mvdkleijn commented 2 years ago

I've also noticed a very low lqi (in the 30s) and am now waiting for some plugs to arrive that can work as repeaters.

It feels like the Frient devices have very poor zigbee transmitters.

zeus86 commented 2 years ago

yeah, the smoke detector is basically sitting in plain view to the dongle, for that, the lqi is far to low. beside that, i think the temperature sensor is also not working correctly. it shows a value (which seems to be halfway realistic), but it doesn't change at all. straight line over several days beside some window-open-cycles...

mvdkleijn commented 2 years ago

I find the same behavior for me. Flat line temperature. LQI improved a little, but still not great.

ark- commented 2 years ago

Hmm tried re-pairing with the same results.

I much prefer ZHA but I've been toying with the idea of having a 2nd Zigbee coordinator (I have a spare) using Zigbee2MQTT. This means for compatibilities sake I can use Z2M for edge case devices such as this and some Tuya thermostats I have but don't need to port everything over. Just a thought for others on here.

mgraeuler commented 2 years ago

I have two SMSZB-120 and I'm experiencing the exact same issues as others via ZHA: I had hoped to use these to control my heating, but they are showing a flat temperature and neither of my two devices is updating. Reconfiguring them doesn't help and LQI is arount 90/255 although the device is right next to the controller (SONOFF Zigbee 3.0 USB Dongle Plus,TI CC2652P + CP2102N via Raspberry Pi 4). I removed the battery from one of the SMSZB-120's and re-paired the other one, but to no avail.

Technical Manual: https://www.develcoproducts.com/media/1742/smszb-120-technical-manual-smoke-alarm.pdf

cpt1gl0 commented 2 years ago

Also for me temperature seems to be stuck at the value from when the device was pairing.

ChristophCaina commented 1 year ago

Hi all, I also have a frient intelligent heat alarm.

The Siren Switch does work as expected - it does trigger the alarm on the device. In that case, the binary sensor will also be set to "on"... So the binary sensor will show an active alarm.

I don't yet know, what the "switch" might do - haven't tested that so far, and also, I haven't test other settings like "alarm sound, alarm level, etc...

Regarding the IASZone Binary Sensor: As far as I understood the documentation, this should be active, when the device detected an alarm (not triggered by the testing push-button or via the alarm switch).

I've received some documentation from the frient - I can attach them, if this might help to improve either the integration of the device, or others?

oza1701 commented 1 year ago

I've received some documentation from the frient - I can attach them, if this might help to improve either the integration of the device, or others?

Yes please!

ChristophCaina commented 1 year ago

Heat Alarm datasheet v2.7_0.pdf HESZB-120 Technical Manual - Heat Alarm.pdf

pvandegeer commented 1 year ago

Anyone has better results with the 4.05 firmware for the smoke detectors? I bought a 3-pack a couple of months ago and only one of them shows the proper temperature. The other two basically show the same temperature al the time. After upgrading the firmware just now, the temperature changed, but it looks as though it is again fixed to the new temperature.

mvdkleijn commented 1 year ago

Anyone has better results with the 4.05 firmware for the smoke detectors? I bought a 3-pack a couple of months ago and only one of them shows the proper temperature. The other two basically show the same temperature al the time. After upgrading the firmware just now, the temperature changed, but it looks as though it is again fixed to the new temperature.

How did you check your firmware version and how did you upgrade it?

pvandegeer commented 1 year ago

The firmware version is shown with the device info in Home Assistant. Firmware: 0x00040004 for v4.04.

I've followed the guide here: https://github.com/zigpy/zigpy/wiki/OTA-Device-Firmware-Updates Firmware can be found here: https://github.com/Koenkk/zigbee-OTA/raw/master/images/Develco/ED_Smoke_Sensor_SSIG_4.0.5.zigbee

When triggering the firmware update manually, follow the example in the wiki but use endpoint_id 35 instead of 1.

service: zha.issue_zigbee_cluster_command
data:
  ieee: 00:15:bc:00:31:01:00:00   <--- your ieee here
  endpoint_id: 35
  cluster_type: out
  command_type: client
  cluster_id: 25
  command: 0
  args:
    - 0
    - 100

On a side note: after resetting, recoupling and moving one of the updated device to a warmer room, it is now displaying correct temperatures it seems. The other one is in an update loop however and is still at 4.04.

mvdkleijn commented 1 year ago

@pvandegeer Thanks for you hints! I followed what you did and what the instructions said with the change that I updated using the GUI method.

For some reason the service method kept complaining about deprecated arguments.

Anyway, it took a good long while to update but it successfully installed 4.0.5 on my 1st smoke detector.

This did not fix anything until I enabled the temperature entity and hit "reconfigure" on the sensor's device overview.

The second smoke detector automatically updated its firmware overnight so I hit its reconfigure button too and its temperature started working.

What I did notice it that the reconfigure works but sometimes parts of it fails.

Also the LQI is still terrible for bot devices. One is at the far end of the house so that makes sense but the other is right next to the controller and still only does 120 LQI. (which is about 50% dropped packets I believe)

Adminiuga commented 1 year ago

What I did notice it that the reconfigure works but sometimes parts of it fails.

These are battery operated devices and may sleep. Keep device awake when reconfiguring, like pressing a button every other second

pvandegeer commented 1 year ago

All of mine are now reading the temperature after the firmware update. :)

mvdkleijn commented 1 year ago

What I did notice it that the reconfigure works but sometimes parts of it fails.

These are battery operated devices and may sleep. Keep device awake when reconfiguring, like pressing a button every other second

I realize that @Adminiuga but the sync/connect button on the back didn't seem to have any effect and the only other button activates a particularly loud siren which I wasn't in the mood to do. :smile:

Any way, for me the same as @pvandegeer .. all temperature sensors now work and all I did was reconfigure, not re-pair.

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

home-assistant / core