By the way, can you successfully control multi-channel devices from iHost’s home page device list?
Yes. There are no problems with iHost.
1 Like
Hello.
I repeat the question. how to remove virtual device from nspanel pro screen. deleting in node-red doesn’t help. the device is still visible in nspanel pro.
I followed your explanation for the temperature sensor with your same parameters, and I got this error:
I made some tests and found out the “error” was that the rssi value cannot be 65 (I changed it to -65 and it worked). Somewhere there must be restrictions of the values the capabilities can have, it would be nice to be able to see them in the manual for using the node-red nodes
I continued to implement your example, and when I try to push the values of an actual t/h device into the virtual one, the push node still keeps the red triangle as wrong configured:
so I cannot deploy it
1 Like
Hi, I had the same issue as you, needing to delete devices. Since they haven’t implemented it, I created my own:
the “process” node has this:
msg.url = ‘http://192.168.0.155:8081’ + msg.command;
if (msg.params != undefined)
{
msg.url = msg.url +‘:’+msg.params;
}
return msg;
the inject node has:
, in the “msg.command” line that will be appended to the ip address, the last part is the serial number of the device to erase.
Sometimes it still reports a device when you call for the device list, even after deleting it, in that case the reply to trying to delete it would be something like “that serial number does not belong to any device”
The last and VERY IMPORTANT thing is that you need to get a Token for your nodes (different from the one got by the ewelink cube nodes) using another http request node:
and the token you get (after injecting to that node when the iHost is giving tokens) has to be put manually in the http request node you use for deleting, after the word "Bearer "
I hope this helps you, I know it is complicated, but we are manually creating the functionality that they haven’t programmed yet
Of course, wherever you see 192.168.0.155, that is my IP, you need to replace it by yours 
sorry, it was not clear since it was after the “token” part:
you select in “Method” the option “- set by msg.method -” since in the inject node you already have a “msg.method = DELETE”, but you could also select DELETE here, I just use the same SEND node for all my tests.
and, as you can se in the picture, you need to add two headers (both string):
“Content-Type” “application/json”
“Authorization” "Bearer " plus the content of your Token, which you have to manually copy here. Surely there are other ways to do it, but it would require to save the token on disk for recovering it after booting. That is what the eWelink nodes do but I assume they save the token encripted (or they should)
so far I have this flow for testing and learning which commands I can send (thinking on whatever the ewelink cube nodes cannot do), that is why I tried to reutilize nodes and just change the inject, but it is not the best way to implement it, later I hope to have global variables keeping some values that would be used for constructing the inject messages depending on the command to send…
thanks for the help.
managed to remove devices from nspanel pro.
1 Like
Hello.
Any plans to update node-red-contrib-ewelink-cube and resolve bug 110006?
They will add NSPanel Pro, SPM, Pow, etc. devices?
Or should we look for other solutions to the problem?
Please reproduce the problem and post your system log and device model here so we can pinpoint what’s wrong.
Can you reproduce the issue again and submit the latest node-red logs and the iHost system logs? Your last node-red log submission only shows that the device reply control has failed, and we can’t confirm what the problem is.
Hello.
Here is the iHost magazine.
I can’t download the Node-Red magazine yet…
1706102941213.tar.zip (3,2 МБ)
1 Like
I still need your multi channel device’s device id or serial number to find the correct error.
Hello.
Sorry for not mentioning it right away.
- 4 channel zigbee, connected directly to iHost - a4c138e5d8a62148
- 2 channel dualr3, ID in iHost - 81ab4f8f-07a2-433d-9b30-7c3bf875ced9, ID in eWeLink - 10018387ce
Error 110006 means control fail.
We can reproduce it sometime. But most of the time is normal.
We are looking for the problem now.
Does this error occur every time the device is controlled, or is it just partially successful and partially unsuccessful, like mine?
Sometimes it goes through without error. But sometimes, if there is an error, it can turn all channels on or off.
I had to do an additional check of the channel and turn it on if it was turned off by an error, or turn it off.
It’s inconvenient, but for now it works like this…
Both of devices shows the same behavior? Control ends with partially successful and partially unsuccessful?
The log is not up to date.
The best way is reproduce the problem, download it right away and post it here.
Yes. I don’t just have these multi-channel devices. But these work on critical nodes.
Sonoff TX ULTIMATE T5-3C-86 and others behave the same way…