-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin crashes homebridge with AssertionError #292
Comments
Another error in the log file: [2/8/2023, 7:00:02 AM] [InsteonLocal] Found 1 devices in config Both of these errors only pop up when I enable/connect the Insteon plugin. |
@Rink73 Haven't seen this one before :-) - can you post your config? |
Hello I have this same error. Any update on what it could be? [1/27/2024, 12:45:21 AM] [InsteonLocal] Initializing InsteonLocal platform... |
@languy99 Make sure you have a name defined for the device in your config. |
Old hub crashed, so I have a whole new 2245 hub. Upon installing plugin and adding credentials (without manually adding any devices), I get the following:
[2/8/2023, 7:34:21 AM] AssertionError [ERR_ASSERTION]: Cannot generate setupURI on an accessory that isn't published yet!
at Bridge.Accessory.setupURI (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:994:11)
at Server.setServerStatus (/usr/local/lib/node_modules/homebridge/src/server.ts:155:45)
at Server.teardown (/usr/local/lib/node_modules/homebridge/src/server.ts:199:10)
at signalHandler (/usr/local/lib/node_modules/homebridge/src/cli.ts:93:12)
at process.emit (node:events:390:28)
at process.emit (/usr/local/lib/node_modules/homebridge/node_modules/source-map-support/source-map-support.js:516:21)
[2/8/2023, 7:34:21 AM] [InsteonLocal] Connected to Insteon Model 2245 Hub...
I have the entire hub setup within the Director app with devices and scenes, and everything works great. When looking through the logs, it does list all the devices that I have on the hub, but continues to crash the whole homebridge docker, forcing a continual reboot.
Any help is greatly appreciated!!!!
The text was updated successfully, but these errors were encountered: