You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When running versisure-mqtt with an image from Docker Hub, I get an error. Ran it on Docker on a Synology and on a Debian linux system, same error on both systems.
Error 1: TypeError: Cannot read property 'toString' of undefined
at /nodeapp/index.js:146:49
at processTicksAndRejections (internal/process/task_queues.js:95:5)
}
Some information is read and published to MQTT, but it is not complete.
To Reproduce
Redeployed the image several times, this error happens 10 minutes after starting the container.
Expected behavior
No error ;-)
Screenshots
If applicable, add screenshots to help explain your problem.
Describe environment:
OS: Synology and Debian 5.10
Containerisation yes, v20.10.22, build 3a2c30b
Version of Verisure MQTT used: The one in the Docker image on Docker Hub.
Command used to start Verisure MQTT:None
Config file(s)
What's the content of the config file(s) you use?
Entered the correct information in the Env settings when deploying the container.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
When running versisure-mqtt with an image from Docker Hub, I get an error. Ran it on Docker on a Synology and on a Debian linux system, same error on both systems.
Some information is read and published to MQTT, but it is not complete.
To Reproduce
Redeployed the image several times, this error happens 10 minutes after starting the container.
Expected behavior
No error ;-)
Screenshots
If applicable, add screenshots to help explain your problem.
Describe environment:
Config file(s)
What's the content of the config file(s) you use?
Entered the correct information in the Env settings when deploying the container.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: