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
[Device support request] Heiman remote control HS1RC-M #2697
Comments
Hi @SwoopX, do you have a confirmation from the web app that you were able to add the remote? I followed your instruction by adding 0x0501 but can only see the device on the VNC/phoscon. Not able to see any new device or events but can see it appears on the logs |
Yeah, you get a confirmation, at least I got one. However, that remote is pretty much unusuable. It uses IAS ACE commands which deconz has no logic for. And that's unfortunately nothing to be added like in 5 mins. Thinking about bending to towards a regular remote, if that's feasible. |
I've made an update so it can be used as a regular remote to the extend feasible. It should be available as a switch and allows 4 short press button events. |
great, thanks. I'll test it as soon as it releases and appears on hass add-on since I don't have any dev environment for it. |
I've added the new endpoint and can see the device in deconz-gui but there is no home automation software which shows the remote. I've tried domoticz and iobroker. |
Unfortunately I have the same issue here on my side.. Shown in deconz, but nothing in the REST API or Home Assistant.. |
Hm, then it seems like I have to take another look. I'll do a new test with a fresh device database. Maybe a line got lost somewhere... |
Closing this as PR has been merged. Supported with .78 |
Power cluster
For the remote to properly join, the coordinator has to be extended by "IAS ACE" cluster manually in deconz GUI. For that, go to Edit -> Network settings -> Endpoints (or press F9 -> Endpoints) and add
0x0501
to thein clusters
of endpoint 0x01.After successful join, the device sends IAS ACE commands on all its buttons as below:
Top button: Arm Mode - Arm Day/Home Zones Only
Right button: Arm Mode - Disarm
Bottom button: Command - Emergency
Left button: Arm Mode: Arm All -Zones
Update:
I've modified the device to be exposed as a switch via REST API, so it now issues 4 "normal" button events. Presumably not really usable with Phoscon, but with other home automation software picking up the websocket messages.
The text was updated successfully, but these errors were encountered: