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
I have used your node for a long time in a dedicated Docker Node-Red instance running in "BRIDGED" mode and everything works fine
When changing the Docker from "BRIDGED" to "HOST" mode (no other changes to code),
Node-Red is crashing at startup with your node
The dedicated Docker-Node-red instance is only for your Vacuum node (v.2.5.0) and no other flows are running
I had this issue for a while ( I think the issue was reported in 2021/2022 the first time) but could never sort it out, and I had to run your node in a dedicated environment
** Hardware / Software **
- Linux with Docker
Node Red V4
The text was updated successfully, but these errors were encountered:
This issue comes from https://www.npmjs.com/package/node-mihome which is the dependancy of my package. The package node-mihome has not received updates for 4 years but still works. Error message says that "EADDINUSE" what could indicate that the port is busy. Maybe you need to open port 4321 (I found it in source codes of node-mihome)
Hi,
I have used your node for a long time in a dedicated Docker Node-Red instance running in "BRIDGED" mode and everything works fine
When changing the Docker from "BRIDGED" to "HOST" mode (no other changes to code),
Node-Red is crashing at startup with your node
The dedicated Docker-Node-red instance is only for your Vacuum node (v.2.5.0) and no other flows are running
I had this issue for a while ( I think the issue was reported in 2021/2022 the first time) but could never sort it out, and I had to run your node in a dedicated environment
** Hardware / Software **
- Linux with Docker
The text was updated successfully, but these errors were encountered: