[Device Support Request] Insta GmbH Nexentro Blinds Actuator Mini #1397
Comments
|
As started by @mdeweerd (le_top) in https://community.home-assistant.io/t/does-zha-not-support-tilt-for-covers-blinds/402038 cover.py for zha component inside Home Assistant core looks to be missing tilt for covers as cover does include tilting blinds here: https://github.com/home-assistant/core/tree/dev/homeassistant/components/cover For reference it means developer need to extend ZHA cover support in cover.py for zha component inside Home Assistant core: https://github.com/home-assistant/core/blob/dev/homeassistant/components/zha/cover.py So could look at the cover.py code in some one the other integrations/components that already include tilt and copy to zha? PS: Temporary workaround until there is native tilt support for cover in ZHA could be to experiment with automations using ZHA toolkit and/or dumpfheimer framework for generic exposure of device configuration attributes. See -> zigpy/zigpy#934 and/or https://github.com/mdeweerd/zha-toolkit + https://community.home-assistant.io/t/zha-toolkit-toolkit-providing-low-and-high-level-zigbee-commands-through-zha-zigpy/373346 but that is probably more work than extending zha component cover support. |
For comparison can look at some of the other components in Home Assistant core that have already implemented tilt, like mqtt: Some other components that also already include tilt support for cover are; deconz, somfy, esphome, knx, rfxtrx, and many more: https://github.com/home-assistant/core/search?p=4&q=tilt |
|
@dmulcahey and @Adminiuga: The ZHA manifest mentiones you two as code owners. Would you be interested in implementing tilt support for covers in ZHA? And are the other problems I mentioned also features that need to be implemented in ZHA directly, or would those be things for a quirk? |
|
Thanks to the documentation of zha-toolkit I now figured out how to set the tilt position. (Btw, I would have figured this out way earlier if home-assistant/frontend#10633 would have been fixed already.) The following script works: alias: Set cover tilt position
mode: single
icon: mdi:boom-gate-up
fields:
entity:
name: Entity
required: true
selector:
entity:
domain: cover
value:
name: Value
required: true
selector:
number:
min: 0
max: 100
sequence:
- service: zha.issue_zigbee_cluster_command
data:
ieee: '{{ (device_attr(entity, "identifiers") | list).0.1 }}'
endpoint_id: 6
cluster_id: 258
command: 8
command_type: server
args:
- '{{ 100 - value }}'
(Getting the IEEE would be easier/nicer with zha-toolkit, but that's fine for me now.) Endpoint, cluster and command ids are the ones from the Zigbee standard, so nothing device or vendor specific is needed. Zigpy also already supports those as a |
|
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 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. |
|
Not resolved. The initial comment is still up to date. |
github-actions
bot
removed
the
stale
Again, be sure to check out a the related zigpy development discussion here -> zigpy/zigpy#934 Developers there discuss ideas to expose more generic device configuration attributes in an easy way for ZHA UI/GUI. |
|
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 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. |
|
Please leave this open for now. Someone is currently working on tilt support for covers in ZHA, see https://community.home-assistant.io/t/support-tilt-for-covers-in-zha/403146/5 |
github-actions
bot
removed
the
stale
|
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 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. |
FYI, this is sill being worked on, check out this draft PR for "ZHA cover tilt" support by @josef109 -> home-assistant/core#93301 |
|
I know that PR and I'd really like to see it merged. But sadly there has been no real change since May and the author doesn't respond to any messages (neither on GitHub nor in the HA forum). |
github-actions
bot
removed
the
stale
|
I've updated the first comment since HA 2023.11 now finally supports tilt for covers in ZHA. |
|
Sounds like also might still need one or both of these fixes from @tomasbedrich and @GuillaumeB-GitHub to work as it should? |
|
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 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. |
Is your feature request related to a problem? Please describe.
I bought a few "Nexentro Blinds Actuator Mini" devices made by "Insta GmbH". Those are mounted behind existing blind switches and enable the blinds to be controlled both by the old manual switches and by Zigbee (and by a config app that uses Bluetooth).
What works:
Note: Initially only one of my devices reported that correctly. The other ones always reported position as 100 and state as open. This fixed itself after I used the "reconfigure device" command on the device page.
What works unreliably:
Sometimes the open/close/stop cover services don't change the state of all devices when executed for all at once (e.g. with
entity_id: all). The actual commands are correctly sent to all devices, it's just the state shown in HA which isn't updated for all.What doesn't work:
Nothing related to tilt works.Update: Fixed in HA 2023.11. ZHA didn't support tilt for covers at all before that version.
But the cover position attribute does change correctly. And I do see zha_events being triggered when the device starts/stops the blinds. See examples below.
This might be related to ZHA : Cover states stays as Opening or Closing when using Set position home-assistant/core#98933
Describe the solution you'd like
All cover services should work. State and all attributes should be reported correctly.
Device signature
ZHA add device log
Click to show
HA log
https://gist.github.com/cremor/ba36e802502f72a4945a95e5cc55f196
(too long to embed in issue)
Example zha_events
When I close/stop/open the blinds via the manual buttons, the following zha_events are received (but HA doesn't update the entity states).
Click to show
Additional context
Source: https://www.nexentro.de/help/#open-source
Picture of the device:
The text was updated successfully, but these errors were encountered: