homebridge-loxone-control

[rvetere]

Plugin Name

homebridge-loxone-control

Link To NPM Package

https://www.npmjs.com/package/homebridge-loxone-control

Plugin Icon (Optional)

[github-actions]

✅ Pre-checks completed successfully.

[rvetere]

it is a completely different plugin compared to the existing loxone proxies. the reason for this is that i have zero access to the loxone miniserver. this plugin is working around this by intercepting the web interface websocket connection. it is a complete rewrite of my first attempt "homebridge-loxone-puppeteer" and compared to that, i could delete ~90% of the code because of the new web-socket approach - it is much cleaner and simpler now (and much stabler, i use it on daily basis now for 2 weeks without reboot)

[bwp91]

Hi @rvetere

If a user has not filled out any of the configuration for the plugin, is there any reason to start the HTTP server?

[11/02/2024, 03:45:59] [LoxoneControl] Http server listening on 18081...

[rvetere]

Oh, good catch - will change that behavior! ;-)

[rvetere]

Ok, just released v1.0.2 with a fix for that

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

• General
  • The plugin must be of type dynamic platform.
  • The plugin must not offer the same nor less functionality than that of any existing verified plugin.
• Repo
  • The plugin must be published to NPM and the source code available on a GitHub repository, with issues enabled.
  • A GitHub release should be created for every new version of your plugin, with release notes.
• Environment
  • The plugin must run on all supported LTS versions of Node.js, at the time of writing this is Node v18 and v20.
  • The plugin must successfully install and not start unless it is configured.
  • The plugin must not execute post-install scripts that modify the users' system in any way.
  • The plugin must not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.
• Codebase
  • The plugin must implement the Homebridge Plugin Settings GUI.
  • The plugin must not contain any analytics or calls that enable you to track the user.
  • If the plugin needs to write files to disk (cache, keys, etc.), it must store them inside the Homebridge storage directory.
  • The plugin must not throw unhandled exceptions, the plugin must catch and log its own errors.

---

---

Comment /check to run checks again.

[bwp91]

Hi @rvetere

A couple of things:

1. Would you say that this was true for the plugin?

   If the plugin needs to write files to disk (cache, keys, etc.), it must store them inside the Homebridge storage directory.

   This is not a trick question, I was just having trouble verifying this and thought you would probably know better!

2. with a config of:

        {
            "name": "LoxoneControl",
            "loxoneMiniServerId": "dsadasd",
            "loxoneUser": "dsadasd",
            "loxonePassword": "sadasdasd",
            "chromiumPath": "dsadasd",
            "platform": "LoxoneControl"
        }

   Homebridge went into a crash loop which affected my other plugins:

   [16/03/2024, 18:56:07] [LoxoneControl] Initializing LoxoneControl platform...
   [16/03/2024, 18:56:07] [LoxoneControl] 🚀 Initializing loxone web interface..
   [16/03/2024, 18:56:08] [LoxoneControl] Http server listening on 18081...
   [16/03/2024, 18:56:08] Error: Failed to launch the browser process! spawn dsadasd ENOENT
   TROUBLESHOOTING: https://pptr.dev/troubleshooting
    at ChildProcess.onClose (/usr/local/lib/node_modules/homebridge-loxone-control/node_modules/@puppeteer/browsers/src/launch.ts:393:11)
    at ChildProcess.emit (node:events:518:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:292:12)
    at onErrorNT (node:internal/child_process:484:16)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
   [16/03/2024, 18:56:09] Got SIGTERM, shutting down Homebridge...
   

   I appreciate my config is random letters but the plugin still needs to catch errors properly (and log them) but not terminate the process, just stop the plugin from loading any more.