I noticed one of my bots makes this pop sound when triggers. This sound started from the moment I set it up. My other bots sounds smooth though. Hope it isn’t going to crack.
Hiya, if its new you might want to send it back. There fiddly to fix, very tight tolerance for the finger. Dont add to much glue helps! 
Cracking sound and stuttering is a sign!
To be fair they are well made, using decent gearing. A Stiffer finger needs to be worked on…Switchbot.
I have a meter which report 100% for battery level when it reports 0% in the Switch-Bot app.
I use ESPHome as I told but I use the same method as you so are there other people than me who noticed that?
@Nardol the battery level can only be retrieved if the switchbot meter is sending out BLE data. The easiest way to confirm what the meter is currently sending out is to use the nRF connect app on a smartphone
At 0% I can’t see how the device would be on, sending data
The service data will look like this for 100%. It is the 3rd byte
If you are using a switchbot hub, it is possible the hub (or app) has some logic which sets the battery to 0% if it hasn’t heard from the device in a certain amount of time
all my meters currently report 100% from the esp32, the switchbot app and nRF connect app. They have been in use for awhile now so not sure how they are reporting 100% still. I have not seen them go down yet
My meters atent updating with the data in HA, does anyone else encounter this? It’s stuck at 55% humidity for 2 days now 
Temperature stuck as well. Shows ok data in the switchbot app and Google Home. Tried restarting ESP a couple of times, nothing unfortunately.
@evnvc the esp32 never connects to meters, but if something has a locked connection (like possibly the hub) it could stop broadcasting
I had a meter stop sending data once a long time ago, pulling the battery out fixed it
if the esp32 was rebooted, it should find the meters if they are broadcasting. you can use the ‘nRF connect’ app with a smartphone to determine if they are broadcasting
did you happen to update the firmware on the meters recently? switchbot updated how the meters broadcast data to match their meter plus. You will need the latest code if you did update firmwares
Thanks for the quick reply and support on this devWaves!
Pulled out the batteries on my meter plus, did a few more restarts in HA, MQTT server and the ESP32, unfortunately same behaviour. It’s being seen, but the data isn’t being reported properly, if at all. My Meter Plus is on V0.6 firmware.
I also installed the nFR connect app, and it seems the device is broadcasting. I will give ESP another flash, was using v6.10 until now and just saw there’s a V6.11 published.
Update: all seems to work well with v6.11, thanks again @devWaves for the additional clarifications and troubleshooting. Coffee’s on me today
if anyone is having issues with disconnects that can only be fixed by rebooting the esp32, I would suggest trying the arduino esp32 framework library from arduino boards manager v1.0.6 and see if the issues continue
I am currently investigating issues with the esp32 framework core arduino versions 2.0 and greater. v1.0.6 has been stable for me
1 Like
Just reflashed mine with downgraded 1.0.6 version, but for one of my contact sensors for example last update was 4 hours ago. nfr app shows the sensors are broadcasting, but mqtt isn’t picking up the updates (checked with mqtt explorer)
hey @evnvc what is the last rssi link quality value of the sensor that isnt working?
link quality is important. for example when testing I had one that worked with my office door open, but with the door closed it barely worked
in some scenarios multiple esp32s is a good call if the signal is bad for certain devices
My ESP is on the same floor, doors open, not sure what to make of it. For the bot, for example, I was sitting with my laptop next to it and didn’t pick up the presses
@evnvc are u using the mqtt user/pass with other stuff?You can try creating a user/pass in HA specifically for switchbot. Somone else mentioned that fixed issues for them
what model esp32 are u using? just to know
u can change the initialScan value in the code to something high and when the esp32 boots it will scan for longer. May not fix stuff bit it doesnt hurt, it stops scanning after it finds the devices or when it reaches initialScan seconds
Just spent around 3 hours on this haha, did many things, so I don’t know what I did to make it work. I did re-install every trace of mqtt on my hassio, then I went full in and also used a spare ESP I had, previously unflashed.
But to answer your questions:
- Not using mqtt for something else atm, and I already had created a user/pass in HA
- what model esp32 are u using? >> I’m using a Lilygo TT7
oh cool. If u dont have issues I’ll probably add the esp32-wrover Lilygo TT7 to the suppported device list as I havent tested with a wrover model yet
1 Like
Hey devWaves,
Just wanted to say thanks for your work on this.
Got my first switchbot curtain robots yesterday and couldn’t get the HA Switchbot integration to setup at all “Unexpected Error”. After a bit of googling I found this. I followed the instructions using a spare ESP32 I bought for my ESPresense project, and got it up and running.
I stumbled for a while, was getting the unresponsive problem after sending an open/close command. Scanning was working fine. Anyway, I’ve read this thread from start to finish and then stumbled on the NimBLE 1.3.7 library comments, I was using 1.3.8. And it worked a treat. Initially I thought it was the board model I had picked in the Arduino IDE.
Anyway, great work, thank you so much.
Just to help with any compatibility concerns/questions, the switchbot Rod’s I’m using have Firmware v4.4 and the ESP32 I have used is this one
https://www.amazon.co.uk/gp/product/B071JR9WS9/ref=ppx_yo_dt_b_asin_title_o08_s00?ie=UTF8&psc=1
3 Likes
Thanks for sharing! How responsive is it? Is there any delay after you press command?
@chintito4ever it depends how close u place the esp32 to the switchbot. the linkquality rssi value will show the signal quality between the esp32 and BLE switchbots. if there is a really good signal it works pretty close to instantly. the worse the signal the longer it will take.
1 Like
@chintito4ever, I’ve really not seen a delay, I don’t see any difference speed wise over using the switchbot app on android. Apart from now I can call the curtains in automations.
What about NimBLE 1.4.0, will that work? Or should we stick to 1.3.7?
Didn’t notice 1.4.0 was out until you mentioned it. stick with 1.3.7. I did some quick testing and looks like the issue remains with 1.4.0. I will update the github issue. thanks