-
-
Notifications
You must be signed in to change notification settings - Fork 17
Description
Bug Description
I have been using vsh for some time now on Node-Red v3.1.11 in a docker container. Works great - thanks.
Today I tried to update to my flows to Node-Red V4.0.2 and now all my vsh nodes have the status
ERROR ETIMEDOUT Periodically Retrying
The log file is full of lines like :
3 Aug 13:25:18 - [info] [vsh-connection:xxx@xxx.com] MQTT: publish to topic vsh/vsht-1d38eb10-dc54-4296-95c5-f7780f16e39a/changeReport: {"template":"TEMPERATURE_SENSOR","endpointId":"vshd-f7149c0d8a33ac0b","properties":[{"namespace":"Alexa.TemperatureSensor","name":"temperature","value":{"value":21.5,"scale":"CELSIUS"},"changed":true}],"correlationToken":"","causeType":"PHYSICAL_INTERACTION","vshVersion":"4.4.1","userIdToken":""}
3 Aug 13:25:40 - [info] [vsh-connection:xxxx@xxxx.com] MQTT: error: {"code":"ETIMEDOUT"}
3 Aug 13:25:40 - [info] [vsh-connection:xxxx@xxxx.com] MQTT: error: {"code":"ETIMEDOUT"}
3 Aug 13:25:40 - [info] [vsh-connection:xxxx@xxxx.com] MQTT: connection closed
3 Aug 13:26:42 - [info] [vsh-connection:xxxx@xxxx.com] MQTT: error: {"code":"ETIMEDOUT"}
3 Aug 13:26:42 - [info] [vsh-connection:xxxx@xxxx.com] MQTT: error: {"code":"ETIMEDOUT"}
3 Aug 13:26:42 - [info] [vsh-connection:xxxx@xxxx.com] MQTT: connection closed
Apart from the Node-Red update, nothing has changed in my setup.
I also note that when I dblclk on any vsh node to see the config, I see that my plan is set to "UNKNOWN" rather than "PRO" but when I look at the connection config I still see "PRO" along with a list of all my devices
When I downgrade back to Node-Red V3.1.11 then everything is working again.
Thanks for any advice
To Reproduce
Deploy VSH virtual device node in Node-Red V4.0.2
Expected behavior
It should work the same as with previous Node-Red versions.
Virtual-Smart-Home Version
4.1.2
Node-RED Version
4.0.2
Node.js Version
20.15.1
Plan
PRO
Thing-ID
vsht-1d38eb10-dc54-4296-95c5-f7780f16e39a