-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Access to scenes configured in free@home SysAP #31
Comments
I think it is possible but need to take a look at it first. |
Would love this to be added! Especially working with lots of shutters is annoying if its already setup in free@home. And controlling the exact rotation of shutters is impossible. Much easier to setup scenes for everything and just switch them on/off via home app. |
I think we can implement it when we switch to the new API. |
Implementing scenes would be great! Btw.: Is there already a plan when to switch to the new API? Thanks, |
It’s still an issue. Is there an update? |
Is adding a scene to HomeKit an alternative? I don't the access point let's use get the status of scenes. |
That is what I have done at the moment. As I have found out, f@h gives the scenes an identifier as devices. |
V E R T R A U L I C H - Feuer Software GmbH
I dont think the scene has a Staus.. It’s just a trigger. Status shows in the single devices.
Dirk Koch
Gesellschafter / Geschäftsführer
[X]
Feuer Software GmbH
Karlsbaderstr.16, 65760 Eschborn
T: +49 6196 5255697
M: +49 173 7467693
www.feuersoftware.com<http://www.feuersoftware.com/>
Eingetragen beim Amtsgericht Frankfurt am Main - HRB 108723
…________________________________
Von: TF1382 ***@***.***>
Gesendet: Thursday, February 24, 2022 9:46:09 PM
An: henry-spanka/homebridge-freeathome ***@***.***>
Cc: Dirk Koch ***@***.***>; Comment ***@***.***>
Betreff: Re: [henry-spanka/homebridge-freeathome] Access to scenes configured in ***@***.*** SysAP (#31)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
That is wahr I have done at the moment.
But for sure one configures it’s ***@***.*** with scenes first and natively in the AP.
So re-building these in Home is double work and sometimes not so nice as well.
As I have found out, ***@***.*** gives the scenes an identifier as devices.
So your work would have to check for them as I understand.
—
Reply to this email directly, view it on GitHub<#31 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APTYED6HMCSWNQRSNHTMDALU42KJDANCNFSM4RXCX6DQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Is there a way to access the configured scenes from the SysAP as a simple switch, which after switching on in homebridge activates the scene and then resets itself after some seconds to off again?
This way one would not have to rebuild all the scenes in the Apple Home again.
Thanks!
The text was updated successfully, but these errors were encountered: