-
-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Schlage lock always unavailable #103197
Comments
Hey there @dknowles2, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) schlage documentation |
Let me add diagnostics support to the integration so you can safely provide debugging information. I just pushed dknowles2/pyschlage#103 to add support to the underlying library. I need to wire it up to HA. |
Ok, thanks! Happy to test when that's available |
I'm experiencing the same issue. Schlage encode integration does not seem to function. Rather than create a new ticket, i figured i'd add relevant information to this thread.
Debug log for a previously working Schlage integration (retry=3) indicated the following:
|
@morikplay that's a different problem. Please file a separate issue. |
@dknowles2 thank you for the guidance. I'll file a separate issue. Your |
ok well, I think I've narrowed this down to a local network issue but I have no idea what that issue is. I noticed that if I have Bluetooth off on my phone, the schlage app is unable to connect to my lock. Additionally, I recently tried to access my lock away from home for the first time, out of Bluetooth range, and the lock was unavailable in the app. so, I think it appeared I was connecting to my lock fine but the app must default to a Bluetooth connection when it's in range. I'm not sure where to begin on the network, I have a TP link ax73 with more or less out of the box settings. broadcasting one SSID 2.4/5 and a guest network on 2.4 only which the lock connects to. I have also tried connecting the lock to the dual band SSID with the same result. I may make a hotspot with my phone tomorrow and see if setting up the lock on that allows HA to see it |
Ok well, one more factory reset on the lock later and this is now working, I'm not sure what prevented it in the past. Currently connected to the 5/2.4 dual broadcast SSID. I do now have wireless multicast enabled and IGMP snooping, although I am unsure if multicast was enabled in the past. I had toggled these before but the factory reset seems to have done the trick. Things that would identify this issue:
Appreciate the investigating and the addition of the diagnostics, I am sure they will be useful in the future! |
The problem
Followup to #103040
This resolved adding the lock to HA, however all sensors for the lock show as "Unavailable." Additionally, the firmware version reported in HA does not match what is shown in SchlageHome.
I am able to interact with the lock properly via the SchlageHome App on both local network and outside.
The lock is an Encode, WiFi.
What version of Home Assistant Core has the issue?
core-2023.11.0b5
What was the last working version of Home Assistant Core?
None
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Schlage
Link to integration documentation on our website
https://www.home-assistant.io/integrations/schlage/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
There seems to be continuous attempts to connect to the lock, which appear to succeed, these logs go on further - redacted for repeats:
Additional information
There is a little alert (!) on the wifi settings menu in the schlage home app, but it is connected according to the app and my router shows a DHCP entry for the lock. The lock is connected to a triple broadcast 6/5/2.4ghz network. I am able to control the lock and view all sensors in the schlage home app.
The text was updated successfully, but these errors were encountered: