Specific details about the filtering not working right was up above:
[RELEASE] Homebridge Hubitat v2.0 - #1251 by brad
I had it not work right for me before but I would have to try and reproduce it again.
Specific details about the filtering not working right was up above:
[RELEASE] Homebridge Hubitat v2.0 - #1251 by brad
I had it not work right for me before but I would have to try and reproduce it again.
That’s a good thing. Glad to see that you’re still around though.
I am just using a simple custom device driver to effectively interface my security system with HomeBridge using a virtual security keypad (supported by Apple). See below. I discovered today that Apple Home is reporting the right security events, but they are somehow VERY delayed. Like by 30-60 minutes delayed. And the security keypad is the only thing out of the many things that I have in HomeBridge that is delayed. Any ideas?
metadata
{
definition(name: "Virtual Security Keypad", namespace: "lnjustin", author: "Justin Leonard", importUrl: "")
{
capability "Actuator"
capability "SecurityKeypad"
}
}
def armAway() {
sendEvent(name: "securityKeypad", value: "armed away")
}
def armHome() {
sendEvent(name: "securityKeypad", value: "armed home")
}
def armNight() {
sendEvent(name: "securityKeypad", value: "armed night")
}
def disarm() {
sendEvent(name: "securityKeypad", value: "disarmed")
}
def intrusion(mode) {
def intrusionValue = "intrusion-" + mode
sendEvent(name: "securityKeypad", value: intrusionValue)
}
@tonesto7 I figured out the issue with the security keypad not updating properly. I have sent a pull request on gitHub to fix the bug. It's simple:
allowedListFLD was missing the "securityKeypad" attribute, so homebridge was not registering security keypads and thus the delay in updating.
Hello, I just added some Sonoff Zigbee Water Valves Outside using the tuna driver in the link below. How can I get them to report correctly in the home app?
I can turn them on and off with Siri and the app, but their state in the home app never matches what the hubitat device page says
I have them added as other in the settings, and they correctly ported over as sprinklers to the home app.
Hello, any thoughts on this error I keep getting in my logs?
[9/3/2024, 7:36:00 PM] [homebridge-hubitat-tonesto7] This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic value expected valid finite number and received "NaN" (number). See Characteristic Warnings · homebridge/homebridge Wiki · GitHub for more info.
heatingSetpoint: 12
coolingSetpoint: undefined
Any way to turn the lookup for Cooling Threshold Temperature off?
If a device sends a null value for something Homebridge was expecting to see, you can filter attributes and capabilities in the Homebridge Hubitat app’s settings (i.e. from the Hubitat web UI, not homebridge UI or Apple Home app).