Closed jmorris644 closed 3 years ago
Try this with your Pi's IP address. Sometimes containers are in host mode, therefore the internal name does not work. I can't remember if that's the case here.
The internal name actually works and it connects. But node-red throws a bypassable config error when deploying.
As a temporary fix I commented out the validation code in blynk-ws-client.html for the path field.
Hi Joe, could you provide me the exact string which is not validated? These are some valid strings:
ws://www.example.it/aaaat
ws://www.example.it
ws://example/aaaat
ws://example
wss://example.it:3000/aaaat
wss://example:3000/aaaat
wss://example:3000
ws://192.168.1.1:3000/aaaaa
ws://192.168.1.1/aaaaa
ws://192.168.1.1
best regards
ws://blynk_server:8080/websockets
ok, the problem is the underscore character that doesn't validate the url. i'll fix this in next release
:)
fixed in 1.0.4 version
When setting up the connection within Docker I need to use the container name instead of a URL or ip address. When I use the conatiner name and I deploy node-red it throws a warning that the blynk node is not properly configured. Continuing deployment ignores the error and the connection works.
It would be great if the error is not thrown at all.