[APP][Cloud & Pro] SwitchBot (Release 2.0.35, Test 2.0.49)

Tim_S · October 30, 2025, 12:22pm

I can see the device in the registered devices

also removed the switchbot app, restarted homey, restarted the esp.
When adding a device to homey the switchbot app keeps “searching”

Adrian_Rockall · October 30, 2025, 1:01pm

Ok, so if the ESP32 has found the devices, the issue is with network connection between the ESP32 and Homey.

If you open the app settings page and enable the Diagnostics Log, then restart the app. Look back at the log while the app starts up and check if the app finds and connects to the ESP32. Send the log if you would like me to take a look.

Tim_S · October 30, 2025, 1:13pm

Hi Adrian, so this is the diagnostic report code i got : 30459c5b-fc2e-455f-a59e-6b040bdad31c when opening the config page of the switchbot app it keeps loading (webinterface) on my mobile app i can see :

detected - invalid token
log - no Oauth2 client
get status : no oauth2 client found

also shared the diagnostic log with you

I don’t think it’s visible. the mac adress of the esp starts with 80-F3
on the device page of the esp the hubmac starts with c4:10 and adress starts with c1:32

Adrian_Rockall · October 30, 2025, 1:34pm

Yeah. I get the same, so I have reported it to Athom.

Tim_S · October 30, 2025, 6:53pm

resolved it with a logic and “get” card ; so it works now (but without the app)

maurice_van_tongeren · November 3, 2025, 12:20pm

I have a Hub2 that triggers a scene for my AC and some homey flows that send a trigger command to the hub. The scene triggering from homey to the hub don’t work anymore. Triggering direct from the switchbot app on my phone works, the homey works for other flows so I suspect the connection between the homey and hub are at fault. I can see the hub in the the swichbot homey app so not sure how to troubleshoot. Homey is on 12.9.0-rc.5, homey switchbot app is on 2.0.35, and the hub is on fw2.6-3.8. all devices rebooted, no effect. Any troubleshoot suggestions? ty

Adrian_Rockall · November 3, 2025, 3:09pm

Could you open the app settings, select the Log tab and set the level to Detailed information. Then run the Flow to trigger the scene. Then go back to the log and tap on Send Log.

maurice_van_tongeren · November 3, 2025, 3:39pm

DM sent

Patrick_Sanger · November 4, 2025, 1:52pm

Hello all,

I am quite new to the Homey world and hopefully you can help me. For my setup I got a bunch of switchbot plugs, which I managed to connect via homey (plug eu hub). The plugs measure the amount of electricity and I have had the Issue at first that every day or two I got an invalid token error, which I could only solve by repairing the device and relogging on to my switchbot Account. By getting a hub mini, entering it afterwards to my switch bot app and account, deleting the switch bot app from homey and reinstalling it finding all Devices again and rebuilding all flows I was able to extend it to one week before the token error appears. Still repairing the device works, but as there are 16 plugs and many flows repairing all 16 every week or reinstalling the homey app and rebuilding all the flows takes quite a bit of time and is rather annoying. I also found the token in the switchbot development settings in the app, but there is nowhere to reenter it in the app settings in homey, logs or anything else. Restarting the app in homey did not help either. Is there a proper solution to this? Is it an issue I will be facing with every other Brand as well (e.g. aqara) as the measuring of the electricity in intervals drains the token to fast with 16 devices? Sorry if there was already an issue recorded but in the past 400-500 messages before I could not find anything related. I hope you can help me and thank you very much in advance:)

Adrian_Rockall · November 4, 2025, 2:13pm

Could you send the Log from the app settings page as soon as you see the error:

I have seen others report the token is lost, but I can’t get to the bottom of it as I don’t see the issue myself.

Patrick_Sanger · November 4, 2025, 3:00pm

Hello Adrian,

Thanks for the quick reply. This is the error message that pops up in the log.

* 2025-11-04T14:58:30.061Z