Switchbot Thread
Oliver Parkes
Since all switchbot integrations are developed & maintained by community devs (i.e. not officially developed by Hubitat themselves), you'll always get the best support by posting your question in the respective community thread about that particular app/driver... That way, it catches the eye of the respective developer and fellow community users who have helpful experience with it.
If you are using tomw's app, I'd encourage you to post your question in that thread. Tomw's readme files (on his respective GitHub sites) are always very thorough though, so if using his app, I'd also encourage you to double-check your setup using the readme steps first.
This will be cloud-based integration.
If you want 100% local control consider to add Home Assistant. The HA automatically picks up
all SwitchBot toys. Then use Home Assistant Device Bridge to bring in all SwitchBot devices to HE.
My integration reflects the Bot status when it is configured in "switch" mode on the SwitchBot side. The SwitchBot API does not report any status (for either state and/or success) when it is in "button" mode, so that info isn't presented in my integration.
Does the switchbot API report battery levels for curtains? It would be great if I could see them in hubitat and add their tiles to my "batteries" dashboard. Also my curtains are all in paired sets so I'm not sure if that makes things more complicated since there'd be 2 separate battery levels per device in hubitat. I can check the levels in the switchbot app but it'd be so much nicer to have everything in one place in hubitat.
I have several IR devices. I used your IR driver and createChildDevices for those IR devices accordingly. But I do not see " infraredRemoteList in the State Variables section". It's empty! Should I delete them and re-create Child devices again? How can I get the SwitchBot driver to discover all IR commands for all the IR devices?
Download the SwitchBot app on App Store or Google Play Store. Register a SwitchBot account and log in into your account. Generate an Open Token within the app a) Go to Profile > Preference b) Tap App Version 10 times. Developer Options will show up c) Tap Developer Options d) Tap Get Token.
Alright everyone, I am brand new to Hubitat and this has been a fun process getting everything in and setup. @toffehoff you are the man for making this API and making it so easy. Your documentation is on point, I'm an IT professional and there are many software development companies that could learn from you lol. Anyways....
Question, I'm using the SwitchBot Contact Sensor, love the sensor and use it for turning on some outside lights. I was hoping there was a way that when I'm done with the outside lights, I could just hit the button on the sensor to turn them off, instead of doing the "exit" action of hitting the button and opening the door. Is that possible and I just havent figured it out, or is this a Switchbot limitation?
Don't worry @bulltipper . There are two drivers. I've made a very lightweight driver for the Bot device (which is the start of this topic). Separate to that, @tomw made another driver which supports many different switchbot devices. It is a bit confusing, I understand.
Regarding your question about the contact sensor, I assume you're not using mine, but the other driver. Therefore I can't answer that specific question.
Welcome to the club anyways
So that bring said, if switch not only allows to button on the contact sensor to be used as an exit, push button and open door, there's no way for me to just use the button as a button on the contact sensor?
Well this work with SwitchBot Tilt - the one that opens the blinds? I'm looking into this as a solution for automating some of my horizontal blinds. I have Alexa, but would love to use something that can be operated through Hubitat.
So It has been a long time since I have had to do any real coding work. I JUST got a hubitat to control a Zwave device I recently got. This part of it works great as the drivers were all built in ready to go.
I have no problem with getting my token from the switch bot app, but when it gets to the part where I am opening a cmd prompt to use that token either I am blind or the steps don't quite line up for me. The how to video attached the guy isn't using hubitat to do it and basically skips right over this step.
Hi, no worries, I've also had to learn and did some very basic mistakes. Am glad you have the guts to ask
First off: are you using windows, linux or mac as your computer? The curl code is for windows, maybe that could already explain things. (I will update the readme.md to reflect it is windows).
If you are using windows, can you tell me what error message you get?
That being said now I am trying to finish the rest of the process. I have added the switch bot system driver to the drivers code area. I also added the switchbot curtain driver. I added them as two separate drivers.
Now I am trying to add the device, so I go to add virtual device. Once there I change the type to
Switchbot Curtain. Give it the correct name. But I dont see anywhere that I can put in the three parameters (OpenToken, DeviceID and Press/Switch mode)
Great to hear you've managed to solve the curl issue.
You mention you're using the switchbot curtain driver. That suggests you're using @tomw driver, that could explain why you don't see the parameter fields.
This is the devicepage of the switchbot-bot driver (with the parameters):
image22301264 157 KB
As I continue to play around, I have been able to successfully add both of my blinds using the drivers from @tomw. Essentially loaded his system driver and then once that was loaded and token and secret code put in I was able to click create child devices and it loaded the blinds.
However, it has one flaw from an automation perspective. It will turn itself off if there is no sound played through it for 20 minutes and requires one to manually press the button to turn it back on. Some users have hacked together something to play an inaudible sound through the speaker periodically to keep it on but Bose warns that the battery may overheat and cause a fire. I was given this speaker as a gift before I was into home automation so had no idea to look for this seemingly simple feature.
Anyway, because this is written in Python it will be of limited use in setting up an OH binding. It also seems to only work on Linux which would cut out Windows and Mac OH users from being able to use such a binding.
I just came across their Kickstarter campaign, and the Switchbot Curtain seems like a thoughtfully designed device, from the way it grips the curtain rod/rail to the optional solar panel. Hopefully it works out well for you!
For multiple reasons I decided to make an abstraction for switchbot as I already had a MQTT broker running. I created a Docker container that translates an incoming mqtt command from openhab (or even google) and scans for the requested switchbot via a bluetooth stick and sends the command, based on the lib that switchbot made available.
If anyone is interested you can find the code here: GitHub - dietah/mqtt-switchbot: Control a SwitchBot switch via mqtt messages
The available docker is compiled for amd64 as I had difficulties with the arm bluetooth stability.
I just wrote this GitHub - devWaves/SwitchBot-MQTT-BLE-ESP32: Allows for 2 switchbots buttons to be controlled via MQTT sent to ESP32. ESP32 will send BLE commands to switchbots and return MQTT responses to the broker
I am basing this PR on what I see in this thread as I do not have a switchbot to work with but I am hoping some of the users here will help with contributions to the effort. All feedback and suggestions are very much welcome and appreciated. I hope this can result in a fully functional control for these devices using OMG.
Hi @travs, I have already done work on the SwitchBot Curtain and Motion Sensor decoders, which are ready for testing, if anyone with these devices is willing to help.
as above I also had serious issues trying to pair Matter devices and after hours of reading and experimenting I found that you have to be on a 2.4ghz ONLY SSID / WiFi network. Every time I tried to add a matter device it would fail if the 5Ghz frequency option was enabled. This includes having the device (ie. iPhone ) also connected to that 2.4 ghz network. Most routers will automatically steer devices up to the 5Ghz band so if your router permits it create a new SSID that is 2.4 only and use that - even if you hide the SSID later. Hope this helps someone.
Adding more data to this thread - I had a Eve Motion (with a matter sticker on it) that was able to pair a month (maybe 2) ago that was working up until I deleted it to add it to another room (big mistake). I also have a brand new Eve Motion that out of the box will NOT pair with Apple Home. I've also had a Leviton in-wall Dimmer switch demonstrate this same behavior (it was upgraded from Homekit to Matter) and it will no longer pair. I've also exhaustively tried all of the various procedures below with no luck sans creating a new AppleID which I just don't have the patience of doing. My last try was to get another Matter Border controller (a Google hub mini with thread) to try to pair the Eve Motions - no luck there also. At this point I'm giving up and putting it up on eBay for sale.
I spent an afternoon trying to add an Eve Energy Matter enabled outlet to HomeKit. The device paired (probably by Bluetooth) easily enough but then became not responsive immediately once added to Home.
c80f0f1006