pgerke / homebridge-freeathome-local-api

A Homebridge plugin that allows controlling you free@home setup using the local API provided by the System Access Point
MIT License
18 stars 2 forks source link

Support free@home scenes and light groups #38

Closed pgerke closed 1 year ago

pgerke commented 1 year ago

As a user I want to trigger scenes that have been created in free@home.

NB: In the current implementation of free@home, the scenes are treated as pseudo devices. It is not possible to find out via the local API which free@home devices are included in a scene. So with the implementation of this ticket, it will be possible to trigger scenes like pressing a button.

pgerke commented 1 year ago

Extended the scope of the ticket to light groups.

pgerke commented 1 year ago

Published a pre-release version to npm: https://www.npmjs.com/package/homebridge-freeathome-local-api/v/1.5.0-pre.1

Scenes are working nicely, light groups not so much. The state of a light group is not reflected correctly on the panel. This needs some additional work I guess... Unit tests also need to be extended.

korneliuscode commented 1 year ago

I tried the new version, works great. The problem is just that the devices don’t show up in the HomeKit app.

pgerke commented 1 year ago

That's strange... The scenes and light groups should show up in the default room. Works for me at least... image

floriangrotz commented 1 year ago

Maybe cross connected to #48 - as Scenes have the prefix FFF

korneliuscode commented 1 year ago

Given it shows up on homebridge I assume an issue between homebridge and HomeKit. Therefore should work in the plug-in. Perhaps I have to reinstall every time new devices are added (not owning a HomePod).

pgerke commented 1 year ago

Scenes are done in #39, light groups still to be done.

pgerke commented 1 year ago

I'm giving up on the light groups. When I'm sending the same updates I'm recieving when I'm triggering the light groups from the free@home app from Apple Home, the lights are going on, but the light group remains off in free@home. This leads to inconsistent states and very bad user experience in mixed operation. I can only assume that some magic is happening in the SysAP that is not visible on the local API.

github-actions[bot] commented 1 year ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.