Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add operation_mode and action for Niko Switches #4061

Merged
merged 3 commits into from
Apr 1, 2022

Conversation

sjorge
Copy link
Sponsor Contributor

@sjorge sjorge commented Mar 30, 2022

@sjorge
Copy link
Sponsor Contributor Author

sjorge commented Mar 30, 2022

It took some trial and error to get this all to work, the switches only send the action when in decoupled mode.
Sadly they cannot be bound to a different device or group, so it's only usable for automation in say HA or node-red.

I only still have access to the single variant, but someone with the double variant was able to confirm they could decouple it using the write convertor (this is great for debugging and testing btw! <3)

As far as I can tell the double variant just has a second endpoint that duplicates everything from endpoint 1.

@sjorge
Copy link
Sponsor Contributor Author

sjorge commented Mar 30, 2022

The omission of value 0 for the tz converter for the opperationMode attribute is intentional, the device nicely spits out an INVALID error when writing unsupported value, however if you write 0, the device soft-bricks and needs to be removed from power and then rejoined. It seemed best to not allow writes of anything not in the set of known values.

@Koenkk Koenkk merged commit d0ebc0e into Koenkk:master Apr 1, 2022
@Koenkk
Copy link
Owner

Koenkk commented Apr 1, 2022

Thanks as always 👍

@sjorge sjorge deleted the nike_switch_decouple branch May 2, 2022 07:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants