Node-RED control-device node throw an error

[guilhermemorara]

I don´t know why but the problem was “corrected” when I created a second token and mapped all nodes that control devices to this new token…
ASAP I will update the node-red container and test further.

[SuiKa]

Hi, aerograf.
You share one device with another eWeLink account and log in with that account, the device will be able to sync to and control through iHost.

The new version of node-red-contrib-ewelink-cube are already released in Sep 28, sorry for the delay of information.

[SuiKa]

Hi, guilhermemorara.
We released the new version of node-red-contrib-ewelink-cube in Sep 28.
Please see if any similar problem occurs.
We are looking forward to your feedback.

[aerograf]

Hello.
You have improved a lot in node-red-contrib-ewelink-cube.
Thanks for your work.
I would also like to see it in the list of devices next to iHost and NSPanel Pro.
I would also like to see a more detailed description of register-device. How can you transfer temperature and humidity data to a virtual device, etc.

And will it be possible to receive data from POWR3 and other similar devices?

Will there be SPM-Main support?

Thanks in advance for your answer!

[SuiKa]

Hi, aerograf.

1. I would also like to see it in the list of devices next to iHost and NSPanel Pro.
   I don’t understand.

2. I would also like to see a more detailed description of register-device. How can you transfer temperature and humidity data to a virtual device, etc.
   When you register the device with the register-device node, select the temperature and humidity capability and set the initial temperature and humidity status for the device.
   After the device is successfully registered, you can receive the device status data transmitted by the previous node through the put-device-state node, and use this status data to update the status of the virtual device you registered in ihost.

3. And will it be possible to receive data from POWR3 and other similar devices?
   You can use the event-state node to monitor the electric status of powerR3. When the status changes, the put-device-state node synchronies the monitored electric status to the registered ihost virtual device.

[SuiKa]

The need of SPM-Main is noted.
We will see if we can support it in recent version.

[aerograf]

Hello.

1. I mean to use the functionality of NSPanel Pro, as access from node-red to iHost is now implemented.

2. I tried it, it doesn’t work. Can you give an example?

3. I don’t see data from POWR3 in node-red. So, can you give an example?

Thanks in advance for your answer!

[aerograf]

@SuiKa

The need of SPM-Main is noted.
We will see if we can support it in recent version.

I’m really looking forward to it and thinking. I’m not alone.
Thanks for the answer!

[songal]

An example of the state of a real device being synchronized to a virtual device display:

After running, if you operate the real device, its switch and brightness data will be automatically synchronized to the virtual device for display:

By defining a virtual device and associating it with a real device, you can create a device with multiple capabilities in iHost, such as simultaneous switch, brightness, color temperature, temperature, humidity, and fan capabilities

[SuiKa]

Hi, aerograf.

For sync your temp and hum sensor data to a virtual device.

1. Use a register-device node to register a virtual device.
   
   
   
   Here are some initial state
   
   
2. Use a event-state to monitor a real temp and hum sensor data.
   
   
3. Use a function node to receive and transfer the data.
   
   
4. Use a put-device-state node to recevie the data and sync to iHost.
   
   
5. Then you can see your real data are synced to your virtual device.
   
   

Here are the whole flow.

As for a POWR3 synchronization, we are cuurently not support a register ability for POWR3.
So you can’t register a virtual POWR3 device to iHost.
But you can still receive a POWR3 data from a event-state node, like here

[aerograf]

Hello.
Thank you so much for the examples! I will study further.
We are looking forward to adding new features.

[aerograf]

But I couldn’t get data from POWR3…

[SuiKa]

Hi, aerograf.

I just checked the device.
This POWR3 currently not support LAN electric data upload.
So you won’t be seeing any data upload to iHost, either.
Sorry about the inconvenice.
We’ll see if we can support it in future version.

If you really need the feature.
Here are the product that support it: POWR316, POWR316D, POWR320D

[aerograf]

Hello.
We will wait for updates and the addition of device support.
Thanks for support!

[aerograf]

Continuing the topic of errors.
Here’s another one I found.
Actuator basicrfr3.
In order not to search, I am attaching an example…

error.json (8,6 КБ)

[SuiKa]

Hi, aerograf.

The code suggests it’s a control failure.
Can you provide your json data that sended to put-device-state node?
So I can pinpoint the problem.
Add a debug node in here to get it.

[aerograf]

I hope I understood correctly…

[aerograf]

As a result, the script is processed, but this error confuses…

[SuiKa]

Looks a little messy…
Keep one control-device node and disconnect others.
And keep debug 81 and one debug node after control-device node.
So I can get a clearer view.

[aerograf]