I hardcoded the IEEE in the first place, since HA prompted it wouldn’t support templates in services.
Instead, I tried accessing the cluster command via device infos → manage zigbee device. I got the same result.
So maybe the roller shutter isn’t handling the command correctly?
cremor
April 15, 2023, 11:53am
26
So you get the same error when using the following things?
The zha.issue_zigbee_cluster_command
service
The “manage Zigbee device” interface
The new tilt ZHA feature developed by @josef109
If yes, then I’d say your device isn’t handling the Zigbee command correctly. Because for me (with the “Nexentro Blinds Actuator Mini” device) all those 3 things work fine.
So NodOn support claims, this might be due to Home Assistant. But shouldn’t the cluster command be the same no matter what hub I use?
cremor
April 19, 2023, 4:39pm
28
ZHA uses the default cluster commands from the ZigBee standard. It could be that the device supports tilt commands via ZigBee, but doesn’t follow the standard. Meaning it uses different cluster ids or commands ids.
This happens quite often and is the reason why the GitHub - zigpy/zha-device-handlers: ZHA device handlers bridge the functionality gap created when manufacturers deviate from the ZCL specification, handling deviations and exceptions by parsing custom messages to and from Zigbee devices. repository exists. You could try creating an issue there.
Is your device one of those?
https://www.zigbee2mqtt.io/devices/SIN-4-RS-20.html
https://www.zigbee2mqtt.io/devices/SIN-4-RS-20_PRO.html
If yes, then that would also hint towards non-standard tilt commands. Because that pages don’t mention tilt. If you compare them with the page for my device , then you’ll see that it mentions tilt.
(Note: Those pages are from Zigbee2MQTT. That’s not directly relevant for ZHA, but can be a good indicator for supported features of devices.)
If you can figure out which cluster ids or command ids your device uses for tilt commands then you could create a script like the one I posted above and use that until a device handler is implemented for your device.
Thanks for your detailed answer. I’m using SIN-4-RS-20. NodOn claims tilt support on their website and customer support assured me they were working on further compatibility. I’ll try and ask them about the used cluster commands.
Apparently, NodOn use custom attributes for tilt runtime calibration. Those aren’t accessible via the Home Assistant interface, as far as I can tell. Is there another way to access these attributes in order to calibrate the runtime?
cremor
April 26, 2023, 3:00pm
31
Unless a ZHA device handler is implemented your only way is to use a custom script like the one I posted in post #22
cremor
May 17, 2023, 9:10pm
32
@josef109 Why did you close the PR? Will you create a new one?
cremor
June 17, 2023, 9:53am
33
@josef109 I found your new PR and saw that it is still in draft state and a few changes were requested. Do you plan to continue working on it?
Hedda
(Hedda)
September 22, 2023, 10:58am
34
mhoff
(Michael Hoffmann)
October 17, 2023, 8:33am
35
I have been running and testing ZHA cover tilt by josef109 · Pull Request #93301 · home-assistant/core · GitHub as custom integration for a few weeks now. It works extremely well, I have not seen any problem so far. I really wonder why ZHA does not support window blinds with tiltable slats (as other cover implementations do e.g. Z2M or Zwave).
I think the tilt support is essential for using ZHA cover.
I know it’s hard to understand if you don’t have such “Venetian blinds” , but they are very common in office buildings and modern energy efficient houses with large windows where you need to control solar heat with the tilt function of the cover (We spent €400 more per window in our new house to have tilting blinds as opposed to roller blinds. )
@josef109 awesome work, thank you very much. (I own you a beer)
I see you still regularly update this PR by merging HA:dev. Can you please go the last step and get the missing things done?
Is there anything I can help?
Greetings from Halle,Germany - Michael
Hedda
(Hedda)
October 20, 2023, 10:24am
36
FYI, there is a new pull request for this by @tomasbedrich to ZHA integration in Home Assistant core:
home-assistant:dev
← tomasbedrich:tomasbedrich/zha-cover-tilt
opened 06:49PM - 15 Oct 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
This PR adds support to control cover tilt as defined in Zigbee Cluster Library Specification (rev 8) 7.4.2.1.2.9.
There are multiple devices waiting for this support:
- Ubisys J1
- NodOn SIN-4-RS-20
- [Insta GmbH Nexentro Blinds Actuator Mini](https://github.com/zigpy/zha-device-handlers/issues/1397)
This PR is a duplicate of #93301, which is currently stale despite our numerous attempts to contact the author @josef109.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: [zha-device-handlers#1397](https://github.com/zigpy/zha-device-handlers/issues/1397)
- This PR is related to issue: #93301
- Link to documentation pull request: <none>
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
mathias1
(Mathias)
October 29, 2023, 7:16am
37
Awesome work. Is it already included in the latest release of Home Assistant? I am on 2023.10.5. Or do I have to go for a beta release? I’m using couple Nexentro Blind Actuators to control my Venetian blinds, but at the moment none of the the new tilt services is availabe in Home assistant. Do I have to remove them from my zigbee network and add them again, to make this new function work?
cremor
October 29, 2023, 8:29am
38
The PR was just merged 5 days ago, so it is not in 2023.10.5. It looks like it is available in 2023.11 beta, although the beta release notes don’t mention it yet.
cremor
October 30, 2023, 9:00am
39
@frenck According to GitHub you created the releases 2023.11.0b0 and 2023.11.0b1, so maybe you can answer that. It looks like PR #102072 was already included in 2023.11.0b0, but is not mentioned in the release notes (and doesn’t have a milestone assigned on GitHub). Was it missed?
mhoff
(Michael Hoffmann)
November 2, 2023, 8:54am
40
#102072 is in the release 2023.11
@tomasbedrich @josef109 Thanks for all your work
(and goodbye to my custom ZHA)
1 Like
Hello!
Can you help with a question?
I have the NodOn SIN-4-RS-20 which are called out as supported in 2023.11. However these devices are made for rolling blinds (up/down only) and don’t believe they really support tilt.
I now have 2 separate sliders - one of which doesn’t really do anything (the tilt).
Is there any way in the device or HASS settings I can remove the tilt slider?
Thx!
1 Like
jhoff80
(Joe)
December 29, 2023, 7:30pm
42
Anyone figure this out yet? I’ve got 5 identical Ikea Fyrtur blinds. 1 of the 5 thinks it supports tilt even though it doesn’t.
Additionally I’ve got 2 of the Ikea Tredansen blinds, 1 of the 2 thinks it supports tilt even though it doesn’t.
All 7 of these run the same firmware version.
I know it is annoying, but until there is a better solution, tilt can be disabled using customize
: Disable tilt - #4 by julienhd
1 Like
danist
(Daniel)
January 2, 2024, 12:05pm
44
Hi
The NodOn seems to support tilt. Because at least Zigbee2MQTT supports tilt for the NodOn SIN-4-RS-20 according to this
Therefore I assume the error must be elsewhere, either on your side or in the ZHA support for tilt.
I can confirm that ZHA tilt support for the Insta Nexentro Blinds Actuator Mini works. This device has been part of the same PR as the NodOn device:
home-assistant:dev
← tomasbedrich:tomasbedrich/zha-cover-tilt
opened 06:49PM - 15 Oct 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
This PR adds support to control cover tilt as defined in Zigbee Cluster Library Specification (rev 8) 7.4.2.1.2.9.
There are multiple devices waiting for this support:
- Ubisys J1
- NodOn SIN-4-RS-20
- [Insta GmbH Nexentro Blinds Actuator Mini](https://github.com/zigpy/zha-device-handlers/issues/1397)
This PR is a duplicate of #93301, which is currently stale despite our numerous attempts to contact the author @josef109.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: [zha-device-handlers#1397](https://github.com/zigpy/zha-device-handlers/issues/1397)
- This PR is related to issue: #93301
- Link to documentation pull request: <none>
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
So I guess it should be working on the ZHA side for NodOn.
Cheers