Marc Mueller
Marc Mueller
I think we need to differentiate here. Setting a value on its on (just for HAP-python) can't fail, because HomeKit can only send valid values. However the callback could. Maybe...
Didn't read the comments below #73 :sweat_smile: Good that we thought of the same thing here.
@ikalchev I don't like the idea of merging a PR that isn't finished yet, only to finish it later. Instead consider committing the changes directly to the PR branch. Maintainers...
Have you tried it without the `run_at_interval` method? Regarding `add_job`: It's not that much magic, just selects how and were to run the corresponding methods. Scheduling of corutines and shutting...
I'm no expert in `asyncio`, but the underlying idea was/is to use `async` for as many program parts as possible, since threads are kind of broken and inefficient in python....
> Also, the problem wasn't just a warning. The scheduling stops, and it stops because _wrappersomehow picks up another event loop that is not the one defined in the instance...
I though that using the `accessory_dirver/set_characteristics` method might work as an entry point. That way we can avoid using delays. I did a little test and this is what this...
Regarding `set_value`: You might be right here. What if the user calls `set_value` at the same time, when the value is changed in HomeKit and `set_characteristics` calls `set_value`? Regarding run():...
I think you're looking for the `getter_callback`.
Assign the accessory to the specific room the sensor is in.