Open tommyjlong opened 7 months ago
Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
zwave_js documentation zwave_js source (message by IssueLinks)
The following may be indicative of problems caused by state always being "unknown".
The Group shown has two Window Covers horizontal slats as members of the group. Each horiz slat has current_tilt_position=0. The Group also has current_tilt_position=0 but notice the icon in the lower right "Preview" showing the blinds as being open.
And here is what the icon looks like (its showing open) for one of these Window Coverings Horiz Slats that has tilt postion = 0
Is there an owner for this?
this is primarily a Home Assistant limitation that leaves the state as unknown. The state of a cover entity is based on its position, not its tilt, so a tilt only cover does not have a state. You can see my architecture discussion/proposal here related to this: https://github.com/home-assistant/architecture/discussions/908
Is there a fix for this horizontal slat issue? Does it only affect iBlinds products? My iBlinds have been working for several years now. But adding a new iBlinds device introduced this crippling problem for the new blind.
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.
Still waiting for a good fix on this as well....
Yeah let's keep this open until the architectural decision has been worked out.
I prototyped some of the different proposed solutions from the architecture threads linked above in branches (1C, 2A). Personally, I have been running the 1C option at home with my iBlinds for a few months now and generally happy with it (but YMMV). It's been on my todo list (though realistically not anytime soon) to check how well it works with automations like https://github.com/basbruss/adaptive-cover , before pushing it further.
The problem
cover.xxxxx_horizontal_slats_angle
Always showsunknown
state.Somewhere along the way, ZWavejs and/or iBlinds changed how the horizontal slats are controlled and managed. The Window Covering v1 CC is now being used and has replaced the MultiLevel CC. After having ZwaveJS-UI re-interview one of my iBlinds, this conversion took place automatically. The result is the entity cover.xxxxx that seemingly was associated with the MultilevelCC is no longer available, and a new entity cover.xxxxx_horizontal_slats_angle was created.
The new entity cover.xxxxx_horizontal_slats_angle can actually control my blinds, but the state is always
unknown
.I'll reference a few discussion I have come across on this topic: https://github.com/home-assistant/core/issues/103268 https://github.com/zwave-js/node-zwave-js/issues/5686 https://github.com/home-assistant/architecture/discussions/908 https://github.com/home-assistant/architecture/discussions/979
What version of Home Assistant Core has the issue?
Version core-2023.12.3 Installation Type Home Assistant OS Development false Supervisor true Docker true User root Virtual Environment false Python Version 3.11.6 Operating System Family Linux Operating System Version 6.1.63-haos CPU Architecture x86_64 Timezone America/New_York Configuration Directory /config
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
zwavejs
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response