Thanks for the quick response. I have been able to connect the outdoor meter, but it doesn’t matter what i do the meter pro doesn’t connect. I already restarted homey and the meter pro (batterys in and out). And the meter is standing next to homey… what could be the problem. Everything works fine in my switchbot app.
1 Like
Hey
Im new here but yeah same problem
I had issues with code 190, then it worked for few weeks and since a week it wont work
i tried everything in this huge forum but nothing works, im devastated
Can you open the app settings page and turn on the Diagnostics Log (Full Information). Then try to add the meter pro and after the procedure is complete (failed) go back and send the log.
Are you using Homey (cloud)?
yes just the cloud
OK, I think there is currently an issue where one or more of the Homey servers have ended up in a SwitchBot blacklist. This has probably happened due to too many requests coming from the same IP and being flagged as an attack. I have made both Athom and SwitchBot aware and they are investigating it, with the goal to add the Homey servers to a whitelist.
I have send the full log 
I used to have had 3 SwitchBot devices in Homey pro 2019 and wanted to add another lock pro but I got an message saying” New devices Found but also an error 190” and my only option was to cancel the installation. I have tried to uninstall SwitchBot app (and all devices), re-install SwitchBot app, re-install the Homey SW but nothing have helped. Now after deleting SwitchBot devices in Homey and I cannot get any devices installed again due to this error. When I look in SwitchBot app homey is registered as an (unknown) login Device. Does anyone have any idea what is wrong?
Probably this reason.
I have just released a new test version with support for the S10 Floor Cleaner.
Hello everyone,
I see the last exchanges and I think that, maybe, my problem is related…! I already have 2 temperature sensors (indoor/outdoor thermo-hygrometer) installed (which work very well). I want to add a 3rd one. The pairing process says “no new device found” (the device was in pairing mode and right next to the Homey).
I went to the developers logs and the device does appear in the list detected (I found the UUID thanks to the bar code on the sensor box):
{ "_events": "...", "_eventsCount": "...", "_maxListeners": "...", "__peripheral": "...", "__client": "...", "__ble": "...", "id": "d0c842461845", "uuid": "d0c842461845", "address": "d0:c8:42:46:18:45", "addressType": "random", "connectable": true, "manufacturerData": { "type": "Buffer", "data": [ 105, 9, 208, 200, 66, 70, 24, 69, 213, 2, 1, 151, 58, 0 ] }, "serviceData": [ { "uuid": "fd3d", "data": { "type": "Buffer", "data": [ 87, 0, 228 ] } } ], "serviceUuids": [], "rssi": -77, "timestamp": 1737924534541 }
What could explain this sensors" failure to be detected?
Thank you for your help !!
JB
Have you added the device to the SwitchBot account as that initialises it?
You don’t need the device in pairing mode to add it to Homey.
Could you send the Log from the App settings page so I can see all the data, plus let me no the UUID.
I have checked the log and it appears the device type is unknown to the app.
The uuid of fd3d indicates it is a SwitchBot device, but the first entry for the data should be the device type and 87 (‘W’) is not one I have come across before. Normally, the indoor/outdoor thermo-hygrometer have an identifier of 119 (‘w’). I don’t know if it’s because it was in paring mode or if they have changed the id for some reason. The rest of the data looks OK and decodes the temperature as 25.3C, 57% humidity, and battery at 100%, so I have published a new test version that will recognise it.
@Adrian_Rockall I have some offtopic switchbot questions…
Do you know if the following is possible:
- replace my old mini hub (first gen) for the current one and migrate all devices from the old to the new one, without deleting and readding them in switchbot…
- is it possible to use 2 switchbot hubs in your local network to extent each other and use them then with Homey? (the idea is to use 1 hub on ground floor and a second one for 1st floor)
Both possible. When you add a hub you can place it anywhere and it will control/monitor any devices that are in range.
The Homey app connects to devices via the cloud and that decides which hub is closest.
I just wanted to ask. Is this issue still ongoing? I tried to add my S10 robot today (in the test version) and got the same error.
AFAIK, the problem still exists with some Homey accounts, possibly due to the Home servers being blacklisted due to too many requests from the same IP address.
Athom and SwitchBot are aware of the problem and we are trying to figure out a solution.
This solved it for me
I have four Switchbot Blind adjusters attached to my Homey Pro 2023 through BLE (no hub). They have been working fine for about 6 months since installation, with timed flows and button-triggered flows to open, adjust and close. They have all suddenly stopped working. I notice two recent updates that may have stopped it. Switchbot app to 2.0.14 and Homey to 12.3.1.
The blinds themselves work fine from my mobile through the switchbot app. So, has a bug in the integration been carried out, or could the bluetooth on my Homey have stopped working.
Has anyone else experienced similar? How can i otherwise debug/analyse where the problem is?
Ok now. I restarted the app, which refound all the devices and i can now control them again. Should not the update have done so?
