Possible Route to Home Kit?

[JDogg016]

Honestly, I blew up homebridge completely because I wanted to eliminate ST as well as some other plugins.

I setup homebridge from a clean slate and received the error when I tried to install the tones to plugin.

I will just try again.

[SmartHomePrimer]

Ah, OK. Maybe it is necessary to have something in there first then? Try this [see below], even though it’s wrong. Just replace the IP shown with your Hubitat, save it and start Homebridge. See if your config will then show up again from the app in Hubitat, allowing you to put in your correct info.

If your config shows, remember to click the back arrow after copying and click the Done button! I kept forgetting to do that in my late night, blurry-eyed state when testing Homebridge-Hubitat the first time, and the result was my api key never matched the app, so nothing worked.

{
“platform”: “Hubitat”,
“name”: “Hubitat”,
“app_url”: “http://192.168.1.100/api/92f88315-8a7a-4ae3-99cc-1c599bfda070/apps/174/”,
“access_token”: “c4642434-ad64-4ded-b8dd-5f3c58c4bb0d”,
“polling_seconds”: 10,
“update_method”: “direct”
“direct_ip”: “192.168.1.100”,
“direct_port”: 8000
},

[JDogg016]

Got it! Don’t know what happened but it works this morning. Maybe my internet and the coincidence of the update.

Thanks for sticking through the insanity!

[JDogg016]

Anyone ever seen this message in the hombridge log related to hubitat?

[SmartHomePrimer]

That’s what I saw and then later discovered it was because my keys were wrong in the config.json

In my case it was because I was clicking on “View the configuration data for Homebridge”, copying the info, but then jumping over to Homebridge and pasting it in, without remembering to go back to Hubitat and click the back arrow, then Done

[SmartHomePrimer]

Setup an Apple TV 4 last night. Works perfectly to sync Hubitat virtual switches in Homebridge with Insteon devices exposed in HomeKit via the Insteon-Local Homebridge plugin. Insteon devices triggered via a Pico in Hubitat react almost instantly. Best of all, this is a completely local setup, that also allows remote access to Hubitat devices!

This is a nice option until direct Insteon integration is available.

[chris.martin]

Could this mean the beginning of a HomeKit Integration without the need of HomeBridge?

https://www.forbes.com/sites/davidphelan/2018/03/31/the-one-thing-nobody-has-told-you-about-apple-ios-11-3-why-the-homekit-upgrade-is-a-game-changer/#3be5a2de64c4

[SmartHomePrimer]

Possibly for the masses.

What is very appealing about Homebridge for hobbyists like us is, integrations are ready quickly. Even if they’re not perfect, many of us don’t care. We just want them for certain purposes, and often the Homebridge plugin fits the bill perfectly. My Insteon integration is exactly that scenario. I can’t dim from Hubitat, but don’t use that functionality often enough from anywhere outside of one of the dimmer switches to care. The only thing I do wish I had was local integration of Insteon sensors with Homebridge.

Homebridge IS HomeKit for the impatient, as it was originally billed. Official HomeKit without the MFi chip is simply Apple getting with the program, and finally conceding that IoT integration requires compromise. Plus they want to sell more Homepods.

[Keo]

Ok. I give up. I keep getting this error when I attempt to start homebridge:

/usr/local/lib/node_modules/homebridge/lib/api.js:122
      throw new Error("The requested platform '" + name + "' was not registered by any plugin.");
      ^

Error: The requested platform 'Hubitat' was not registered by any plugin.
    at API.platform (/usr/local/lib/node_modules/homebridge/lib/api.js:122:13)
    at Server._loadPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:294:45)
    at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:85:36)
    at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:40:10)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (module.js:643:30)
    at Object.Module._extensions..js (module.js:654:10)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)

[ogiewon]

You are using @tonesto7's plugin, correct? Have you ever used Homebridge previously (e.g. with the old ST plugin) ? What platform are you running it on?

Homebridge Plug-in

I’ve ported over and heavily modified the Homebridge (HomeKit) plugin made by @pdlovelace. Screen Shots [image][image] New Features Full Local Network Communication Added Alarm support for Hubitat Safety Monitor Added inputs to define device types in HomeKit for the following: Lights Fans Speakers (Not Supported in Home App) - Apple has really didn’t add much to this except mute and volume control Window Shades (Currently works with the Generic Z-wave Drive) Native HomeKit Irrigat…

