Iāve had various issues with the switchbot app in Homey, mainly after around a day all devices do not update. So reading here I updated to 2.0.49. which has support for the old settings for auth.
However after another day noticed today that devices failed to update for several hours, iāve checked the log there is zero errors. Restarting the app everything resumes as normal.
Note I did notice one fact if in the app settings i choose get status for a device, the correct values are returned, rather than the stale values against the devices within Homey.
Secondly also use Home Assistant and the cloud updates have never failed.
I have seven devices so cannot see hitting 10,000 limit.
It sounds like the webhook is not working. Unfortunately, that one is difficult to diagnose as it could be anywhere. You say you also use the devices in HA, so maybe thatās robbing the webhook as the API only supports one webhook server.
Thanks for Reply. Iāve just disabled the Home Assistant Cloud service and will monitor if Homey App keeps the connection. It was just odd I could get up to date service information in the app status page by id. Will Report back if ok / or fails
When you use the app settings page it polls the device, asking for the information. If the app did that all the time, updates would be slow, becoming more infrequent with each device added, as they all would have to share the 10000 api calls. So, to ensure a speedy response, the app sets up a webhook to receive push notifications when something changes. The problem is the SwitchBot server will only register one webhook sever per user account.
Is it somehow possible to see the RSSI, when using the Hub?
I wanted to compare the signal strength between Homey and Hub, but do not see the RSSI via Hub (neither Switchbot app nor Homey).
I have the issue that not all temperature/humidity changes, which are shown by the meter plus are send to Homey. But this missing values are also not (directly) visible in the log/history data in the switchbot app. So the App shows the correct value as ācurrent valueā, but in the diagram you do not see it - sometimes significantly later. Seems to be an issue on switchbot side, that the meter plus does not write everything to its own log file immediately?
But why is the webhook info related to the history/log file and not the current value?
Perhaps it helps to connect via Matter? I need all updates, because the radiator valves use the sensor as input.
Interesting: Via Smartphone Homey App I can connect all 4 Meter Plus parallel via BLE without activating the pairing mode. But via Homey web app nothing is found. (To check if I get all updates in this mode ā> yes)
The Meter+ with ~7 m distance (and severall walls) inbetween has -95 dB RSSI, but still connection. But also the Meter+ in ~2 m distance has only -74 dB (but two speakers are inbetween and they block very good signals like WiFi).
Placing the Homey higher in the room increases a little bit the signal strength.
Would be nice to now the values via Hub - if they are better. But it work at the moment.
Directly next to Homey I get -55 dB.
Via manage hubs in the switchbot app you can see a signal strenght without values. Two have only 1 of 4 beams. The two nearby 2 of 4. So also not the best connection.
But also directly next to the hub its only 2/4.
Iām not sure I understand, but the webhook receives pushed data and that updates the current value, plus it is logged by Homey. Iām not sure how the SwitchBot app works, but maybe it gets the log from the device.
I canāt comment as I have not had any luck using Matter.
The SwitchBot devices constantly broadcast the BLE data, so the pairing mode is not required.. However, AFAIK they do need to be added to a SwitchBot account in order to initialise them so they start broadcasting.
There is a long time issue (2 to 3 years) with the web app where it times out after 10 seconds, even though it doesnāt show an error straight away. The BLE request normally takes between 15 to 20 seconds, so the web app gives up before the BLE call has finished. The mobile app doesnāt have that issue and will keep listening for around 30 seconds before timing out. I have reported this to Athom many times, but it is still there.
Generally, the SwitchBot hubs have a much better range than Homey. In fact, the range of Homeys varies a lot. At one time I had three Homeys and a bridge and the BLE connections for one were nearly impossible, even struggling when the device was right next to it. Another had an OK range and could connect to devices in the same room, with the other two somewhere in between. I have several SwitchBot hubs of one kind or another and they can all pretty much reach anywhere in the house.
My best solution, and the one I generally use, is with an ESP32 and the code I have made public on GitHub. It doesnāt support all the devices, but it has a great range and is very fast to respond. It connects to the devices via BLE and pushes changes directly to the Homey SwitchBot app via the LAN.
Homey gets only the values which are written by the meter plus into its history/storage. But not the āactual valueā if it is not written to the history.
I checked it multiple times: Sometimes the meter plus shows an update on the display, but does not write it into its history data. You can see that in the switchbot App. The App shows the current displayed values and the values in the history/log of the meter plus.
And only if the value is already written into the history, it gets pushed to Homey via Webhook.
I tried it and here is the same issue. Also via Matter only the values, which are recorded in the history data are available in Homey.
I already wrote a Mail to Switchbot. I think the meter plus sometimes āforgetā to write the new value into the history. And the webhook does only react on changes in the history, not the ācurrent displayed valueā.