@dan.t if you're ears are on, just wanted to report I'm seeing this in homebridge logs...
[3/21/2026, 10:40:49 PM] [homebridge-hubitat-makerapi] This plugin threw an error from the characteristic 'Brightness': Unhandled error thrown inside read handler for characteristic: Characteristic is not defined. See Characteristic Warnings · homebridge/homebridge Wiki · GitHub for more info.
Homebridge v2.0.0 is finally released!
And I'm happy to say that @dan.t's homebridge-hubitat-makerapi plugin still works great.
Well, I gave it a few months before upgrading to HomeBridge 2.x, hoping all bugs would be worked out by now.
Unfortunately, it appears that @dan.t's Plug-in via Maker-API is not working 100% correctly with HB2.x. Events generated by the Hubitat Hub are not resulting in updates to Apple Home. Apple Home can control Hubitat devices via the plug-in. It is just that the real-time status updates from Hubitat -> Plug-in -> HomeBridge -> Apple Home is not working correctly. Homebridge does receive the updates from Hubitat, but they never make it all of the way to Apple Home.
It appears that this issue has been reported on @dan.t's GitHub for the plug-in. A user has also submitted a pull request to fix this issue. I am hoping that @dan.t will take a look and resolve this issue.
Update: Fortunately, I took a fresh backup of my Unraid server before performing the HB v2.x upgrade. I was able to restore HomeBridge v1.11.4 and now this are working properly again.
Could this be Homebridge version or plugin version related? I’m on 2.0.0, with plugin version 0.5, and Apple Home seems to receiving updates - I made a video just to confirm that we’re referring to the same thing:
Nope. At some point of time I must have restored an old backup. I am on Homebridge v1.1.12 and the plugin version is v0.4.15.
Sorry about the misinformation!
No worries. I got to learn how to perform a very specific Unraid restore of just one Docker container today. It worked very smoothly!
I am running HomeBridge 1.11.4 with this plug-in v0.5.2. All is well again.
At some point, I am probably going to need to either use Hubitat's OR Home Assistant's built-in Apple HomeKit bridge feature. It does not appear that anyone is still actively maintaining the dedicated Hubitat HomeBridge Plug-Ins these days. I appreciate all of the work the Devs did back in the day, but I also understand that time moves on and once there are other ways to achieve the same goal, sometimes things get left behind.
I installed the latest released version of homebridge (v2.4.0), and the latest plugin (0.5.0). I can see the issue clearly. Fortunately, the fix from @cgmckeever resolves it completely and is easy to apply.
Here's what I did (running Homebridge on bare-metal Linux):
/var/lib/homebridge/node_modules/homebridge-hubitat-makerapiindex.js with index.js from @cgmckeever's fork/var/lib/homebridge/node_modules/homebridge-hubitat-makerapi/accessorieshe_st_accessories.js with he_st_accessories.js from @cgmckeever's fork.Probably a little more tricky for me as I am running HB in a Docker container on Unraid.
Glad to hear the code in the PR fixes the issue for HB2.x!
For sure. You'll have to make your own Docker container to deploy.
@aaiyar SWEET ... glad it resolved it for you. It drove me completely bonkers.
@ogiewon The other alternative is to link the docker to local files. This way your runtime is contained in Docker, but you have a much simpler time managing the files and configs as they are local to the machine running docker, but mounted to the container.