# Node-RED control-device node throw an error
**URL:** https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019
**Category:** eWeLink CUBE
**Created:** [September 21, 2023, 8:16pm UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019 "2023-09-21T20:16:13Z")
**Posts on this page:** 20
**Page:** 3
### Author:  [@SuiKa](https://forum.ewelink.cc/u/SuiKa)
#### Post date: [October 10, 2023, 7:59am UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/50 "2023-10-10T07:59:22Z")
Your payload to control the device is apparently wrong.
Can you show me what device you used in control-device node?
You can findout what payload to use in help.
---
### Author:  [@aerograf](https://forum.ewelink.cc/u/aerograf)
#### Post date: [October 10, 2023, 8:06am UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/51 "2023-10-10T08:06:10Z")
I take control data from SNZB-02D
```auto
msg.payload : array[1]
array[1]
0: object
serial_number: "84ba20fffed477c7"
name: null
manufacturer: "SONOFF"
model: "SNZB-02D"
firmware_version: "1.0.9"
display_category: "temperatureAndHumiditySensor"
capabilities: array[7]
protocol: "zigbee"
app_name: null
state: object
battery: object
temperature: object
temperature: 24.1
updated_at: 1696922866729
thermostat-mode-detect: object
humidity: object
rssi: object
tags: null
online: true
```
---
### Author:  [@SuiKa](https://forum.ewelink.cc/u/SuiKa)
#### Post date: [October 10, 2023, 9:00am UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/53 "2023-10-10T09:00:36Z")
For SNZB-02D, it’s a temp and hum sensor. It cannot be switch on or off.
You mean you want to update the real temp and hum data to a virtual device in iHost?
---
### Author:  [@aerograf](https://forum.ewelink.cc/u/aerograf)
#### Post date: [October 10, 2023, 9:20am UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/54 "2023-10-10T09:20:08Z")
Got it. My mistake…
Thanks for the help!
I will wait for updates and expanded functionality.
---
### Author:  [@aerograf](https://forum.ewelink.cc/u/aerograf)
#### Post date: [December 1, 2023, 4:07pm UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/55 "2023-12-01T16:07:20Z")
Hello.
I noticed that after updating iHost to 1.11.0, a warning began to pop up:
“control-device: Failed. Please check Node configuration.”
There are no device errors.
---
### Author:  [@Teki](https://forum.ewelink.cc/u/Teki)
#### Post date: [December 6, 2023, 6:27am UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/56 "2023-12-06T06:27:37Z")
hi, after rebooting, iHost IP may change, please check your node-red settings
---
### Author:  [@aerograf](https://forum.ewelink.cc/u/aerograf)
#### Post date: [December 7, 2023, 1:01pm UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/57 "2023-12-07T13:01:22Z")
Hello.
I have a fixed IP.
This is a problem specifically in node. The description of the error is not displayed anywhere, and I can’t find where it occurs…
---
### Author:  [@songal](https://forum.ewelink.cc/u/songal)
#### Post date: [December 8, 2023, 1:50am UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/58 "2023-12-08T01:50:55Z")
Hello, can you provide your node-red log and iHost syslogs, they can be submitted through the [help center](https://help.ewelink.cc/).
---
### Author:  [@aerograf](https://forum.ewelink.cc/u/aerograf)
#### Post date: [December 8, 2023, 1:20pm UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/59 "2023-12-08T13:20:30Z")
Hello.
For some reason it gives an error when sending.
I’m posting it here.
[b9d1cf57-f121-414a-82c7-dcd9f8dd75b3.rar](https://forum.ewelink.cc/uploads/short-url/1QiWvH8GTNCT6zfNoBMwpY0PLOa.rar) (1,5 МБ)
---
### Author:  [@aerograf](https://forum.ewelink.cc/u/aerograf)
#### Post date: [December 29, 2023, 1:11pm UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/60 "2023-12-29T13:11:19Z")
Hello.
Seems to have caught the problem.
It is connected with virtual devices.
eWeLink CUBE Version - 1.13.0
Node-Red - 3.1.3
node-red-contrib-ewelink-cube - 1.1.0
---
### Author:  [@SuiKa](https://forum.ewelink.cc/u/SuiKa)
#### Post date: [January 2, 2024, 7:51am UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/61 "2024-01-02T07:51:02Z")
May you provide the log of node-red-contrib-ewelink-cube?
We’ll look into it.
---
### Author:  [@aerograf](https://forum.ewelink.cc/u/aerograf)
#### Post date: [January 2, 2024, 4:11pm UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/62 "2024-01-02T16:11:02Z")
> [@SuiKa](#):
>
> May you provide the log of node-red-contrib-ewelink-cube?
> We’ll look into it.
Hello.
Unfortunately I can not. Due to the fact that Node-Red stopped working stably after the update, I now have Node-Red running on my external server. But everything is connected with iHost.
Above I posted one of the latest Node-Red logs. There are the same errors. It was just easier to figure out the type of error here. Error 110006 also began to appear frequently…
I’ll try to make an error log…
---
### Author:  [@aerograf](https://forum.ewelink.cc/u/aerograf)
#### Post date: [January 2, 2024, 6:39pm UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/63 "2024-01-02T18:39:20Z")
> [@SuiKa](#):
>
> May you provide the log of node-red-contrib-ewelink-cube?
> We’ll look into it.
Here is a log that contains errors…
[192.168.4.4-20240102-190351.rar](https://forum.ewelink.cc/uploads/short-url/jvYOJkXOzByrgCNiaFRQAfCY3N5.rar) (58,8 КБ)
---
### Author:  [@aerograf](https://forum.ewelink.cc/u/aerograf)
#### Post date: [January 5, 2024, 11:04am UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/64 "2024-01-05T11:04:12Z")
I think I understand what the problem is.
After updating Node-Red to 3.1.3, an old problem with multi-channel devices appeared. Error 110006 after accessing one or more channels. If all channels are ON/OFF, then there is no error…
---
### Author:  [@ociepa.ekotox](https://forum.ewelink.cc/u/ociepa.ekotox)
#### Post date: [January 5, 2024, 2:40pm UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/65 "2024-01-05T14:40:50Z")
Hello.
I added a virtual device to nspanel pro. now I want to remove them from the nspanel pro screen but I don’t have this option.
I deleted the device in node-Red but it is still visible in nspanel pro.
---
### Author:  [@aerograf](https://forum.ewelink.cc/u/aerograf)
#### Post date: [January 5, 2024, 2:50pm UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/66 "2024-01-05T14:50:22Z")
> [@aerograf](#):
>
> I think I understand what the problem is.
> After updating Node-Red to 3.1.3, an old problem with multi-channel devices appeared. Error 110006 after accessing one or more channels. If all channels are ON/OFF, then there is no error…
```auto
4 Jan 13:32:00 - [info] [control-device:ВКЛ] MULTI DATA : {"1":"keep","2":"on","3":"keep","4":"keep"}
4 Jan 13:32:00 - [info] [control-device:ВКЛ] reverse result --> {"1":"on","2":"on","3":"on","4":"on"}
4 Jan 13:32:00 - [info] [control-device:ВКЛ] DEVICE CONTROL DATA : {"id":"968e9d23d7928789","deviceId":"a4c138e5d8a62148","params":{"toggle":{"1":{"toggleState":"on"},"2":{"toggleState":"on"},"3":{"toggleState":"on"},"4":{"toggleState":"on"}}}}
4 Jan 13:32:00 - [info] [control-device:ВКЛ] commonAxiosRequest data :{"id":"968e9d23d7928789","deviceId":"a4c138e5d8a62148","params":"{\"toggle\":{\"1\":{\"toggleState\":\"on\"},\"2\":{\"toggleState\":\"on\"},\"3\":{\"toggleState\":\"on\"},\"4\":{\"toggleState\":\"on\"}}}"}
4 Jan 13:32:03 - [info] [control-device:ВКЛ] res>>>>>>>>>>>>>>>>>>>{"error":110006,"data":{}}
```
```auto
4 Jan 12:24:08 - [error] [put-device-state:Внешняя температура SRV] Error: read ECONNRESET
4 Jan 12:24:08 - [error] [put-device-state:Внешняя температура SRV] Error: read ECONNRESET
```
---
### Author:  [@guilhermemorara](https://forum.ewelink.cc/u/guilhermemorara)
#### Post date: [January 6, 2024, 3:16pm UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/67 "2024-01-06T15:16:18Z")
Problem does not occur on recent versions
---
### Author:  [@songal](https://forum.ewelink.cc/u/songal)
#### Post date: [January 8, 2024, 3:03am UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/68 "2024-01-08T03:03:14Z")
Hello, I actually tested and found that there is no control device failure issue,
Or you can download the system log on the settings page and submit it via Feedback to the eWeLink team for troubleshooting. 🤔
---
### Author:  [@aerograf](https://forum.ewelink.cc/u/aerograf)
#### Post date: [January 8, 2024, 7:43am UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/69 "2024-01-08T07:43:00Z")
Hello.
I reinstalled Node-Red. Some errors have gone away, but 110006 with multi-channel devices remains.
I’ll take a log today and send it.
---
### Author:  [@aerograf](https://forum.ewelink.cc/u/aerograf)
#### Post date: [January 8, 2024, 9:18am UTC](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019/70 "2024-01-08T09:18:28Z")
Like many people, my feedback form is not working.
I’m posting the log here. Error 110006 exists…
[192.168.4.4-20240108-104520.rar](https://forum.ewelink.cc/uploads/short-url/ek6akHoKHuxwDM9c5ASv4dbx0He.rar) (39,3 КБ)
[Previous page](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019.md?page=2)
[Next page](https://forum.ewelink.cc/t/node-red-control-device-node-throw-an-error/22019.md?page=4)