Error during HB startup

[RienduPre]

Hi,

I get this error when install the latest (1.45) of the plugin and HB is booting

Load homebridge-instances-platform.InstancesPlatform
[4/25/2019, 10:13:34 PM] TypeError: Cannot read property 'push' of undefined
at InstancesPlatform.configureAccessory (/usr/local/lib/node_modules/homebridge-instances-platform/src/platform.js:150:22)
at Server._configCachedPlatformAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:386:24)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:93:8)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:59:10)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)

Thanks for helping me, Rien

[seydx]

@RienduPre

which homebridge version do you have installed? It seems that homebridge can not handle dynamicPlatform. Or can you set "clearCache": true in config.json, restart and set "clearCache": false and restart again to reset the accessory pls.

btw v1.4.6 is online

[RienduPre]

Hi, I use the latest HB version 4.49. Does ClearCache clear also existing accessories from my HB, I run multiple plugin which I don't want to be cleared.

Thanks, Rien

[seydx]

@RienduPre

No it removes only homebridge instances accessory

[RienduPre]

I'll give it a try as soon as I get home.

[palasinio]

Hi, I have exact the same error. I do not have Telegram configured. I have about 6 instances an one with separated config-ui-x. I never had an accessory, because it’s the 1st try to get it startet. It’s the only plugin in its own instance.

[seydx]

@palasinio

Remove the accessory from homekit and delete you accessories and persist folder

Restart again

[RienduPre]

@RienduPre

No it removes only homebridge instances accessory

I have set ClearCache to true and now it starts without errors. I guess that I now have set it to false again and restart ?

[seydx]

@RienduPre

Yes thats right

[RienduPre]

Ok, lots of new errors now