Also, if you can share your config.json file (obscure your private key), that would help us to assist you in debugging the issue.

[Keo]

@ogiewon

You are using @tonesto7’s plugin, correct?

Yes

@ogiewon

Have you ever used Homebridge previously (e.g. with the old ST plugin) ?

Yes. It worked when on ST

@ogiewon

What platform are you running it on?

Pi 3

{
    "bridge" : {
    "username" : "{myUserName}",
    "name" : "Homebridge",
    "pin" : "***-**-***",
    "port" : 51826
    },
    "description": "JSON API",
    "platforms": [
        {
            "platform": "Hubitat",
            "name": "Hubitat",
            "app_url": "http://{IP}/apps/api/581/",
            "access_token": "{myToken}"
        }
    ]
}

[ogiewon]

I am running on a PI3 as well, running latest version of Raspian Stretch, NodeJS, etc… (i.e. a very clean, fresh install a few days ago.)

My config.json is as follows:

{
    "bridge": {
        "name": "Homebridge",
        "username": "{my username}",
        "port": 51826,
        "pin": "xxx-xx-xxx"
    },
    
    "description": "JSON API",
    "platforms": [
        {
            "platform": "Hubitat",
            "name": "Hubitat",
            "app_url": "http://192.168.1.144/apps/api/616/",
            "access_token": "{my token}"
        }
    ]
}

which looks pretty much identical to yours, I believe, except the order of a few lines (which shouldn’t hurt anything.)

If you try to run the smartthings plugin instead, does it start without errors? Just trying to determine if the issue is with Homebridge OR the Hubitat plugin…

[Keo]

I removed the plug in and installed it again. Everything is working now.

[JDogg016]

Had HomeKit running for about a week, works pretty great. Had a few questions/thoughts:

1. Anyone notice duplicate devices? I have two devices for lights (ie. Barn lights)

2. (Way more important), is there a way to limit the attributes that come from hubitat into ST. For instance, I have 5 doors leading out to my back yard each is a contact sensor but now I have 5 temperature sensors that I don’t need. This limitation existed in ST.

[JDogg016]

Anyone else have an experience where a restart of the home kit container (or RPI) caused you to lose all the customized names and room assignments within home kit?

[csteele]

Yes, nearly every time. Very annoying given that HomeKit is just a DB,

[JDogg016]

Glad I am not the only one. @tonesto7 … any ideas on how to remedy this?

Also, any thoughts on polling and has anyone seen whether polling more frequently (ie. every 10 seconds) impacts hubitat performance.

I am having a s#@t show worth of issues right now and tried to isolate whether it was caused by homekit/hombridge.

[SmartHomePrimer]

I’m not having the same issue, but I’m not using it on a RPi.

I needed more responsive polling so I could use changes in Hubitat virtual switches to trigger Insteon devices and vise-versa, so I am using a 1 second polling time. No issues with either platform for the last 11 days I’ve been running this way.

[Keo]

So I’ve noticed that my hue hub stopped being as responsive and I couldn’t figure out why. I removed all of my custom apps but it wasn’t until I removed homebridge that I’ve seen improvements.

[JDogg016]

I removed and re-installed the hubitat plugin, things have been all quite and responsive for about 15 hours. I think things to focus on to improve the plug-in:

1. Somehow storing room, name, device type data within the plugin so the user does not have to re-build home kit in the event the RPI/container restarts;

2. Somehow being able to stop device attributes from appearing as separate devices. As an example, a contact sensor with a temperature sensor appears as two separate devices. If the user does not want to see one of them the user should be able to have it not appear. This would seemingly require less data to be pushed to home kit and may improve performance.

3. Overall improvements as the plugin relates to the hubitat infrastructure. I think this has a lot to do with polling and the resources placed on the hubitat. I have amended my config.json removing all references to polling within the plugin and have gotten stability… I had polling @ 10 seconds and I think this caused tremendous stress on the hubitat system as automations failed and response time within hubitat plummeted.

Just my thoughts…__