BLYNK
BLYNK.IO       📲 GETTING STARTED       📗 DOCS       ❓HELP CENTER       👉 SKETCH BUILDER

Blynk IoT (new version) with Node-Red

Hello to Everyone,
I have implemented a project with the following components (and it is working):

  1. PLC S7-1200 (node-red-contrib-s7 3.0.0-beta3)
  2. Blynk websocket (node-red-contrib-blynk-ws 1.0.5)
  3. Blynk 0.1

In this days i am trying to migrate the Blynk 0.1 for the new version Blynk IoT (web and ios app) but i cant achieve the connection with the new website.
I will like to know if someone has the right parameters in order to get this connection.
I have attached a picture of my configuration, i hope someone can help me.

Hi @felixcalderon unfortunatly, Node-Red doesn’t work with the new version of Blynk, because websockets haven’t been implemented (yet).

There is a discussion about this in the posts preceding this one from @gab.lau (the person who created and maintains node-red-contrib-blynk-ws

However, if you just want to write data out to the Blynk server/app, as shown in your screenshot, then there is a workaround using the API…

In this flow, data from four different sources is coming in (on msg.payload) and needs to be written to four different virtual pins (V12 - V15).
The V12 - V15 nodes simply set msg.pin to V12, V13, V14 or V15, like this:

image

msg.token is then set to the Blynk token for the device in the next node, like this:

image

The three variables of msg.payload, msg.pin and msg.token are then used to make an HTTPS GET to the Blynk server to update the values to the virtual pins, like this:

The URL field looks like this:

https://fra1.blynk.cloud/external/api/update?token={{{token}}}&pin={{{pin}}}&value={{{payload}}}

Note that the fra1.blynk.cloud part may need to be changed, depending on where you are in the world. You can find your server by going to the new Blynk app, clicking on the “head and shoulders” icon in the top left, then clicking “About”.
The third line of data will show you which Blynk cloud server your project is on.

The Debug node (set to “Complete message object” will show the API call and the returned result, which should be “statusCode: 200”. You could add some error checking to ensure that the correct status code is returned each time then you could do that.

I’ve been using this process to send data to the Blynk server every 5 seconds since the start of Beta testing and it works fine.

Pete.

@PeteKnight I’ll try to add WebSockets support soon.

2 Likes

@PeteKnight @felixcalderon I deployed the web socket to the fra1.blynk.cloud. We have multiple changes here. First of all, now we support only secured web sockets. The full URL looks like this:

wss://fra1.blynk.cloud/hardwarews

For now, I added just 1 test to make sure it works. So it should. Please let me know if it doesn’t.

In general, blynk.cloud host could be used too, however in that case redirect should be implemented in the node-red-blynk-ws plugin. I’m don’t think it was done there initially.

1 Like

Hi @Dmitriy I just tried this and it is returning values from a virtual pin when I write data to it from the API, but it’s also disconnecting and re-connecting from websockets every few seconds with a message that says Websocket RangeError: Invalid WebSocket frame: invalid opcode 0

This is the Node-Red console output. Where it says Client logged it means that data has been successfully been received on the virtual pin and I can view this data in the Node-Red editor.

5 Jun 19:35:34 - [info] Starting flows
5 Jun 19:35:34 - [info] [blynk-ws-client:Blynk_2_TestDevice1] LOG PINS []
5 Jun 19:35:34 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Start secure connection: wss://fra1.blynk.cloud/hardwarews
5 Jun 19:35:34 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Register input node - type: write pin: 12
5 Jun 19:35:34 - [info] Started flows
5 Jun 19:35:34 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Client logged
5 Jun 19:35:49 - [error] [blynk-ws-client:Blynk_2_TestDevice1] Websocket RangeError: Invalid WebSocket frame: invalid opcode 0
5 Jun 19:35:49 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Client Error
5 Jun 19:35:49 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Reconnect in 5 seconds...
5 Jun 19:35:49 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Websocket closed: wss://fra1.blynk.cloud/hardwarews
5 Jun 19:35:49 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Reconnect in 5 seconds...
5 Jun 19:35:54 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Start secure connection: wss://fra1.blynk.cloud/hardwarews
5 Jun 19:35:54 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Client logged
5 Jun 19:36:09 - [error] [blynk-ws-client:Blynk_2_TestDevice1] Websocket RangeError: Invalid WebSocket frame: invalid opcode 0
5 Jun 19:36:09 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Client Error
5 Jun 19:36:09 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Reconnect in 5 seconds...
5 Jun 19:36:09 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Websocket closed: wss://fra1.blynk.cloud/hardwarews
5 Jun 19:36:09 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Reconnect in 5 seconds...
5 Jun 19:36:14 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Start secure connection: wss://fra1.blynk.cloud/hardwarews
5 Jun 19:36:14 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Client logged
5 Jun 19:36:29 - [error] [blynk-ws-client:Blynk_2_TestDevice1] Websocket RangeError: Invalid WebSocket frame: invalid opcode 0
5 Jun 19:36:29 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Client Error
5 Jun 19:36:29 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Reconnect in 5 seconds...
5 Jun 19:36:29 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Websocket closed: wss://fra1.blynk.cloud/hardwarews
5 Jun 19:36:29 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Reconnect in 5 seconds...
5 Jun 19:36:34 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Start secure connection: wss://fra1.blynk.cloud/hardwarews
5 Jun 19:36:34 - [info] [blynk-ws-client:Blynk_2_TestDevice1] Client logged
5 Jun 19:36:42 - [info] Stopping flows

I’m not sure if this is an issue with the way that @gab.lau’s Node-Red plugin is working in the background, or differences between the websockets protocol in Blynk 2 versus Blynk 1.

Pete.

1 Like

@PeteKnight thanks. I know what the problem is. I’ll fix.

2 Likes

@PeteKnight please try one more time. Deployed the fix.

1 Like

@Dmitriy - Okay, I’m not getting the disconnections anymore, but I’m not seeing the data for the virtual pin that I’m watching. Instead, it seems to be showing all data that is being written to any virtual pin, along with a warning, like this…

5 Jun 21:19:35 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|12|2.56"
5 Jun 21:19:35 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|14|12.46"
5 Jun 21:19:35 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|13|0.0"
5 Jun 21:19:36 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|15|50"
5 Jun 21:19:43 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|13|0.0"
5 Jun 21:19:43 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|12|2.52"
5 Jun 21:19:43 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|14|12.46"
5 Jun 21:19:44 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|15|50"
5 Jun 21:19:51 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|14|12.46"
5 Jun 21:19:51 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|12|2.5"
5 Jun 21:19:51 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|13|0.0"
5 Jun 21:19:59 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|13|0.0"
5 Jun 21:19:59 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|12|2.47"
5 Jun 21:19:59 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|14|12.46"
5 Jun 21:20:07 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|12|2.47"
5 Jun 21:20:07 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|14|12.46"
5 Jun 21:20:07 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|13|0.0"
5 Jun 21:20:15 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|12|2.44"
5 Jun 21:20:15 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|13|0.0"
5 Jun 21:20:15 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|14|12.46"
5 Jun 21:20:23 - [warn] [blynk-ws-client:Blynk_2_TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|12|2.41"

My Node-Red flow running on another machine is writing values to 4 virtual pins (12, 13, 14 & 15) via the API, as described above in post#2

My Node-Red test flow is running on a second machine and monitoring only virtual pin 12.

The Node-Red console above is showing the data values for all four virtual pins, along with CMD data.

Pete.

1 Like

Do you have some log of what commands are send to the server?

Do you send command from the node-red to the server or from the server to node-red?

This looks like something with the ws-client, as my own client works as expected. Probably he sends command that are not supported anymore.

Hi @Dmitriy, I don’t know how to see the commands that are sent I’m afraid, probably a question for @gab.lau

I guess I could try wiresharking the data, but I’m going to be away from home today, so I might try that tomorrow.

Pete.

1 Like

Hi @Dmitry, I figured-out how to get Node-Red to give me more info…

7 Jun 18:16:35 - [info] [blynk-ws-client:TestDevice1] Start secure connection: wss://fra1.blynk.cloud/hardwarews
7 Jun 18:16:35 - [info] [blynk-ws-client:TestDevice1] Register input node - type: write pin: 12
7 Jun 18:16:35 - [info] Started flows
7 Jun 18:16:35 - [info] [blynk-ws-client:TestDevice1] login -> ***************************V0Y5m
7 Jun 18:16:35 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: LOGIN, Id: 1, len: 32, data: "***************************V0Y5m"
7 Jun 18:16:35 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: RSP, Id: 1, responseCode: OK
7 Jun 18:16:35 - [info] [blynk-ws-client:TestDevice1] Client logged
7 Jun 18:16:35 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: INTERNAL, Id: 2, len: 85, data: "ver|0.6.1|h-beat|15|buff-in|32767|dev|node-red|con|Blynk-ws|fw|1.0.5|build|2021-03-17"
7 Jun 18:16:36 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 111, len: 30327, data: "|12|13.63"
7 Jun 18:16:36 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|12|13.63"
7 Jun 18:16:36 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 2, responseCode: ILLEGAL_COMMAND
7 Jun 18:16:36 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 111, len: 30327, data: "|13|0.1"
7 Jun 18:16:36 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|13|0.1"
7 Jun 18:16:36 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 2, responseCode: ILLEGAL_COMMAND
7 Jun 18:16:36 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 111, len: 30327, data: "|14|12.53"
7 Jun 18:16:36 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|14|12.53"
7 Jun 18:16:36 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 2, responseCode: ILLEGAL_COMMAND
7 Jun 18:16:37 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 111, len: 30327, data: "|15|54"
7 Jun 18:16:37 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|15|54"
7 Jun 18:16:37 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 2, responseCode: ILLEGAL_COMMAND
7 Jun 18:16:44 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 111, len: 30327, data: "|12|13.63"
7 Jun 18:16:44 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|12|13.63"
7 Jun 18:16:44 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 2, responseCode: ILLEGAL_COMMAND
7 Jun 18:16:44 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 111, len: 30327, data: "|13|0.1"
7 Jun 18:16:44 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|13|0.1"
7 Jun 18:16:44 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 2, responseCode: ILLEGAL_COMMAND
7 Jun 18:16:44 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 111, len: 30327, data: "|14|12.53"
7 Jun 18:16:44 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|14|12.53"
7 Jun 18:16:44 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 2, responseCode: ILLEGAL_COMMAND
7 Jun 18:16:45 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 111, len: 30327, data: "|15|54"
7 Jun 18:16:45 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|15|54"
7 Jun 18:16:45 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 2, responseCode: ILLEGAL_COMMAND
7 Jun 18:16:52 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 111, len: 30327, data: "|13|0.0"
7 Jun 18:16:52 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|13|0.0"
7 Jun 18:16:52 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 2, responseCode: ILLEGAL_COMMAND
7 Jun 18:16:52 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 111, len: 30327, data: "|12|13.63"
7 Jun 18:16:52 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|12|13.63"
7 Jun 18:16:52 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 2, responseCode: ILLEGAL_COMMAND
7 Jun 18:16:52 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 111, len: 30327, data: "|14|12.54"
7 Jun 18:16:52 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|14|12.54"
7 Jun 18:16:52 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 2, responseCode: ILLEGAL_COMMAND
7 Jun 18:16:53 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 111, len: 30327, data: "|15|54"
7 Jun 18:16:53 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 111, len. 30327, data. "|15|54"
7 Jun 18:16:53 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 2, responseCode: ILLEGAL_COMMAND

Does this help?

Pete.

@PeteKnight a bit.

I see that log (and node-red?) “receives” hardware message "RECV ← Cmd: HW, Id: 111, len: 30327, data: “|12|13.63”

And that’s confusing. First of all, id=111. It’s returned only in HTTP API, but node-red using WebSockets. So how that’s possible?
Next, data body seems missing the first 2 bytes. It should be “vw|12|13.63”. But we didn’t change the hardware protocol. So it seems more like an node-red parser.
len: 30327 is actually missing “vw” part.
In case of the WebSockets len part should be taken from the WebSocket message, not blynk message.

So looks likes the initial version was compatible with the node-red plugin. And second version require to change this code node-red-contrib-blynk-ws/blynk-util.js at master · gablau/node-red-contrib-blynk-ws · GitHub.

Length is no longer needed with websockets, as websocket frame has a length field and blynk header should be 3 bytes in that case, not 5 like it was before.

@Dmitriy, the data is being written to the Blynk server using the HTTP API, on a different machine (as I described in post #2).
The data log from my last post is connected to a Blynk Write Event node in Node-Red, which is in effect the same as a BLYNK_WRITE(vPin) function in C++
The Blynk Write Event node is subscribed only to virtual pin V12, but is being triggered by data being written to virtual pins 12, 13, 14 and 15. This wasn’t happening with your initial websockets code for Blynk 2/0. With that code I was only seeing the V12 data and not the string of data preceding it, or the data for the other tree virtual pins.

Pete.

@Dmitriy I’ve been doing a bit more testing and this time I added a slider widget to the web dashboard, connected to the D6 datastream for the same project.

Now, when I move that slider, I see the values in Node-Red with a different hardware ID…

Cmd. HW, Id. 3169, len. 30327, data. "|6|840"
Cmd. HW, Id. 3187, len. 30327, data. "|6|560"

This is all against the node that should be subscribed to pin V12

So, I think there’s maybe a problem with your websockets integration?

Pete.

1 Like

@Dmitriy Okay, tested a few other things…

  1. Turned-off the Node-Red flow on the other machine that was pushing data to pins V12-15 vioa the API

  2. Added a node to the websockets test mavhine that would inject a value of either 100 or 500 to pin V6 (which is what I have a slider attached to in the web dashboard.

  3. Started the node-red websockets flow.

Without any incoming data from the API on the other machine, the websockets connection drops and re-connects every 5 seconds or so…

8 Jun 12:31:15 - [info] [blynk-ws-client:TestDevice1] LOG PINS ["12"]
8 Jun 12:31:15 - [info] [blynk-ws-client:TestDevice1] Start secure connection: wss://fra1.blynk.cloud/hardwarews
8 Jun 12:31:15 - [info] [blynk-ws-client:TestDevice1] Register input node - type: write pin: 12
8 Jun 12:31:15 - [info] Started flows
8 Jun 12:31:15 - [info] [blynk-ws-client:TestDevice1] login -> ***************************V0Y5m
8 Jun 12:31:15 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: LOGIN, Id: 1, len: 32, data: "***************************V0Y5m"
8 Jun 12:31:15 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: RSP, Id: 1, responseCode: OK
8 Jun 12:31:15 - [info] [blynk-ws-client:TestDevice1] Client logged
8 Jun 12:31:15 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: INTERNAL, Id: 2, len: 85, data: "ver|0.6.1|h-beat|15|buff-in|32767|dev|node-red|con|Blynk-ws|fw|1.0.5|build|2021-03-17"
8 Jun 12:31:24 - [info] [blynk-ws-client:TestDevice1] Websocket closed: wss://fra1.blynk.cloud/hardwarews
8 Jun 12:31:24 - [info] [blynk-ws-client:TestDevice1] Reconnect in 5 seconds...
8 Jun 12:31:29 - [info] [blynk-ws-client:TestDevice1] Start secure connection: wss://fra1.blynk.cloud/hardwarews
8 Jun 12:31:29 - [info] [blynk-ws-client:TestDevice1] login -> ***************************V0Y5m
8 Jun 12:31:29 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: LOGIN, Id: 1, len: 32, data: "***************************V0Y5m"
8 Jun 12:31:29 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: RSP, Id: 1, responseCode: OK
8 Jun 12:31:29 - [info] [blynk-ws-client:TestDevice1] Client logged
8 Jun 12:31:29 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: INTERNAL, Id: 4, len: 85, data: "ver|0.6.1|h-beat|15|buff-in|32767|dev|node-red|con|Blynk-ws|fw|1.0.5|build|2021-03-17"

Injecting a text or numeric value of 100 or 500 to pin V6 using the websockets Write node had no effect on the slider on the web dashboard, but there were no disconnections as long as I injected something at least every few seconds…

8 Jun 12:31:34 - [info] [blynk-ws-client:TestDevice1] virtualWrite: -> ["vw","6","100"]
8 Jun 12:31:34 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: HW, Id: 5, len: 8, data: "vw|6|100"
8 Jun 12:31:37 - [info] [blynk-ws-client:TestDevice1] virtualWrite: -> ["vw","6","500"]
8 Jun 12:31:37 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: HW, Id: 6, len: 8, data: "vw|6|500"
8 Jun 12:31:42 - [info] [blynk-ws-client:TestDevice1] virtualWrite: -> ["vw","6","100"]
8 Jun 12:31:42 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: HW, Id: 7, len: 8, data: "vw|6|100"
8 Jun 12:31:44 - [info] [blynk-ws-client:TestDevice1] virtualWrite: -> ["vw","6","500"]
8 Jun 12:31:44 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: HW, Id: 8, len: 8, data: "vw|6|500"
8 Jun 12:31:47 - [info] [blynk-ws-client:TestDevice1] virtualWrite: -> ["vw","6","100"]
8 Jun 12:31:47 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: HW, Id: 9, len: 8, data: "vw|6|100"
8 Jun 12:31:50 - [info] [blynk-ws-client:TestDevice1] virtualWrite: -> ["vw","6","500"]
8 Jun 12:31:50 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: HW, Id: 10, len: 8, data: "vw|6|500"

Moving the V6 slider on the web portal produced this:

8 Jun 12:32:53 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 4531, len: 30327, data: "|6|530"
8 Jun 12:32:53 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 4531, len. 30327, data. "|6|530"
8 Jun 12:32:53 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 18, responseCode: ILLEGAL_COMMAND
8 Jun 12:32:55 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 4532, len: 30327, data: "|6|530"
8 Jun 12:32:55 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 4532, len. 30327, data. "|6|530"
8 Jun 12:32:55 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 18, responseCode: ILLEGAL_COMMAND
8 Jun 12:32:57 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 4533, len: 30327, data: "|6|280"
8 Jun 12:32:57 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 4533, len. 30327, data. "|6|280"
8 Jun 12:32:57 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 18, responseCode: ILLEGAL_COMMAND
8 Jun 12:32:59 - [info] [blynk-ws-client:TestDevice1] RECV <- Cmd: HW, Id: 4535, len: 30327, data: "|6|800"
8 Jun 12:32:59 - [warn] [blynk-ws-client:TestDevice1]  Cmd. HW, Id. 4535, len. 30327, data. "|6|800"
8 Jun 12:32:59 - [info] [blynk-ws-client:TestDevice1] SEND -> Cmd: RSP, Id: 18, responseCode: ILLEGAL_COMMAND

Hopefully this helps??

Pete.

Hi @Dmitriy any more thoughts on the websockets integration for Node-Red after reviewing the additional information I’ve posted above?

Do you think it’s an issue with the Node-Red plugin, or is there still work needed at your end?

Pete.

1 Like

I think the red-node plugin should be reworked. Unfortunately, I can’t dig into it right now, so we’ll have to wait until someone will have time to fix it.

2 Likes

@gab.lau - for info…

Pete.