[4/26/2019, 6:33:57 PM] [InstancesPlatform] [ERROR] Error with CMD: ps -eo pid:1,pmem:1,pcpu:1,etime:1,unit:1,state:1 --no-header | grep homebridge
[4/26/2019, 6:34:05 PM] [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while fetching service informations!
[4/26/2019, 6:34:05 PM] [InstancesPlatform] [ERROR] Error with CMD: ps -eo pid:1,pmem:1,pcpu:1,etime:1,unit:1,state:1 --no-header | grep homebridge
[4/26/2019, 6:34:11 PM] [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while fetching services!
[4/26/2019, 6:34:11 PM] [InstancesPlatform] [ERROR] Error with CMD: systemctl list-unit-files | grep enabled | grep homebridge
[4/26/2019, 6:34:12 PM] [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while fetching service informations!
[4/26/2019, 6:34:12 PM] [InstancesPlatform] [ERROR] Error with CMD: ps -eo pid:1,pmem:1,pcpu:1,etime:1,unit:1,state:1 --no-header | grep homebridge
[4/26/2019, 6:34:19 PM] [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while fetching service informations!
[4/26/2019, 6:34:19 PM] [InstancesPlatform] [ERROR] Error with CMD: ps -eo pid:1,pmem:1,pcpu:1,etime:1,unit:1,state:1 --no-header | grep homebridge
[4/26/2019, 6:34:26 PM] [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while fetching service informations!
[4/26/2019, 6:34:26 PM] [InstancesPlatform] [ERROR] Error with CMD: ps -eo pid:1,pmem:1,pcpu:1,etime:1,unit:1,state:1 --no-header | grep homebridge
[4/26/2019, 6:34:33 PM] [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while fetching service informations!
[4/26/2019, 6:34:33 PM] [InstancesPlatform] [ERROR] Error with CMD: ps -eo pid:1,pmem:1,pcpu:1,etime:1,unit:1,state:1 --no-header | grep homebridge
[4/26/2019, 6:34:40 PM] [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while fetching service informations!
[4/26/2019, 6:34:40 PM] [InstancesPlatform] [ERROR] Error with CMD: ps -eo pid:1,pmem:1,pcpu:1,etime:1,unit:1,state:1 --no-header | grep homebridge
[4/26/2019, 6:34:41 PM] [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while fetching services!
[4/26/2019, 6:34:41 PM] [InstancesPlatform] [ERROR] Error with CMD: systemctl list-unit-files | grep enabled | grep homebridge
[4/26/2019, 6:34:47 PM] [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while fetching service informations!
[4/26/2019, 6:34:47 PM] [InstancesPlatform] [ERROR] Error with CMD: ps -eo pid:1,pmem:1,pcpu:1,etime:1,unit:1,state:1 --no-header | grep homebridge
[4/26/2019, 6:34:54 PM] [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while fetching service informations!
[4/26/2019, 6:34:54 PM] [InstancesPlatform] [ERROR] Error with CMD: ps -eo pid:1,pmem:1,pcpu:1,etime:1,unit:1,state:1 --no-header | grep homebridge
[4/26/2019, 6:35:01 PM] [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while fetching service informations!
[4/26/2019, 6:35:01 PM] [InstancesPlatform] [ERROR] Error with CMD: ps -eo pid:1,pmem:1,pcpu:1,etime:1,unit:1,state:1 --no-header | grep homebridge
[4/26/2019, 6:35:08 PM] [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while fetching service informations!
[4/26/2019, 6:35:08 PM] [InstancesPlatform] [ERROR] Error with CMD: ps -eo pid:1,pmem:1,pcpu:1,etime:1,unit:1,state:1 --no-header | grep homebridge
[4/26/2019, 6:35:11 PM] [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while fetching services!
[4/26/2019, 6:35:11 PM] [InstancesPlatform] [ERROR] Error with CMD: systemctl list-unit-files | grep enabled | grep homebridge
[4/26/2019, 6:35:15 PM] [InstancesPlatform] [ERROR] Homebridge Instances: An error occured while fetching service informations!
[4/26/2019, 6:35:15 PM] [InstancesPlatform] [ERROR] Error with CMD: ps -eo pid:1,pmem:1,pcpu:1,etime:1,unit:1,state:1 --no-header | grep homebridge

[seydx]

Which system u use? @RienduPre

[RienduPre]

The plugin runs on HB Docker and I have multiple HB dockers and RPi based HB's

[seydx]

@RienduPre

Pls open terminal and post following command

ps -eo pid:1,pmem:1,pcpu:1,etime:1,unit:1,state:1 --no-header | grep homebridge

Post output pls

[palasinio]

@SeydX Okay, this really fixed it (maybe together with 2 later versions). There are two curious things: Plugin /usr/local/lib/node_modules/homebridge-instances-platform requires Node version of ^8.9.1 which does not satisfy the current Node version of v9.3.0. You may need to upgrade your installation of Node. and

[2019-4-27 17:06:39] [InstancesPlatform] [INFO] Homebridge Instances: Adding new Service:  Instance
[2019-4-27 17:06:39] [InstancesPlatform] [INFO] Homebridge Instances: Adding new Service:  Lgtv
[2019-4-27 17:06:39] [InstancesPlatform] [INFO] Homebridge Instances: Adding new Service:  Ranger
[2019-4-27 17:06:39] [InstancesPlatform] [INFO] Homebridge Instances: Adding new Service:  Test
[2019-4-27 17:06:39] [InstancesPlatform] [INFO] Homebridge Instances: Adding new Service:  Ui
[2019-4-27 17:06:39] [InstancesPlatform] [INFO] Homebridge Instances: Adding new Service:  Weather
[2019-4-27 17:06:39] [InstancesPlatform] [INFO] Homebridge Instances: Adding new Service: .timer                       Enabled

I have tested the config-ui as independent service. This one is found as "Ui". Guess I can "fix" this with the exclude. Is it possible to be aware of the separate config-ui-x services?

But my original homebridge instance is started with a timer (homebridge.service is disabled and a homebridge.timer added to start the homebridge.service later. This one is (false) found as ".timer" and the "hombridge" instance is not found (I guess, cause it's disabled). Do you have an idea how to get my homebridge instance displayed?

regards,

[seydx]

Will add this to my list thx @palasinio

[ghost]

Hey, I have the same problem and my output is:

/homebridge # ps -eo pid:1,pmem:1,pcpu:1,etime:1,unit:1,state:1 --no-header | grep homebridge ps: unrecognized option: no-header BusyBox v1.29.3 (2019-01-24 07:45:10 UTC) multi-call binary.

Usage: ps [-o COL1,COL2=HEADER]

Show list of processes

    -o COL1,COL2=HEADER     Select columns for display

/homebridge #