Did the log print before that refer to the Hub Mini or the Bot? It's probably the hub and is innocuous if so.
If you refresh the SwitchBot System device page and scroll down, do you see a child device for your Bot?
Yes, here's the line:
device = [deviceType:Hub Mini, hubDeviceId:, deviceId:F690551FB5E5, deviceName:Hub Mini E5, enableCloudService:false]
No. So just to be clear, I don't need to create a new virtual device for the bot, right? The "Create Child device" should do this automatically?
That's right - the createChildDevices command should create the child automatically.
You have to enable cloud access to the Bot in the SwitchBot app. Then make sure you have the SwitchBot Bot driver installed in addition to the System driver.
Then hit Initialize and createChildDevices.
If it still doesn't show up, please enable logging and show the full output (or PM it to me if you prefer) while you do those steps.
Motion sensor then only does motion but no brightness aka light sensing events?
Contact sensor then only does door open/close but no button press or light sensing?
Is that right?
Is there a way to get that functionality into Hubitat (HE)?
It would be great as it could help automate some functions via Rule Engine, etc.
The real time events only contain the main attributes as described.
But if you do a full refresh on the child then you will get the rest of the info from both sensors.
My driver supports both of those methods for getting updates, so you can have the parent driver still running polled refreshes periodically (same as it always had) and the new app receiving real time events.
It's just that some of the info will have some lag and only show up in the polled updates.
3 Likes
I did all the steps again and it worked! Thanks 
2 Likes
Got my first curtain up and running but for the life of me I can't figure out how to get the open and closed status to work correctly. It shows as opposite in the Hubitat app and on my dashboard though correctly in the switchbot app. What an I doing wrong? Open is closed and closed is open.
When I click open it does open, same for closed. It just reports opposite.
I probably got it backwards (though, I'd be surprised if nobody else noticed, so maybe something changed in the values the API reports).
I'll PM you a modified version of the code to try to see if it helps.
1 Like
@jnosa899 confirmed via PM that my quick fix to swap the logic on open/closed worked.
I am curious if this is also broken for others, before I change the code and potentially break people's automations or other assumptions about how it behaves.
@rudyscoggins, @rob121, @dadarkgtprince, or others -- if you are still using this, do your "open" and "closed" states with my driver match the physical state of the device and/or the SwitchBot app?
1 Like
i'll have to update and test this again. won't lie, i tested the curtains at first, but still have yet to physically install them
1 Like
That's the original behavior in my driver (0=open). Does the SwitchBot app also say opened? @jnosa899 seemed to be seeing the opposite -- SwitchBot app and this integration were flipped from each other.
Is there an indication of which side of the window it is on? Or are they a pair? Just trying to figure out how this could potentially get flipped.
1 Like
This is with one sb curtain - not a dual pair. It's behavior in app is the same. 0% is fully open. Which is what your driver also shows.
1 Like
My are open but this is what it shows in the app.
1 Like
Ok, you are seeing what @jnosa899 is seeing.
Unless anybody can figure out what's resulting in the change in "polarity", I'm going to chalk it up to differences in physical installation and probably just add a Preferences input for the virtual device to invert the values when it's appropriate.
I'll leave the default for that input to be the current behavior, just so there isn't a change in behavior for existing users.
If anyone has other clues or suggestions on how to handle it, please let me know.
2 Likes
That sounds like a perfect solution tom. No need to re-invent the wheel. I'm loving this weather integration btw.
2 Likes
my curtains are open where the bot is on the right of the curtain rod and closed when on the left of the rod. I bet this is the determination of that value.
or maybe it's the newer version 2 of the curtain bot? I have yet to hook my version 2's up.
That was my hunch- that some of these were installed on the opposite side because of the physical blinds configuration, and there is no way for SwitchBot to know which way they're set up.
So, if the SwitchBot app doesn't provide a way to set the polarity, then I'll just do it in my integration with that user preference as input on which way to report it.
HAHA, I'm not the only that buys stuff and than doesn't hook it all up. My pile is growing.
1 Like
