Zigbee garden irrigation device ( Solenoide valve ) not fully supported by ZHA integration

Hi,

I bought this zigbee garden irrigation device ( Solenoide valve ) … Electrovanne et programmateur d'arrosage Zigbee avec mesure - SASWELL [SAS980]

This has been integrated in 2022.7 ZHA integration but the water measurement is not working at all ( no sensor)

Enclosed the log and the screenshot of the device information :

Logger: homeassistant.components.zha.core.channels.base
Source: components/zha/core/channels/base.py:486
Integration: Zigbee Home Automation (documentation, issues)
First occurred: July 27, 2022 at 11:10:56 PM (6 occurrences)
Last logged: 2:45:48 PM

[0x9733:1:0x0008]: async_initialize: all attempts have failed: [DeliveryError('[0x9733:1:0x0008]: Message send failure'), DeliveryError('[0x9733:1:0x0008]: Message send failure'), DeliveryError('[0x9733:1:0x0008]: Message send failure'), DeliveryError('[0x9733:1:0x0008]: Message send failure')]
[0x118F:11:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0x118f:11:0x0006]: Message send failure'), DeliveryError('[0x118f:11:0x0006]: Message send failure'), DeliveryError('[0x118f:11:0x0006]: Message send failure'), DeliveryError('[0x118f:11:0x0006]: Message send failure')]
[0x9733:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('[0x9733:1:0x0006]: Message send failure'), DeliveryError('[0x9733:1:0x0006]: Message send failure'), DeliveryError('[0x9733:1:0x0006]: Message send failure'), DeliveryError('[0x9733:1:0x0006]: Message send failure')]
[0xC69F:1:0x0001]: 'async_configure' stage failed: 'uint8_t' object is not subscriptable
[39174:1:0x0001]: 'async_configure' stage failed: 'uint8_t' object is not subscriptable

Please any advice ?
Thank you

There were/are multiple threads on the french hacf pages, try there. The saswell page has one review, stating exactly that…no consumption exposed. You could also try zigbee2mqtt…not something you would like to here but there it seems supported … I would try in a dev-env first
RTX ZVG1 control via MQTT | Zigbee2MQTT

All in all, if the device does not send it, also z2m will not show it

Thanks @vingerha for your answer but some progress in HA Core 2022.8

I want to stay with ZHA so i think i need to write a PR for this problem

Hi,
Did you succeed to get the battery level and/or water flow ?
Can you share your solution if any ?
Thanks.
Cray

Hi @cray19003

No change . A PR has been issued … Zigbee garden irrigation device ( Solenoide valve SASWELL SAS_SAS980) not fully supported by ZHA integration · Issue #76797 · home-assistant/core · GitHub

If a device already have a quirk for ZHA then post a new issue with bug report that includes information + debug logs needed for troubleshooting here → https://github.com/zigpy/zha-device-handlers/issues

It is likely your device was shipped with a different firmware version which has changed the behaviour or attributes and parameters to the existing quirk need to be updated to match that, read → https://www.home-assistant.io/integrations/zha#zha-exception-and-deviation-handling

For deeper information and overview how “quirks” (ZHA Device Handlers) actually work read more here → https://github.com/zigpy/zha-device-handlers/blob/a072ca3a99acc3744e74ef0b9d40d30d86adeead/README.md

FYI, “PR” is the wrong terminology/work to use as “PR” stands for “Pull Request” meaning you have submitted code with a request to commit your code. But you have reported and issue, not submitted code to the zha-device-handlers (zha-quirks) library/project via Git/GitHub… Using the term “PR” would imply you are a developer that will code this yourself and then contribute that code to the needed upstream libary/project by submitting a pull request via Git/GitHub.

Thanks @Hedda for your valuable inputs.

In fact an issue was opened in the github of home assistant/core and not a PR.

This issue " ZHA integration #76797" has been closed without explaination

Please re-read my post and instead open a new bug report issue to the zha-device-handlers repository on GitHub where the fix is really needed → https://github.com/zigpy/zha-device-handlers/issues as ZHA in Home Assistant core depends on zha-device-handlers for device specific quirk/quirks fixes.

Hi @Hedda ,

Got it !

There is an existing issue report in the zha-device-handlers repository on GitHub

[Device Support Request] SASWELL SAS980SWT-7-Z01 (_TZE200_akjefhj5, TS0601) Smart Irrigation Valve · Issue #1668 · zigpy/zha-device-handlers · GitHub

I will look at it

EDIT : I can see from above that you have put a lot of effort to improve the zigbee project
Thank you

I have opened a new issue in the zha-device-handlers repository on GitHub as suggested by @Hedda

Hi all,
The last discussion on this topic is now 6 months old. I see on the Github page that some of the requests seem to be have been closed, but not sure what is the latest status on this subject.
For sure, when I include the device through ZHA here, I have very limited data beyond the switch. Battery levels for instance doesn’t show up, while on the Github discussions, some users seem to have this available.
Can anyone help me with the latest on this subject?
Thanks in advance

Post your input/feedback to device feature request issue @gerardsamara opened and linked above:

Thanks Hedda,
I was actually asking the question as I see several threads on Github related to that same integration:

I was therefore wondering if any of those had been resolved at all.
Sorry, I am not a great expert of Github, and it is not easy to follow the discussions and status of the various requests.
Thanks in advance

Zigbee devices that do not only use standard configuration and parameters (default ZCL clusters and attributes) but instead also implement custom manufacturer clusters and attributes (also known as “quirks”) will need a custom handler/converter/parser/translator as Python script code in the upstream “ZHA Device Handlers” library repository to extend custom manufacturer device “quirk” support for specific non-standard ZCL clusters and attributes (which Zigbee gateway implementations that depends on zigpy and the ZHA Device Handlers library, like Home Assistant s ZHA integration, then can make use of).

https://github.com/zigpy/zha-device-handlers/#readme

If you can not code that Python script code yourself to write the needed custom handler/converter/parser/translator for adding that specific device to the “ZHA Device Handlers” repository/library then you should normally submit a new “device support request” (with device signature and diagnostic information) as new issues → https://github.com/zigpy/zha-device-handlers/issues

However since there is already an open device support request suggest you add your details to that existing issue → https://github.com/zigpy/zha-device-handlers/issues/1837

Without people posting in a such “device support request” as an issue posted to the “ZHA Device Handlers” repository/library requesting support for an unsupported device or device feature with Device signature and Diagnostic information the ZHA integration developers will not even know about the device unless they by random chance happened to have bought it themselves.

The reason is why non-standard devices need a custom handler/converter/translator is explained in ZHA integration documentation here → https://www.home-assistant.io/integrations/zha#zha-exception-and-deviation-handling

Zigbee devices that use clusters and attributes that are standard in the official ZCL (Zigbee Cluster Library) do not need custom handlers/converters/translators as explained in the ZHA integration documentation here → https://www.home-assistant.io/integrations/zha#knowing-which-devices-are-supported

PS: Off-topic but FYI, this also works kind of similarly for Zigbee2MQTT which also requires a custom handlers/converters/parsers/translators for specific devices → https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html

1 Like