Ok, I assume that channel.auto_disconnect_time unit is seconds.
But I think that I eventually found out what was draining the batteries, in the python scan wizard exemple in the is_private case, the scanner is never removed. I suspect this forces all the buttons to stay active if no-one press on the foreign button for 7 sec. Since I fixed that with a timeout, batteries are felling much better :-)
I'm using the python library to write a gateway between Flic buttons and some Yoctopuce products. It worked well so far, but I'm a bit worried about something: I added button battery monitoring and noticed that batteries level is dropping quite fast, at this rate, batteries won't last more than a few weeks.
So my question is: are there some programming strategies that will suck less energy than others? I found some mentions of active and passive modes, but there is no reference to such modes in the python API.
Is there some developers from Flic in there ?
I had to buy more buttons to find out, here is the answer
I suspect there are also Pale Yellow "yellow" buttons in the wild.
Hi!
Python documentation for get_button_info(self, bd_addr, callback): states:
The server will send back its information directly and the callback will be called
once the response arrives. Responses will arrive in the same order as requested.
The callback takes three parameters:
bd_addr,
uuid (hex string of 32 characters),
color (string and None if unknown).
What are the possible values for color ? are they "official" colors name, such as HTML color names?