With the Homebridge and Hubitat packages on node red i have integrated my nest protects into Hubitat from Homebridge to node red.
I also use it so that I can run two Hubitat instances of node red. I've found Hubitat only allows one instance of node red. So by moving switches I need into Homebridge i can basically run two separate instances of Hubitat node red.
So one node red utilizes the smoke detectors and triggers my emergency switch to set off my diy security alarm. Node red has a better Chromecast integration so i play a file from github on repeat over my Google Homes when this switch is turned by either smoke or co detected.
Another sits on my vpn raspberry pi which has Homebridge switches from Hubitat. These send terminal commands to the raspberry pi to auto connect to the particular vpn servers and automates my Chromecast with Google tv and my android tvs....such as launching my mlb at bat app when the vpn connects to the California server and presses buttons on the app to auto start the game.
This is one instance of node red. It's an always on NordVPN AP...and is technically on another network, hence needing another instance of node red to run it. The first switch is from HOOBS.
Notice I also have 2 hubs connected - C-5 and C-7. Used to have a C-4 ("NET Hub") as well but it died and I moved stuff over to the C-5 but kept that stuff in a separate maker instance. For NR all I had to do was edit the NET Hub config and point it to the C-5 (edit the token and webhook stuff).
Yep that's how you do it! I didn't realize you could the first time I connected NR either. Just make sure your webhook config has a different url like:
http://[your NR address]:1880/hubitat/webhook_instance1
http://[your NR address]:1880/hubitat/webhook_instance2
also set the token and Application ID to the proper maker instance.
then in maker make sure you include the same url...
Sorry can't help you there.. I put my google home device away as I was already using Alexa and now Apple Home. Still too many cloud things for my comfort...
LMAO. Thing is every time I learn something new like this I go further down the rabbit hole. This morning I had one instance of Maker API now I have 4 lol. 2 node red ones and 2 for the Hubitat Custom dashboard app on android haha.
I am confused about the makerapi plugin. I use the Homebridge Hubitat Tonesto7 plugin. Why would I need Makerapi plugin or what can I do with it I cant do with Homebridge Hubitat Tonesto7?
The MakerAPI HomeBridge plugin has the advantage of no custom code on the Hubitat hub. It simply uses the built-in MakerAPI app on the hub. I have been using it for quite some time, and it just works for all my needs. It was also available before Tonesto7’s current solution.
Tonesto7’s plugin requires a custom app on the Hubitat hub. As such, it is more purpose built for the specific function of supporting its companion HomeBridge plugin.
Both a very good solutions. If what you have works well for you, then I see no reason to change anything. If not, it is very nice to have options!
Likewise. Been using it for a year. Its very stable and meets my needs. One difference that may matter to @cdikland is that @dan.t's plugin requires a tiny bit of config file editing, whereas it is my understanding that @tonesto7's does not.
Correct, @tonesto7's does not require manually editing of the config file. I was using @dan.t's MakerAPI plugin for a long time without any issues, but switched to Homebridge v2 because of its simplified capability filtering. I have a bunch of Iris V1 sensors that were reporting tampering that I did not want to reset. With Homebridge v2 it is easy to filter out this capability without manually editing the Homebridge config file.
I have used both and they are both great so either one will do. If you encounter issues with one you can always try the other. In fact you can run them both simultaneously if you really want to.. ( I did for some testing ). Ultimately I am using Tonestos because that's what I started with but would find no issue in changing if needed. It's really nice to be able to have a choice. Really appreciate both @dan.t's and @tonesto7's hard work in giving us this very useful capability!!!
