homebridge-instances-platform von SeydX

SeydX · 22. April 2019

v1.3.5 online

Glaube das wars dann auch mit den Bugs

Btw Available Disk Space wurde hinzugefügt

SeydX · 22. April 2019

und weiter gehts mit der hoffentlich letzten Neuerung

v1.4.0 ist online

Habe es endlich geschafft Journalctl inkl Telegram Ressourcen schonend zu implementieren.

Bei mir hat es eine CPU Auslastung von 0,9% und RAM von 0,6%

Beim PI müsste es etwas höher sein, aber akzeptabel. Bitte berichten!

Achja, nun zur Neuerung:

Es ist nun möglich unter Config.json den "Notifier" zu aktivieren. Dieser sendet euch eine Telegram Nachricht wenn ein Dienst gestoppt wird oder aufgrund eines Fehlers neu startet.

dazu unter config.json folgendes eingeben:

Code

     "notifier":{
       "active": true,
       "token": "TELEGRAMTOKEN",
       "chatID": "TELEGRAMCHATID"
     }

Liebe Grüße

Marco Schmidt · 22. April 2019

Zitat von SeydX
und weiter gehts mit der hoffentlich letzten Neuerung

v1.4.0 ist online

Habe es endlich geschafft Journalctl inkl Telegram Ressourcen schonend zu implementieren.

Bei mir hat es eine CPU Auslastung von 0,9% und RAM von 0,6%

Beim PI müsste es etwas höher sein, aber akzeptabel. Bitte berichten!

Achja, nun zur Neuerung:

Es ist nun möglich unter Config.json den "Notifier" zu aktivieren. Dieser sendet euch eine Telegram Nachricht wenn ein Dienst gestoppt wird oder aufgrund eines Fehlers neu startet.

dazu unter config.json folgendes eingeben:
Code
     "notifier":{
       "active": true,
       "token": "TELEGRAMTOKEN",
       "chatID": "TELEGRAMCHATID"
     }
Liebe Grüße
Alles anzeigen

Code

npm ERR! 404 Not Found - GET https://registry.npmjs.org/@seydx%2fjournalctl - Not found
npm ERR! 404 
npm ERR! 404  '@seydx/journalctl@^1.0.0' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'homebridge-instances-platform'
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-04-22T08_38_21_849Z-debug.log

Alles anzeigen

Krocko · 22. April 2019

Gleicher Fehler bei mir.

vgnsxe · 22. April 2019

Sams here

SeydX · 22. April 2019

Marco Schmidt Krocko @vgnsxe

sollte jetzt gehen, Package war auf "Privat" gestellt

vgnsxe · 22. April 2019

Geht, konnte installiert werden, Telegram hab ich auch integriert.

Wie kann jetzt testen, ob ich vin Telegram ne Info kriege?

SeydX · 22. April 2019

@vgnsxe

benutzt du nur ein Service oder mehrere?

vgnsxe · 22. April 2019

Homebridge als eine Instanz und durch das update, config-ui-x als separate Instanz, thats it.

Bin halt noch eher am Testen des plugins fuer ein moegliches zukuenftiges Setup oder fuer Freunde, die ganz neu dabei sind und fuer die ich das Ganze einrichten sollte.

SeydX · 22. April 2019

@vgnsxe

Update grad das Plugin damit auch nur ein Service unterstützt wird, update kommt gleich

Krocko · 22. April 2019

SeydX ich habe beim homebridge-harmony Plugin die beta installiert (1.0.0.rc1), trotzdem zeigt mir dein Plugin ein Update an 0.7.0).
Kann man da etwas machen?

SeydX · 22. April 2019

Krocko

Nein es werden nur Versionen mit "X.X.X" Format unterstützt

SeydX · 22. April 2019

v1.4.1 ist online

@vgnsxe

Nach Update kannst du ja mal folgendes machen um es zu testen:

Einfach service stoppen (systemctl stop...) oder neustarten (systemctl restart...)

lg

vgnsxe · 22. April 2019

SeydX

Update installiert, homebridge neugestartet, danach manuell uebers terminal sudo systemctl restart homebridge.service ausgefuhert, in der config-ui-x geprueft. Homebridge wurde gestoppt und neu gestartet. Alles ist wieder online, aber keine Telegram Nachricht.

Alle Nachrichten direkt uebers Telegram Plugin eingebunden in Szenen/Automationen laufen, somit kann es auch nicht am Token etc liegen.

Ich vermute ich muesste natuerlich das Plugin in eine separate Instanz umziehen, weil so wird es ja selbst neugestartet und laeuft nicht gleichzeitig um etwas auszufuehren, oder?

Edit: hab den Fehler gefunden, ich hatte die Filter vergessen. Danke Marco Schmidt fuer das posten deiner config. Jetzt laeuft es bei mir.

Krocko · 22. April 2019

Ich nutze kein Telegram. Bei mir startet jetzt die Instanz nicht mehr.

Code

