Replies: 1 comment 2 replies
-
You're in luck as this is already detected by the integration. You can use the Puck temp sensor, for example, to detect if a puck is "inactive". When a puck is offline, the sensor will become unavailable. So, in your automation, check for when the state of the puck temp sensor entity is "unavailable" as your trigger. The same can be done for vent cover entities to determine if a vent is offline as reported by Flair's servers. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Frist time HA user and know just enough coding to be dangerous.
The idea:
Detect when pucks go offline and allow it to trigger an action. As it stands now, it does not appear that the "Inactive" data is passed through to HA's data set.
The data:
The Flair API does seem to track when a puck goes offline. Calling "get https://api.flair.co/api/pucks" returns a bunch of data, including "Data.attributes.inactive"
Inactive = "False" means the puck is online
Inactive = "True" means the puck is offline
The reason:
If my internet blips, one or both of the gateway pucks will go offline. Following the Instructions for "Automatic Firmware Recovery" at https://support.flair.co/hc/en-us/articles/360040851932 seems to fix the problem. I have configured them with Smart switches to be able to power cycle them remotely, but would love to just have HA detect and do it for me rather then coming home to a off temp house and having to go looking what failed.
Thoughts and am I doing this right?
Beta Was this translation helpful? Give feedback.
All reactions