I tried removing the integration entirely, and it didn’t seem to have any impact. Lock model is DDL240X-1HB, and the WiFi bridge is DDL203.
If you can, message me on discord under the same handle. We can try and figure it out.
Added. Same handle here as well.
Thank you very much rjbogz. I just bought a Philips lock DDL220X-1HW and I installed your Philips Home Access integration and everything works as “promised”. The only significant problem that I found so far - is that if I use the “native” Philips Home Access phone app, the Home Assistant would require a re-authorization (which is expected). But after I enter my credentials I can see a message “re-authorization successful” but the integration is still effectively disabled and the Home Assistant wants me to go through re-authorization again, but with the same result. The only way to “revive” your integration is to restart the Home Assistant. After restarting the Home Assistant everything works normally and without a need to re-enter my Philips Home Access credentials.
If you could address this issue it would be really great!
Thank you!
I am aware of the issue. Right now, the fix is restarting home assistant. I will hopefully have it fixed in the next update.
Thank you very much!
And another “wish” that I saw was discussed some time ago, but I haven’t seen any follow-up - is ability to talk to these locks over Bluetooth. If you are interested to work on this I’d be very happy to help and to contribute to this effort in any way I can.
This could definitely be possible with the gateway locks. I don’t have one to test with so it’s very hard. I would need to sit near it and test everything with an esp. Local control would be great for these.
I see the same as Kraze. I have a DDL240X-1HB and a DDL203 bridge. Thanks again rjbogz!
The lock I have (DDL220X-1HW) doesn’t require the gateway (though I assume it would work with it). This lock supports both - Bluetooth and Wi-Fi, and the Philips app is capable of connecting to the lock using either interface. If Wi-Fi connection is available it uses it, otherwise it tries to use Bluetooth. I have a little Android box where I can be “root” and I was able to install the original Philips app on this Android box. I don’t know whether this setup can be used to debug the Bluetooth communication…
Once I updated to the latest version, the locking function worked as expected. Thanks rjbogz!
I believe the polling I’m doing is causing the battery to drain quickly, at least on wifi only locks. If anyone else can confirm, even if on gateway, I may just update polling to only when an action is made on the lock, or once per day, whichever comes first.
First off, sorry this is in such early stages still with plenty of bugs. I’m 99% sure I am causing wifi locks to drain battery because I am polling every minute to retrieve lock state and battery/wifi data. There are some challenges to how to go about updating this.
My first goal is to try and read the data sent by the lock when you manually open/close the lock. This would be ideal as it would require way less state changes, but it is definitely the most challenging.
Second would be to just slow down the polling. I currently do it every minute and I could cut it down to every 5 minutes (extending battery life by 5x), or let the user configure this.
Third option is the possible bluetooth only control, which presents it’s own challenges. Personally, my server is about 30m (100ft) from my lock, so I would need something in between, possibly an esp, to relay stuff. This is tricky in itself to design, especially for people with not much coding or hardware experience.
I’m happy to take ideas or anything from everyone. Like I said, this is my first integration and I’m definitely not perfect.
(I have also purchased rechargeable batteries for my lock in the mean time, these last ones made it 2 months, roughly 62 days)
EDIT: I will likely implement the second option (for now) to let users configure it as it is pretty easy to implement. Should be available in the next day or two.