homebridge-sma-home-manager

[wimleers]

homebridge-sma-home-manager

[bwp91]

Hi @wimleers

Re (1) - there are still plenty of users who configure stuff directly with JSON, so we just need to make sure that any 'config issues' are caught properly by its plugin - to make sure that it does not send homebridge into a crash loop and therefore not stop any other plugin from functioning. homebridge-config-ui-x has made things so much easier for a lot of users, but please don't assume that every user will be using this.

Re (2) - okay 👍 - no action needed from you, thanks for explaining

[bwp91]

Great! Once ready, please reply on here with a comment just saying /check and we can try again 👍

[github-actions]

✅ Pre-checks completed successfully.

[bwp91]

A basic config of

        {
            "platform": "SMAHomeManager",
            "_bridge": {
                "username": "0E:E7:D4:44:A2:0A",
                "port": 46564
            }
        }

sends Homebridge into a crash loop:

[26/03/2023, 18:04:39] Registering platform 'homebridge-sma-home-manager.SMAHomeManager'
[26/03/2023, 18:04:39] [homebridge-sma-home-manager] Loaded homebridge-sma-home-manager v1.1.1 child bridge successfully
[26/03/2023, 18:04:39] Loaded 0 cached accessories from cachedAccessories.0EE7D444A20A.

/usr/local/lib/node_modules/homebridge-sma-home-manager/index.js:285
                Object.keys(signalNames).forEach(id => {
                           ^
TypeError: Cannot read properties of undefined (reading 'offGrid')
    at /usr/local/lib/node_modules/homebridge-sma-home-manager/index.js:286:35
    at Array.forEach (<anonymous>)
    at SMAHomeManager.accessories (/usr/local/lib/node_modules/homebridge-sma-home-manager/index.js:285:28)
    at /usr/local/lib/node_modules/homebridge/src/bridgeService.ts:534:24
    at new Promise (<anonymous>)
    at BridgeService.loadPlatformAccessories (/usr/local/lib/node_modules/homebridge/src/bridgeService.ts:528:12)
    at ChildBridgeFork.startBridge (/usr/local/lib/node_modules/homebridge/src/childBridgeFork.ts:155:36)
[26/03/2023, 18:04:39] [homebridge-sma-home-manager] Child bridge process ended
[26/03/2023, 18:04:39] [homebridge-sma-home-manager] Process Ended. Code: 1, Signal: null
[26/03/2023, 18:04:46] [homebridge-sma-home-manager] Restarting Process...

---

Also does your plugin ever wait for the didFinishLaunching event? Im not sure if your plugin type needs to or not. But I wonder if this is the reason of the logging

[26/03/2023, 18:23:24] [homebridge-sma-home-manager] This plugin is taking long time to load and preventing Homebridge from starting. See https://homebridge.io/w/JtMGR for more info.

and the icon never turning to green?

[wimleers]

@bwp91

1. The support for homebridge-config-ui-x would never result in that sort of configuration as far as I can tell? 😅
2. The plugin will never launch unless both an SMA solar inverter is discovered (using mDNS/DNS-SD) and a SMA Home Manager (using a Speedwire multicast subscription, where this device is broadcasting a datagram every second) are found. You likely do not have either device on your network, which is why the plugin takes so long to launch: it keeps trying indefinitely. I'm happy to change that to a limited period of time of course. But: A) the logging should make it pretty clear, B) it's then absolutely pointless to run this plugin.

(Over here it typically takes a few seconds to discover the devices, connect, and then launch.)

[wimleers]

Makes sense, will address 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.

[wimleers]

I will follow up on this in the coming week.