I will also send this as a ticket support directly to the team, but I wanted to describe this weird behavior to the general forum too.
For the past few weeks, I have not been able to interact with my U-Bolt Pro Wifi using wifi, only using Bluetooth when physically present.
Using the app, I can not lock/unlock, add users, view logs… Essentially I can not access any of the lock’s internal data on wifi (only out-of-date cached data that populates the fields in the app). The app says WiFi is enabled, connected, Signal State is good (-46dB). But overall the whole app experience behaves as if I am not connected with the lock via Wifi.
But here is the STRANGEST thing. And I think this is the most telling piece of bug testing I can provide. When I physically lock the lock by turning the dial, the app’s homepage on my phone (bluetooth off!) will update the lock status in the app within 1 to 2 seconds. But the same status inside the inner app does not receive the live updated lock status (you know how they recently added a new pretty wrapper app to the old app, and the old app still runs inside the new homepage app?) This means that the device is in fact connected to wifi, can send outgoing messages, and the homepage of my app on my phone is picking up this changed state information. But I can not send commands over wifi.
Is the device only waking up and turning on its wifi radio when I physically turn the locking dial, but immediately going into some sleep mode and not listening for incoming wifi-sent messages? Is the new wrapper app able to listen to wifi state changes, but the older inner app can not/broken?
The whole thing works flawlessly over Bluetooth, but as everyone here knows, that is not why we bought this device.
U-Bolt Wifi Pro
Lock Firmware 01.38.0023
Bluetooth Firmware 00.06.0050
App version 3.1.0
Batteries are brand new.
Wifi router is only in 2.4GHz mode.