[RELEASE] Homebridge Hubitat v2.0

[nh.schottfam]

This is fixed in latest update.

[mailtomatte]

Anyone Having trouble with home Geofence lately?

Mina isnt triggerering Away everytime..

[dJOS]

Every now and then I need to manually "test" the automation and then it comes good - this usually happens to me after a HomeBridge app update.

[mailtomatte]

How do you manually "test"? I have done it in Home app but doesn't always work also sent from send location geo from hubitat dashboard app

[Busthead]

I upgraded to a new iPhone and it appears arrival is being detected properly but not departure.

My Home address is configured in iOS Contacts and under Find My->Me->My Location "This Device" is listed.

Homebridge v1.3.4 with Plugins up to date. Running latest rev of iOS.

When I manually turn off the vPresenceSensor via the iOS Home app, Homebridge indicates an away status as expected.

Any idea how to troubleshoot this?

[cdikland]

@Brianlees

rebuilt everything and it still didn't work.

I realize this post is over 6 weeks old but wonder if you ever found a solution. I had a similar issue where of the 9 HE Modes it appeared that only 4 Modes appeared in Homebridge. Additionally, I lost 5 Hue bulbs from Homebridge. Or so I thought. Here is my post

Homebridge V2 and modes, Bug?

I installed Homebridge V2 on my Hubitat and setup a Hubitat (PI) server along with the Homebridge Hubitat Tonesto7) plugin. I started off small and added 27 Hue bulbs. Later, I decided to add my 9 modes. Once I did the first 5 (alphabetical order) hue bulbs disappeared from the Homebridge Accessories tab. All 9 modes just added appeared within the default room. On my iPhone Home app, I noticed that only 4 of the 9 Modes were present, however, the 5 missing hue bulbs have become switches (& beh…

[Brianlees]

Nope. No solution. I have up for now even though I really want to sync both so that I can better use the notifications in Hubitat based on modes.

[cdikland]

@Brianlees

Nope. No solution.

Have you tried to creating 5 new modes, delete your existing Hubitat modes then renaming the new created modes to the names of those you deleted. After that, try adding them back to Homebridge. Worked for me. ymmv

[cdikland]

Is it possible to add a second Hubitat hub to Homebridge? If so, what changes do I have to make to the generated configuration?

[dennypage]

Yes:

[RELEASE] Homebridge Hubitat v2.0

Wanted to post this here for anyone wanting to mess around with the child instances in HB v1.3.xx. You can use separate HE hubs or multiple Homebridge V2 apps or whatever... This assumes that you already have HE Homebridge V2 running.. Adding another config and starting child instances. To add child instances to HB, add another Homebridge App (or add app on a different hub) and copy the generated HB config: [nr331] When done, in HB Plugins click on the wrench icon and select JSON Config: …

[cdikland]

@dennypage

Yes

Nice. Thanks for the info.

[cdikland]

I am running HB server on a rPi4. Are there any issues running Node-Red on this same PI?

[erktrek]

None at all.. I am running HB, NR and Wireguard.

[JBrown]

Have not seen any.

[Ken_Fraleigh]

@tonesto7, I'm seeing this error whenever I change a zigbee bulb level from the Home app. I'm not sure when it started, but it's been going on for a while. I just hadn't had the time to see what was causing it. I tried several different drivers, just to see if it made a difference:

It randomly does it when controlling directly from the Home app. It does it every time I turn on a zigbee bulb using an automation in the Home app with a Hue dimmer and will set the CT, but doesn't set the level.

[Vettester]

I just tested this with one of my bulbs and I am able to change the level in the Home app without any error. However, when I turn the bulb off I am getting the same error.

[Ken_Fraleigh]

It doesn't occur very often when using the Home app directly, but happens with button automations that are created in Home every time.

[tonesto7]

I'm leaning toward it being something related to the driver itself, but I will investigate further just in case.

[Vettester]

@tonesto7

I'm leaning toward it being something related to the driver itself,

Thanks for the response, you are spot on.... I was using the built-in advanced zigbee bulb driver so I switched to the generic zigbee bulb driver and the error went away.

[Ken_Fraleigh]

@tonesto7

I'm leaning toward it being something related to the driver itself,

The three screenshots I posted are from three drivers; Sengled color plus, Generic rgbw, and Advanced rgbw.

@Vettester

I switched to the generic zigbee bulb driver and the error went away.

That was the driver in use when I first noticed this error.