Apr 22 17:09:29 raspberrypi homebridge[3680]: TypeError: Cannot read property 'active' of undefined
Apr 22 17:09:29 raspberrypi homebridge[3680]:     at new InstancesPlatform (/usr/local/lib/node_modules/homebridge-instances-platform/src/platform.js:47:34)
Apr 22 17:09:29 raspberrypi homebridge[3680]:     at Server._loadPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:337:32)
Apr 22 17:09:29 raspberrypi homebridge[3680]:     at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:90:36)
Apr 22 17:09:29 raspberrypi homebridge[3680]:     at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:59:10)
Apr 22 17:09:29 raspberrypi homebridge[3680]:     at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
Apr 22 17:09:29 raspberrypi homebridge[3680]:     at Module._compile (internal/modules/cjs/loader.js:816:30)
Apr 22 17:09:29 raspberrypi homebridge[3680]:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:827:10)
Apr 22 17:09:29 raspberrypi homebridge[3680]:     at Module.load (internal/modules/cjs/loader.js:685:32)
Apr 22 17:09:29 raspberrypi homebridge[3680]:     at Function.Module._load (internal/modules/cjs/loader.js:620:12)
Apr 22 17:09:29 raspberrypi homebridge[3680]:     at Function.Module.runMain (internal/modules/cjs/loader.js:877:12)
Apr 22 17:09:29 raspberrypi homebridge[3680]: Got SIGTERM, shutting down Homebridge...
Apr 22 17:09:34 raspberrypi systemd[1]: homebridge-instances.service: Main process exited, code=exited, status=143/n/a
Apr 22 17:09:34 raspberrypi systemd[1]: homebridge-instances.service: Unit entered failed state.
Apr 22 17:09:34 raspberrypi systemd[1]: homebridge-instances.service: Failed with result 'exit-code'.

Alles anzeigen

Wenn ich in der config.json notifier.active auf false setze, bekomme ich folgenden Fehler.

Code

Apr 22 17:07:29 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:07:29 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:07:29 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:07:29 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:07:29 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:07:29 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:07:34 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: homebridge-cmd.service stopped!
Apr 22 17:07:34 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:07:34 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: homebridge-cmd.service stopped!
Apr 22 17:07:34 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: homebridge-cmd.service stopped!
Apr 22 17:07:34 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:07:34 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:07:34 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:07:34 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:07:34 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:07:34 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:07:34 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:07:34 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:07:58 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:07:58 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:07:58 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:08:01 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:08:01 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:08:01 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:08:01 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:08:01 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:08:01 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:08:01 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:08:01 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:08:01 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:08:01 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:08:01 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:08:01 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:08:01 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [WARN] Homebridge Instances: Homebridge stopped!
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:08:02 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:09:20 raspberrypi systemd[1]: Stopping Node.js HomeKit Server...
Apr 22 17:09:20 raspberrypi homebridge[31719]: Got SIGTERM, shutting down Homebridge...
Apr 22 17:09:20 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while sending telegram notification!
Apr 22 17:09:20 raspberrypi homebridge[31719]: [InstancesPlatform] [ERROR] Error: Failed to load data, status code:404
Apr 22 17:09:25 raspberrypi systemd[1]: homebridge-instances.service: Main process exited, code=exited, status=143/n/a
Apr 22 17:09:25 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
Apr 22 17:09:25 raspberrypi systemd[1]: homebridge-instances.service: Unit entered failed state.
Apr 22 17:09:25 raspberrypi systemd[1]: homebridge-instances.service: Failed with result 'exit-code'.

Alles anzeigen

Marco Schmidt · 22. April 2019

Bei mir nach Update:

Code

Apr 22 18:41:52 homebridge homebridge[3480]: [2019-4-22 18:41:52] TypeError: Cannot read property 'active' of undefined
Apr 22 18:41:52 homebridge homebridge[3480]:     at new InstancesPlatform (/usr/local/lib/node_modules/homebridge-instances-platform/src/platform.js:47:34)
Apr 22 18:41:52 homebridge homebridge[3480]:     at Server._loadPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:337:32)
Apr 22 18:41:52 homebridge homebridge[3480]:     at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:90:36)
Apr 22 18:41:52 homebridge homebridge[3480]:     at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:59:10)
Apr 22 18:41:52 homebridge homebridge[3480]:     at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
Apr 22 18:41:52 homebridge homebridge[3480]:     at Module._compile (internal/modules/cjs/loader.js:816:30)
Apr 22 18:41:52 homebridge homebridge[3480]:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:827:10)
Apr 22 18:41:52 homebridge homebridge[3480]:     at Module.load (internal/modules/cjs/loader.js:685:32)
Apr 22 18:41:52 homebridge homebridge[3480]:     at Function.Module._load (internal/modules/cjs/loader.js:620:12)
Apr 22 18:41:52 homebridge homebridge[3480]:     at Function.Module.runMain (internal/modules/cjs/loader.js:877:12)
Apr 22 18:41:52 homebridge homebridge[3480]: [2019-4-22 18:41:52] Got SIGTERM, shutting down Homebridge...

Alles anzeigen

Marco Schmidt · 22. April 2019

So läuft jetzt mit folgender Config:

Code

{
            "platform": "InstancesPlatform",
            "startParam": "home",
            "clearCache": false,
            "sudo": false,
            "temperature": {
                "active": false
            },
            "notifier": {
                "active": true,
                "token": "xxxxx",
                "chatID": "xxxxx",
                "filter": [
                    "Main process exited",
                    "Error",
                    "error",
                    "ERROR"
                ],
                "spamInterval": 1
            }
        }

Alles anzeigen

Krocko · 22. April 2019

Marco, nutzt du telegram?
Funktioniert es bei dir ohne telegram?

vgnsxe · 22. April 2019

Wie oben schon erwaehnt, laeuft es jtezt bei mir. Habe soeben die Nachricht erhalten, dass homebridge gestoppt wurde, nachdem ich meine condig aktualisiert hab und neu gestartet hab. Welchen filter muesste ich noch hinterlegen um eine Nachricht zu erhalten, wenn homebridge erfolgreich neu gestartet waere? "Homebridge is running"?

Marco Schmidt · 22. April 2019

Zitat von Max Mustermann

Marco, nutzt du telegram?
Funktioniert es bei dir ohne telegram?

Ja, nachdem ich Telegram eingetragen habe, gehts, vorher ohne Telegram gings nicht.

Teilen