[APP][Cloud & Pro] SwitchBot (Release 2.0.57, Test 2.0.59)

Yes - when i restart my Homey, it miss the token - and i have to connect the Homey again with the Mini Hub filling in username and password.

Is this a Homey problem or a Switchbot problem ?

I’m guessing it’s a Homey problem, but the tokens should be saved to nonvolatile memory. My Homey Pro regularly restarts due to beta firmware updates, but I have only ever logged in to my SwitchBot account once when I added the first device over a year ago.

If I delete the app, do I need to re-add all the devices?
And if I add the devices again, will my flows remain intact or do I need to rebuild them?

Don’t delete the app, just that one device. But, unfortunately, you will need to rebuild the Flows for that device, really sorry.

You might wan to look at this topic [HOW-TO][Pro][Cloud] - Tool to FIX (advanced) flows after removing and re-adding devices

Note: that fixing the Flows requires re-adding the cards that were based on that device.

2 Likes

Just to confirm, have you installed the Homey SwitchBot app and installed the lock using that or are you just using Matter?

Did you send me the Information Log from the App settings page?

Hi Wolfgang,

can I set the expected temperature at the panel and will get a trigger card for flows to set the temperature at the heating valve?

Here’s my current configuration. As you can see, there is a trigger card for change of new destination temperature.

I would like to know how I can use the panel compared to the Danfoss ones I’m using for now. But like to switch to Switchbot for valve and control panel.

Greetings,
David

From my experience, I can only pair it one AC unit at a time and not the radiator valves.

The API doesn’t support setting the temperature either.

There’s no feedback when the target temperature is changed.

1 Like

It seems the Home Climate Panel can only be paired with the radiator valves directly using Bluetooth. Setting the target temperature is not mapped using the API with web hook. Too bad. For now I’m using the heating planer for all my radiator valves and climate panels from Tado or Danfoss. And I would like to use only one place for configuration of heating plans.

Hello David,

I’m not that good at the system. I’m happy with tools and workflows that work. Unfortunately, I can’t answer the question.

Regards

Wolfgang

1 Like

I added it to Homey using matter. You can switch the candle warmer on/off and set the dimm level for the lamp. Works fine.

I’ve got 4 climate panels and wonder, how to add it to Homey: does it support only BT mode for adding or hub mode too?

It’s only hub mode.

1 Like

That’s fine for me, but pairing shows only ā€œno device foundā€ - but I added one panel to the Switchbot app and connected it with the radiator valve for this room. Do you have a hint, how I can debug this?

I’ve the app 2.0.52 (test) running on my Homey Pro (2023 / 12.10.0).

I did the ā€œget hub devicesā€ in the settings of you app and got this:

{ "deviceList": 
  [ 
    { "deviceId": "xxxxxxxxxx", "deviceName": "Ruth Raumklima", "deviceType": "Home Climate Panel", "enableCloudService": true, "hubDeviceId": "000000000000" },
    ... } 
  ], 
  "sceneList": [] 
}

I removed all other devices and replaced the devices id with ā€œxxxxā€. So it’s there, but I can’t connect it to Homey.

Any idea?

I will be home this evening and take a look as it should find it.

We had to make an emergency trip up north yesterday as my wife’s father is end of life, so that’s now both her parents that probably won’t see Christmas. As you can imagine it’s a difficult time for us.

1 Like

Oh no :frowning:

Family is more important than the tech stuff - no need to investigate for this issue too fast.

I have now also a Meter Pro. It is connected to the switchbot App (and thereby Hub).

I can connect it via BLE mode with Homey (but only with active pairing mode), but the temperature, humidity and battery level is never updated (sometimes there are initial values, but never updates). The RSSI gets updates frequently.
The distance to Homey does not matter.

What could be the issue?
Connection via hub-mode works, but BLE mode not.

Normally the pairing mode should not be necessary after adding the Meter pro to the Hub?

OK, I have found the issue. At some point the device type must have changed as I was only looking for ā€œClimate Panelā€ and I have added it to my Homey several time like that. I just tried again and it also failed for me, so I looked closer and then noticed it is now ā€œHome Climate Panel". I have also noticed that for the webhook it is still reporting just ā€œClimate Panelā€, so it seems they haven’t changed it everywhere.

So I will publish an update soon.

It is probably due to Homeys poor BLE performance. If you open the app settings and open the Log page, then set the Level to Basic, you should see message come in from the BLE polling:

I suspect the reception is not good enough to receive all the Service data and / or Manufacture data which is were the information comes from.

You could also try looking at Homey Developer Tools and find the device in there to see if the relevant sections are present.

If you want to send the Log I will take a look and point the relevant bits out.

I have published a new version.

In the LOG is written: !!! Parsed MeterPro BLE: No service data
I send out the full log. Thank you.

In developer tools it looks similar to the meter Plus. The content for data is shorter. Excerpt:

  • Advertised service data (hex)

    [{"uuid":"0000fd3d-0000-1000-8000-00805f9b34fb","data":"340064"}]

  • Advertised Manufacturer data (hex)

    "6909b0e9feacd6ab8b6409943a0030"

I have four meter Plus and an outdoor sensor, where BLE works. So the range is not the issue. It the same even if the meter Pro is directly next to Homey.

Sorry, my mistake, could you set the log to Full Information, then it will show the received data.

Also, could you let me know the BLE mac address of the Meter Pro, so I know which packets to look at.

Unfortunately, I don’t have a Meter Pro, only the Meter Pro CO2, so I can’t check what is happening without the exact packet of data.