Without a SwitchBot Hub, however, you can only control that switch via a BLE connection. It is obviously a neat trick to be able to - you know - make the little arm appear by poking your phone, but it is only so useful. You have to be pretty close to the printer and the switch, so you may as well just push the button yourself.
Luckily, I run RaspberryMatic on a Raspberry Pi 3 that is quite close to both printer and switch. Even more luckily, said Pi does have Bluetooth built-in, so ahead I went, searching for a way to make the Pi talk BLE to my SwitchBot.
First, of course, I needed to enable Bluetooth on the Pi. By default this is turned off on the RaspberryMatic install, but that can be solved quickly by ssh-ing into the system (how to configure that is documented elsewhere).
Then all the is need is to enable bluetooth and reboot by doing the following
Afterwards you should be able to play with your
hciconfig hci0 down
hciconfig hci0 up
The lescan command should shows a list of BLE MAC addresses, among which I found my SwitchBot. So the PI was close enough to work.
My first attempt at integrating the switch via some sort of NodeRed plugin failed miserably, though. None of the BLE plugins work on the RaspberryMatic due to lack of Python, apparently. So I gave up on that an resorted to an old friend: CUxD. I used CUxD for a virtual, command-line based switch before, so I though I can use that again.
After some playing around and some more google’ing I finally found a command line call that would work and trigger to Switch:
gatttool -b E7:E9:62:XX:XX:XX -t random --char-write-req -a 0x0016 -n 570100
Note that my Switch is configured to act as a push button. The arm will “press” for a second or two, then retract. It does not maintain state. If you have your SwitchBot configured that way you will send other numeric values:
570100 = Press
570101 = ON
570102 = OFF
570103 = Hold
With that knowledge I then went and created a CUxD Switch
The two important commands to set are obviously
CMD_LONG to trigger
gatttool, as well as
CMD_TIMER which we use to set the switch state by pinging the Printer.
Yes, the timer command looks complicated, but it is just an URL encoded call to cuxd to set the state of the cuxd device
CUX2801002 to the inverted result of a single ping. I have not found a cleaner solution yet and it works pretty well also for my other virtual switches.
And that’s all it takes! Happy Switching!