kouske
kouske
@technyon why do you think there would be such a big power waste? I guess the Lock and ESP are in a connection already so I would assume there is...
If the lock and esp are connected then the lock should be sleeping between the BLE connection events anyway. If I query it every second then at one of those...
1. Why not just stay connected? 2. If the lock state changes, will that reflect in the topic immediately?
1. In this case the lock is the advertiser so it needs to send adv packets on all 3 primary adv channels with non-empty payload. When the lock and esp...
Ah I see, I thought the Hub has some proprietary implementation. I tried setting the query interval back to what it was but for some reason it didn’t update that...
So I played around a bit with the status entity and what I found is that if I set query interval to default then the status won’t always correctly reflect...
Oh, thanks for that :) I guess it’s done to service multiple devices.. In that case the esp should show ulockedNga status even when query interval is long but for...
If you could map the dimmer value then it would be awesome! I will try to look into it as well (hope I can ramp quickly :))
It might be that the dimming option was not ported due to lack of space..
In file xplg_wemohue.ino, there is a function called HueLights which eventually parses a value called "bri". This "bri" is later on sent to a function called LightSetHsb and I'm guessing...