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

9.27.8 / 14.3.7 - crashed after working for some hours after update #4053

Closed
3 tasks done
kpanchen opened this issue Dec 5, 2024 · 3 comments
Closed
3 tasks done
Labels
bug Something isn't working

Comments

@kpanchen
Copy link

kpanchen commented Dec 5, 2024

Checklist

  • I am not using Home Assistant. Or: a developer has told me to come here.
  • I have checked the troubleshooting section and my problem is not described there.
  • I have read the changelog and my problem is not mentioned there.

Deploy method

PKG executable

Z-Wave JS UI version

9.27.8

ZwaveJS version

14.3.7

Describe the bug

After update from 9.27.7 worked for some hours and stopped responding. UI is not responding, MQTT seems publishing but not responding to updates. Restart won't fix and issue. Reverting back to 9.27.7 works fine.

In the log just see the line:
2024-12-05T15:40:29.423Z DRIVER Dropping message because the driver is not ready to handle it yet.

Line repeats from time to time.

Logs attached. Note: that log includes both failure and working normally after reverting back.
Let me know if more information required.

To Reproduce

Update to a new version.

Expected behavior

Operate normally

zwavejs_current.zip
z-ui_current.zip

Additional context

Not sure about this error:
2024-12-05T15:40:36.525Z CONFIG Writing the device index to disk failed: ENOENT: no such file or directory, op en '/snapshot/build/node_modules/@zwave-js/config/config/devices/index.json'

@kpanchen kpanchen added the bug Something isn't working label Dec 5, 2024
@robertsLando
Copy link
Member

You should set the env var ZWAVEJS_EXTERNAL_CONFIG=./store/.config-db fix this command in order to customize the destination folder

@robertsLando
Copy link
Member

Starting from next minor version setting that env var will not be needed anymore: #4055

@kpanchen
Copy link
Author

Thanks!! Had to do a bit of googling but understand the issue now, guess I'll wait for a fix on your side, prev version just works fine! Thanks a lot for the answer!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants