Skip to content
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

After update from UI cannot start it anymore #263

Closed
stich86 opened this issue Apr 21, 2019 · 3 comments
Closed

After update from UI cannot start it anymore #263

stich86 opened this issue Apr 21, 2019 · 3 comments
Labels

Comments

@stich86
Copy link

stich86 commented Apr 21, 2019

Hi,

i've updated the HB (first) and UI (after second restart) itself from the UI (i'm running oznu/homebridge Docker container) without update the container itself.

After restart HB running again with anyissue, then update the UI plugin on second reboot doesn't start anymore with this error:

(node:7717) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'find' of undefined
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-config-ui-x/dist/main.js:133215:47)
    at Generator.next (<anonymous>)
    at fulfilled (/usr/local/lib/node_modules/homebridge-config-ui-x/dist/main.js:133201:58)
(node:7717) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)

I've already tried to destroy container, pull latest version and deploy it again without success. May be I need to destroy also the volume mounted as /homebridge and setup it again on my HomeKit App?

Thanks in advance!

@oznu
Copy link
Member

oznu commented Apr 22, 2019

I see what the problem is.. fix incoming.

Your config.json file does not contain a "platforms": [] array.

@oznu oznu closed this as completed in faa276f Apr 22, 2019
@oznu
Copy link
Member

oznu commented Apr 22, 2019

Updating the plugin or pulling the latest version of the docker image should fix this. Thanks for reporting.

@oznu oznu added the docker label Apr 22, 2019
@stich86
Copy link
Author

stich86 commented Apr 22, 2019

thanks man!
it works now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants