ST was kind enough to have a lengthy detailed conversation with me about this issue. Without going into technical details, ST is aware that there is a problem with some locks and the auto encapsulation feature. Thankfully now there is a temporary “workaround” and a potential permanent “fix” that we discussed in detail. Unfortunately since not a lot of people have brought up the issue the permanent “fix” is not a priority.
The best way at this time to get notifications working again on the BE369/FE599 locks is:
- Send an email to email@example.com; tell them you have a FE599 or BE369, that you aren’t receiving notifications/updates from the lock and request the “association workaround”. They will send the “association workaround” command to that specific lock on your account. You will need to request this for each affected lock (and each time you re-pair the lock). This will get your notifications working again.
If enough people affected this issue ask for the “workaround”, they may consider investing in the permanent “fix”. Hope this helps.
UPDATE: The permanent fix is going to be deployed in the upcoming 0.31.x hub firmware. Note that this would required you to exclude and re-pair your lock with the changes to take effect.