[RELEASE] Homebridge Hubitat v2.0

jtp10181 · August 15, 2024, 3:55pm

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.

Ken_Fraleigh · August 15, 2024, 9:53pm

That’s a good thing. Glad to see that you’re still around though.

JustinL · August 24, 2024, 12:24pm

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)
}

JustinL · August 25, 2024, 2:13pm

@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.

Steve9123456789 · August 26, 2024, 5:01pm

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.

philippompili · September 3, 2024, 11:37pm

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?

marktheknife · September 3, 2024, 11:46pm

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).

qtrain2391 · September 21, 2024, 12:50pm

Hey all,

Trying to get this installed but running into several issues. The config generator in the app doesn't seem to be working. It doesn't provide the cloud URL or the app ID. I was able to figure these out, but now I'm stuck with another issue. Here's what it says upon starting homebridge:

I did make sure these ports are open to my firewall. How can I fix this?

jtp10181 · September 22, 2024, 11:11pm

You don’t need the cloud url of the server is local. The error means Homebridge cannot reach HE. Post your config from the HB plug-in (remove any tokens)

evcallia · October 1, 2024, 6:43pm

Hello, looking for some support with this error Error: Cannot Bridge more than 149 Accessories. I've cut down my number of devices to 51 as seen in the stack trace below, but I'm still running into this issue. I have it running on it's own child bridge in Homebridge so no other plugins should be conflicting with it. Do I need to limit the number of capabilities each device has or something? Any help appreciated, thanks!

ritchierich · October 1, 2024, 7:36pm

This is a HomeKit issue as it cannot have more than 149 devices per accessory. I searched for that error and found a ton of posts online. Net of the issue is the cache within HomeKit/Homebridge may be full even though you cut down teh accessories. This one offers some advice:

jtp10181 · October 1, 2024, 8:12pm

Go into Homebridge Web UI > Settings > Remove Single Accessory
From there, remove any cached devices that you are not longer sharing.

If it is way out of sync you may just want to use the options to remove the entire cache, although not sure if that will have any other side effects.

evcallia · October 1, 2024, 9:04pm

@ritchierich @jtp10181 Thanks for your help!

Removing all the cached accessories specific to the homebridge-hubitat integration worked. I didn't want to delete all cached accessories since I have a few other integrations so I did it one by one like @jtp10181 suggested. For anyone else with this issue, I first had to uninstall the plugin because it was adding them back as I deleted them despite having disabled it.

Ken_Fraleigh · October 4, 2024, 4:48pm

@tonesto7 , getting the following error on latest beta:
[10/4/2024, 12:41:42 PM] [Hubitat-v2] initializeAccessory (fromCache: false) | Name: Kitchen Can 2 | Error: TypeError: Cannot read properties of undefined (reading 'hap')
TypeError: Cannot read properties of undefined (reading 'hap')
at PlatformAccessory.addAdaptiveLightingController (/var/lib/homebridge/node_modules/homebridge-hubitat-tonesto7/src/HE_Accessories.js:440:45)
at DeviceCharacteristics.light (/var/lib/homebridge/node_modules/homebridge-hubitat-tonesto7/src/HE_DeviceCharacteristics.js:410:24)
at /var/lib/homebridge/node_modules/homebridge-hubitat-tonesto7/src/HE_Accessories.js:131:48
at Array.forEach ()
at HE_Accessories.configureCharacteristics (/var/lib/homebridge/node_modules/homebridge-hubitat-tonesto7/src/HE_Accessories.js:127:22)
at HE_Accessories.initializeAccessory (/var/lib/homebridge/node_modules/homebridge-hubitat-tonesto7/src/HE_Accessories.js:90:25)
at HE_Platform.updateDevice (/var/lib/homebridge/node_modules/homebridge-hubitat-tonesto7/src/HE_Platform.js:307:46)
at /var/lib/homebridge/node_modules/homebridge-hubitat-tonesto7/src/HE_Platform.js:267:63
at Array.forEach ()
at /var/lib/homebridge/node_modules/homebridge-hubitat-tonesto7/src/HE_Platform.js:267:38
It seems to break adaptive lighting, rolling back to 2.9.4 fixes it.

tonesto7 · October 14, 2024, 9:26pm

I've been completely rebuilding the plugin so I will try to test to make sure this issue doesn't occur

user1781 · December 6, 2024, 9:23pm

I recently discovered that maker api isn't developed any longer. I have successfully setup homebridge v2 and connected it to my homekit. However, I need to make some direct api calls to homebridge v2 to completely migrate away from maker api and I haven't been able to find any api documentation. Can someone point me in the right direction?

bertabcd1234 · December 6, 2024, 9:28pm

Maker API is an app on Hubitat that can be used for a variety of purposes (often to integrate with another system without the need to write custom code on the hub yourself to do so). This statement is not true; it is still being developed.

But perhaps that's not what you mean. Are you talking about the Maker-API-based plugin for HomeBridge? I don't know about the status of that, but it would be the other end of this setup and unrelated to Maker API (or anything else about Hubitat) per se. That seems more likely, but then I'm confused by this question:

More information about what you are trying to do would be helpful.

Alternatively, have you looked into other options, such as the built-in Hubitat HomeKit integration or the one in this topic (see the first post)?

user1781 · December 6, 2024, 9:32pm

i assumed(incorrectly?) that maker api app and the homebridge plugin were made by the same person and were both no longer being developed. The maker api app has a nice section with some api documentation for making direct calls to the api. Since I plan on replacing maker api and the homebridge plugin with homebridge v2 and it's associated homebridge plugin, I figured I would try and migrate my api calls that go to maker api over to homebridge v2 instead of maintaining two apps in hubitat.

user1781 · December 6, 2024, 9:41pm

I have the built-in homekit integration. I wasn't able to fully migrate to it when it came out because it didn't support all the devices i wanted to export to homekit. I ended up running maker api with homebridge in addition to the built-in integration. Over the last year, the built-in integration has been very hit or miss with stability and reliability. As a result, i lost my desire to migrate over to it.

I see that the maker api is not related to the homebridge plugin, it's a built-in app. I guess I can just keep it and continue to use webhooks to call it for api based automations.

tonesto7 · December 7, 2024, 12:17am

I'm the developer of the Homebridge-V2 plugin and app. My plugin is superior is just about every way. It's completely customizable.
I just did a complete rewrite and I'm about to push out the new beta version after some more testing which is even better and easier to customize.