@Emil I managed to check the battery and it was still at 85%+
I have disconnected and reconnected from the system and hopefully that will resolve it.
@Emil I managed to check the battery and it was still at 85%+
I have disconnected and reconnected from the system and hopefully that will resolve it.
@Emil How do you go about checking the battery?
They all started at the same time and used about the same amount, so I would expect the battery to fail on all of them at the same time.
I have a a flic hub situated in a downstairs cupboard and 2 flic buttons in a bedroom at the top of the stairs. One on the buttons stays connected with zero issues the other always drops to standby and will not wake.
What reasons are there that this button won't stay connected? And how can I fix it. It is currently hurting the WAP
@emil do you mean use postman as the target for flic to send to? or as an agent to mimic the call I want to make?
I have used Thunder Client (vs code extension that works the same as postman) to test the call and it works successfully. it also allowed me to send failing calls to see a response.
The problem I'm having is I don't even know if the Flic button is sending the call (or if it's getting blocked by the hub, getting caught in network firewalls or something else).
I'm trying to create an HTTP request to Home Assistant but am finding a block in the deployment.
I have created the test query that works with curl, but when I transfer that call to the HTTP request option in the Flic app (that is connecting to a hub) invoking the call or pushing the button does nothing.
Is there a way to see the logs of the calls being triggered and the response in the flic app? or any way to identify if the query is actually being sent to my HA environment?
Is it possible to run Git on the flic hub using the SDK for code management?