Obviously the Webhook will only come through when the contact state changes.
The thermometer also supports the Webhook but if it is the old type then it only updates every 10 minutes. The new bigger unit updates when the readings change.
Wait, I spoke too fast there. I repaired all of my Switchbot devices before I started posting here today, and the bot is using webhooks now. WOW Iām stoked for this. Itās controlling a door, so the polling interval was pretty annoying. I mean⦠contact sensors are both not working now, but if this is all that today brought me, I am a very happy gal. This is⦠wow.
OK, back to the contact sensors⦠so they both donāt work. One of them (the one I already re-added a couple of days ago) does have a status change from this morning, but I tried the door just now and it doesnāt read. Same as the other one.
Edit:
Oh yeah, Iām not that much of a noob
I just was concentrated on the one that stopped working this morning, had not checked it for the other door yet.
Can you see if there are any updates available for the contact sensors in the Switchbot app?
When I get home I will check the version of mine.
Mine have been reliably reporting via the Webhook so not sure why yours arenāt.
None that I can see, but to be honest I donāt know where one would look for that? I have it on auto-update, but that didnāt seem to update my bot as it just started to use webhooks after a manual repair.
I re-installed my two contact sensors, and the one Iāve been struggling with since today flawlessly updated itās contact status (no webhook though) exactly one time. Now itās back to only updating the motion sensor part.
Iām gonna step away from it for a while now. You get to it when you get to it. As I said Iām very glad my bot responds so fast now, and the contact sensors donāt work in many flows because they were too slow (sans webhooks, at least).
But itās weird, right? Iād almost say itās a hardware issue, if it wasnāt for the native Switchbot app still updating correctly. And the kinda suspicious timing of two sensors breaking in a similar way around the same time.
How far away are the sensors from the hub?
When you use the native app it will try to connect directly via BLE if it can, so if you have your phone next to the sensors when you operate them they will have a good signal.
You could try switching off the phones Bluetooth to see if you get the same results.
Also try moving the hub closer to the sensors.
30 cm, for the one that Iāve been struggling with today. The other one could in theory cause more problems, but even that is 3 or 3,5 meter. With a wall in between, though. But shouldnāt the Switchbot hub solve issues with distance you could experience with BLE? Also I donāt really get why that would cause issues for one of the sensors and not for the other. Although⦠some of the smart home sensors have issues reporting more than one change at the time, in my experience. Like a vibration sensor not reporting vibration if itās also tilted, or a motion sensor not reporting back movement when the tamper alert is activated. Just my personal experience. But the Switchbot sensors never seem to have had these kind of issues in the past.
The contact sensor did give me another contact sensor activation. But then it was back to only reporting motion again. Whatās more, the quicker response time for my bot seems te be spotty as well. Less hit and more miss. Does a phone have any role in sending or receiving a webhook? Because it looks like it is, but again I donāt really understand how webhooks work. Itās not using my phone as a hotspot or anything?
30cm should certainly be OK. 3m with a wall between, depends on the type of wall. The hub talks to the devices using BLE so it will still have limited range just like Homey (although not as bad in my experience). The advantage is you can have more than one and position them closer to the devices.
The phone has no direct influence over the webhook, other than it will relay the signal from the BLE to the cloud via WiFi and the webhook is generated by the cloud.
The firmware on my contact sensor is V1.1. If yours is lower then contact SwitchBot via the app and ask for them to make the update available.
This is the sort of information I get logged:
* 2022-05-21T16:30:46.170Z
* BLE Finished Discovery
* 2022-05-21T16:30:46.183Z
* Polling BLE: waiting for devices to update
* 2022-05-21T16:30:47.030Z
* Parsed Bot BLE (f4:7a:e9:a5:04:17): No service data
* 2022-05-21T16:30:48.714Z
* Parsed Presence BLE: No service data
* 2022-05-21T16:30:48.717Z
* Parsed Curtain BLE (ee:df:c1:eb:30:7b): No service data
* 2022-05-21T16:30:48.719Z
* ------------------------------------ Polling BLE Finished
* 2022-05-21T16:30:48.720Z
* Next BLE polling interval = 30000
* 2022-05-21T16:30:48.746Z
* Got a webhook message! {
"eventType": "changeReport",
"eventVersion": "1",
"context": {
"deviceType": "WoPresence",
"deviceMac": "***********",
"detectionState": "DETECTED",
"timeOfSample": 1653150647420
}
}
* 2022-05-21T16:30:48.752Z
* Got a webhook message! {
"eventType": "changeReport",
"eventVersion": "1",
"context": {
"deviceType": "WoContact",
"deviceMac": "***********",
"detectionState": "DETECTED",
"doorMode": "OUT_DOOR",
"timeOfSample": 1653150648154
}
}
* 2022-05-21T16:30:50.814Z
* Success sending command to ************** using OAuth
* 2022-05-21T16:30:54.086Z
* Got a webhook message! {
"eventType": "changeReport",
"eventVersion": "1",
"context": {
"deviceType": "WoContact",
"deviceMac": "***********",
"detectionState": "NOT_DETECTED",
"doorMode": "OUT_DOOR",
"timeOfSample": 1653150653683
}
}
Good day Adrian_Rockall
Is the air conditioning koenic kac 3352 also supported on the switchbot hub?
Iād like to hear it from you
Yours sincerely
Wilfried
I canāt see that one specifically listed, but if it works with an infrared remote then you should be able to teach it using the remote control of the AC unit. Thatās what I did with my AC unit and it works OK.
I donāt know if it works with infrared at all
If its not IR then it wonāt be compatible.
If you cup your hand over the end of the remote, to block itās transmission, does it still work?
If it stops working then itās probably IR.
Yes, I read somewhere the BLE of the Switchbot hub is better than that of Homey. But the main problem seems to be with the one thatās closest to the hub, so it doesnāt seem to be a BLE thing. I also donāt see how that would cause the motion sensor to work but not the contact sensor.
Apparently, I had to switch on bluetooth tethering on my phone. The bot is working great now, without the delay it had before ![]()
Iāll have a look at the firmware and contact Switchbot if needed. I do have another theory that I want to run by you though. Would it be possible that the polling interval, and as such the delay, could cause a contact sensor to not register if itās only opened for a short time? If one would open and close the door again in between the scheduled polling, would that read as if it hadnāt opened at all?
That still wouldnāt explain why the sensors donāt use webhooks right now, but it would explain why the āback-upā information doesnāt come through. Also why the motion sensors seem to work better than the contact ones, and why the front door sensor, though further from the hub, works better than the indoor ones. The front door usually remains open for longer before itās closed again.
Very strange, as the phone should be required once the bot is added to your account.
When just using polling then yes, that is one of the know issues.
To try and track down the webhook issue, could you enable āFull Informationā on the Log screen, then restart the app. As it starts up you should see a message in the output window on the log tab:
* Homey Webhook registered for devices {
"$keys": [
a list of devices should appear hear
]
}
@Adrian_Rockall
Can you confirm that switchbot did an update onto there API of the humidifier?
I believe i get sooner messages that the tank is empty, not sure but it looks like the status is now updated more frequently, maybe the homey app needs also fine tuning?
Iām not aware of any changes but will investigate.
I have taken my humidifier out of operation over the summer. However, it is not completely disconnected from the power supply. I get the message that the tank is empty at least once a day. I donāt think Switchbot has changed anything. The firmware is still the same.
I was looking for an app for a airconditioner, type Haier, model Pearl.
When i search in the Homey app store on āHaierā this app pops up.
Is this app supporting the Haier airconditioner?
It has wifi and IR.
For now this is only research, I do not own one at this moment.
The Switchbot Hub supports any air conditioner. The air conditioner only needs to have an IR remote control. You can learn all the buttons via the Switchbot Hub and then control the individual options via Homey.
Ah, ok. So I have toe add the Switchbot hub to Homey and place the hub in line of sight with the ac and thatās it.
Right?
Almost right. You add the AC to your SwitchBot account, via the hub, using the native SwitchBot app. Then you can add the AC unit to Homey using the Homey SwitchBot app.
Homey connects to your SwitchBot account in the cloud to control the devices.
As you say, the hub needs to be in line of sight with the AC, as that sends the IR commands.