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

Just received 5 new presence sensors and popped on here to see if there was any update. Hopeful of support soon. These are so cost effective and so far they seem pretty good from inside the SwitchBot app but Homey is where I need the functionality :grinning_face:

Mine are on the way, so as soon as I get them I will add support to the app.

1 Like

New test version has support for the new presence sensor.

2 Likes

Awesome Adrian, just testing it and it’s working great. Will the light level become available to Homey?

Unfortunately, it’s not reported by the API.

That’s a shame - hope that will change in the future or the FP300 may have to be bought.

I have requested the light level, but not sure if it will be added.

1 Like

Is there a possibility to add the functionality of trigger/start the delay (on/off) function of the Power Plug mini (EU).

So like in the switchbot app ?

Please. :folded_hands:t2:

(And if the plug (and Presence sensor) ever becomes available as BLE this (combination of these 2 devices) would be making a massive impact because it could open up to so much (reliable and not cloud dependent) potential/ possibilities).

(By the way , I never saw the plug mini (EU) cheaper then now (as 4 pack) on Amazon(.nl) on Black Friday:

(its a real “steal” imho. )

(I need some (BLE plugs to be capable to be turned off and on (by Homey) when the internet and/of wifi is down/unavailable to restore the internet/Wifi by restarting the modem/router/wifi (poe power) by power cycling them through these power plugs automatically/by flow).

Using a SwitchBot Mini Hub with Homey and everyting works fine for a day or two. Often i got this error “No Oauth2 client found“ and after a repair in Homey ehverthing works fine for some time again.

Are there an error with the app?

@Jacob_B No issue here and I have several Switchbot devices.

Andy

There’s a few user reported this issue, but so far I haven’t found the cause or solution.

If you have a Homey Pro, as soon as you notice the error has occurred, could you open the app settings page, select the Log tab and then send the log.

Maybe still some last errors/problems of the cloudflare downtime a couple of days ago. :person_shrugging:t2:

And so you need to login/re-authenticate for your switchbot app again.

Who knows if of how the switchbot servers were affected.

Just a weird/mad hunch :face_with_monocle::thinking:

I logged in yesterday and today I got the error again

I cannot sent a log because it’s empty it says. See the screenshots

I’m having the exact same problem. Seems to be a bug in Homey’s SwitchBot app. :anxious_face_with_sweat:

I hope somebody who can fix this is reading it.

Otherwise I have to return it to the dealer.

For info: I’m running on Homey Pro 2023 and I do not have a SwitchBot hub (because I don’t want to) - and I am trying to connect the “Meter Pro (BLE)” device.

I can even see it in discovery mode in homeys developer tools.

Same exact error, “Invalid token”

In my case I do have hub, maybe it is not related. After repair device, login again in switchbot account, the integration works agaiin

I presume you have added hub devices to Homey?

I have added a single remote control to Homey. Is that what you mean?

I’m not sure why it is loosing the token in some cases. The app has well over 10000 users but this only happens to a few and I can’t replicate it.

In the latest test version (in review), there is an option to fall back to the old method using the tokens provided by the SwitchBot app.

From the SwitchBot API page to get the required tokens:

Generate an Open Token within the app For app version ≥ V9.0, a) Go to Profile > Preferences > About b) Tap App Version 10 times. Developer Options will show up c) Tap Developer Options d) Tap Get Token

For app version < V9.0, a) Go to Profile > Preferences b) Tap App Version 10 times. Developer Options will show up c) Tap Developer Options d) Tap Get Token

Once you have your token and secret, open the app settings page, select the Old Settings tab, enter those into the fields and then press Save.

Restart the app and it should then try to use the old method of logging in.