No announcement yet.

There are a lots of nodes in Homebridge !

  • Filter
  • Time
  • Show
Clear All
new posts

  • There are a lots of nodes in Homebridge !


    First i am not talking about beeing able to import HOMEKIT nodes to homeseer. I think this npm packaghe already exist (to mqtt)
    With this package, it seems you would be able to control from mqtt ..the node wich are reals homekit based nodes. ( like the exemple of the ocobee3 thermostat on the page linked.)
    Since the lutron plugin is not able to acess NON-Pro hub anymore and I want my mom to take the hs3 ride ( i gave her my old Lutron non-pro bridge), that could maybe be a way to bring those nodes back to hs3 automation engine.

    What I would like to talk about is the huge number of plugins available on Homebridge. It would be nice to be able to export the nodes from Homebridge to Mqtt, or Node-red, or even better , to Homeseer directly! I do not know a package able to do this yet. ( i have seen this one : but it is not clear if it cans control nodes and reports values directly from Mqtt).

    Any idea ? limitation of this approach? Would it be complicated to make a plugin for this ? Or do you think there is a suitable mqtt approach that i didn't see to accomplish this?

  • #2
    edit: After 2 days with homebridge... this platform is not stable at all. I wont use this as a bulletproof system..

    but ther are a lot a nice nodes on there that a developer could be inspired to make a plugin here


    • #3
      I have a valid config.json as validated by but I get the above error when I load homebridge. Thoughts?

      [2018-10-29 08:22:52] Loaded config.json with 0 accessories and 1 platforms.
      [2018-10-29 08:22:52] ---
      [2018-10-29 08:22:52] No plugins found. See the README for information on installing plugins.
      [2018-10-29 08:22:52] Loading 1 platforms...
      C:\Users\Rich\AppData\Roaming\npm\node_modules\homebridge\li b\api.js:122
      throw new Error("The requested platform '" + name + "' was not registered by any plugin.");

      Error: The requested platform 'HomeSeer' was not registered by any plugin.
      at API.platform (C:\Users\Rich\AppData\Roaming\npm\node_modules\homebridge\l ib\api.js:122:13)
      at Server._loadPlatforms (C:\Users\Rich\AppData\Roaming\npm\node_modules\homebridge\l ib\server.js:316:45)
      at (C:\Users\Rich\AppData\Roaming\npm\node_modules\homebridge\l ib\server.js:86:36)
      at module.exports (C:\Users\Rich\AppData\Roaming\npm\node_modules\homebridge\l ib\cli.js:45:10)
      at Object.<anonymous> (C:\Users\Rich\AppData\Roaming\npm\node_modules\homebridge\b in\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)

      I have a valid config.json as validated by but I get the above error when I load homebridge. Thoghts?


      • #4
        my config starts like this:

        "bridge": {
        "name": "Homebridge",
        "username": "CC:22:3D:E3:CE:30",
        "port": 51826,
        "pin": "031-45-154"
        "platforms": [
        "platform": "HomeSeer",
        "name": "HomeSeer",
        "host": "HTTP://",
        "accessories": [
        "ref": 99,
        "type": "Lightbulb",
        "name": "2nd Flr.Hall",
        "offValue": "0",
        "onValue": "255",
        "can_dim": true,
        "uuid_base": "DimmableLight99"

        SO it seems valid


        • #5
          maybe hombridge is installed loccally and homeseer plugin is not ...or vice versa? Did you read all the content on this site ?

          I can’t help much. This is just by memory , I do not use homebridge


          • #6
            Remember that you must specify a username and password if you have user authentication enabled in HomeSeer. You can ignore this if authentication is not enabled.

            Which implementation or installation instructions did you use?

            I have been very happy with Homebridge and been using it for 2-4 years with no real issues other than that it seems to be more "polling" rather than real-time.

            HomeSeer 2, HomeSeer 3, Allonis myServer, Amazon Alexa Dots, ELK M1G, ISY 994i, HomeKit, BlueIris, and 6 "4k" Cameras using NVR, and integration between all of these systems. Home Automation since 1980.


            • #7
              Seems like it has been done. Do not have the time to test it right now. But will surely do.

              iobroker :


              Node red:



              • #8
                MattL0 , I did find the MQTT Server ioBroker adapter to be problematic but the Client alone adapter seems good. And the client too reported to HomeSeer mqtt but I get nothing coming in to Node-RED mqtt nodes! Strange! I have yet to learn how to set it up to trigger. Time deficiency......

                The People's Advocate.


                • #9
                  I do not use the mqtt adapter from iobroker. I use node red adapter ( which I replaced from my standalone node-red instalation). When you install node-red from the iobroker adapter , you will have an input and a outpout node added. ( and one for polling).
                  I just exported all my node red flows and then imported them into this one. I removed the systemd file and then activated node-red from iobroker.

                  the node-red adapter that comes with iobroker, is 1.7.1 . You can update it to 1.8.0. with this command
                   npm i iobroker.node-red --unsafe-perm
                  from the /opt/iobroker folder.

                  You will also be able to acess nodered from your navigator ( outside of iobroker) by typing Your_machine_ip: NR_port, to get the same view as before ( see second picture)

                  Do not care about my mqtt topic names... i didn't change them when I moved from plex to emby lol.

                  Attached Files


                  • #10
                    From theses twos pictures, you can see how easy it is to get info from iobroker nodes :
                    Attached Files


                    • #11
                      True, I forgot to mention that Node-RED in ioBroker works fine I even managed to hack in from the back end and manually installed Node-RED -NEEO! It's the MQTT Server adapter which doesn't want to play the game!

                      So does your project above imply that you are using an external MQTT Broker or this one : ?

                      Else, I still need time to explore ioBroker

                      The People's Advocate.


                      • #12
                        ha ok got it.

                        Yes installing node manually is a little ''harder ''.

                        I'm using mosquito mqtt broker on the same machine i installed hs3 and iobroker


                        • #13
                          Originally posted by MattL0 View Post
                          ha ok got it.

                          Yes installing node manually is a little ''harder ''.

                          I'm using mosquito mqtt broker on the same machine i installed hs3 and iobroker
                          I think what you did there is the best way. Because in case of system updates it's far easier than running separate raspberry pis although that can also be done using a python script but I have not found to try and set them up. I will try and get me beefy Intel NUC and install everything on for the experience.

                          The People's Advocate.


                          • #14
                            yes That's an advantage, everything on the same pc is easier to manage. But the obvious downpoint is if something fail, and you didint have a nice backup ( i.e clonezilla)... then it is longer to reinstall all the program versus a part of them when it is decentralized.


                            • #15
                              MattL0 , Here it is : . The reason I wanted Emby information like "Now Playing" on a screen outside my Home Theater door!
                              I gathered a few more links :
                              Example : and more on the Magic Mirror : which takes you here :

                              Now, the fact is I have so much on my plate ​ but please share if you nail it.

                              Else, I turned off the remote Node-RED and MQTT Broker then added the Node-RED adapter of ioBroker then inside it I add the mqtt broker node : and everything just works!

                              The People's Advocate.