Homebridge stopped von alleine

[wuast94]

versuche gerade homebridge zum laufen zu bekommen. allerdings fährt der server nach dem hochfahren relativ schnell mit einem SIGTERM wieder runter...

davor findet bzw legt er die ganzen devices/readings von fhem an. zum Schluss wie man sieht kamen noch ein paar werte und danach nix mehr.

Code Auswählen Erweitern

[7/3/2019, 4:15:30 PM] [FHEM] Initializing platform accessory 'ambilight'...
[7/3/2019, 4:15:30 PM] [FHEM] creating services for ambilight
[7/3/2019, 4:15:30 PM] [FHEM] information service for ambilight
[7/3/2019, 4:15:30 PM] [FHEM] manufacturer, model and serial number characteristics for ambilight
[7/3/2019, 4:15:30 PM] [FHEM] name (siriName) characteristic for ambilight
[7/3/2019, 4:15:30 PM] [FHEM] Lightbulb service for ambilight
[7/3/2019, 4:15:30 PM] [FHEM] Hue characteristic for ambilight:rgb
[7/3/2019, 4:15:30 PM] [FHEM] Saturation characteristic for ambilight:rgb
[7/3/2019, 4:15:30 PM] [FHEM] Brightness characteristic for ambilight:rgb
[7/3/2019, 4:15:30 PM] [FHEM] Lightbulb service for ambilight (TV.Licht)
[7/3/2019, 4:15:30 PM] [FHEM] On(TV.Licht) characteristic for ambilight:state
[7/3/2019, 4:15:30 PM] [FHEM] Lightbulb service for ambilight (Umgebungslicht)
[7/3/2019, 4:15:30 PM] [FHEM] On(Umgebungslicht) characteristic for ambilight:state
[7/3/2019, 4:15:30 PM] [FHEM] Lightbulb service for ambilight (Effekt)
[7/3/2019, 4:15:30 PM] [FHEM] On(Effekt) characteristic for ambilight:state
[7/3/2019, 4:15:30 PM] TypeError: Cannot read property 'toString' of undefined
at Accessory.addService (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:154:59)
at /usr/lib/node_modules/homebridge/lib/server.js:471:19
at Array.forEach (<anonymous>)
at Server._createAccessory (/usr/lib/node_modules/homebridge/lib/server.js:451:14)
at Server.<anonymous> (/usr/lib/node_modules/homebridge/lib/server.js:413:32)
at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:16:19
at FHEMPlatform.<anonymous> (/usr/lib/node_modules/homebridge-fhem/index.js:1192:22)
at Request.self.callback (/usr/lib/node_modules/homebridge-fhem/node_modules/request/request.js:185:22)
at Request.emit (events.js:196:13)
at Request.<anonymous> (/usr/lib/node_modules/homebridge-fhem/node_modules/request/request.js:1161:10)
[7/3/2019, 4:15:30 PM] Got SIGTERM, shutting down Homebridge...
2019-07-03 16:15:30 caching: WZ_Strom_TV-power: 388.4 W
[7/3/2019, 4:15:30 PM] [FHEM] caching: Custom Power: 388.4 (as number; from '388.4 W')
2019-07-03 16:15:31 caching: Temp_Schlafzimmer-temperature: 23.5
[7/3/2019, 4:15:31 PM] [FHEM] caching: CurrentTemperature: 23.5 (as number; from '23.5')
2019-07-03 16:15:31 caching: Temp_Schlafzimmer-temperature: 23.5
[7/3/2019, 4:15:31 PM] [FHEM] caching: CurrentTemperature: 23.5 (as number; from '23.5')
2019-07-03 16:15:32 caching: WZ_Strom_TV-power: 366.6 W
[7/3/2019, 4:15:32 PM] [FHEM] caching: Custom Power: 366.6 (as number; from '366.6 W')
2019-07-03 16:15:34 caching: WZ_Strom_TV-power: 358.5 W
[7/3/2019, 4:15:34 PM] [FHEM] caching: Custom Power: 358.5 (as number; from '358.5 W')

[wuast94]

Ok habe mittlerweile heraus gefunden das es am Ambilight(Hyperion) device liegt .. nehme ich das aus dem Homekit räum raus klappt es.