I just updated to 2.3, which forced me to also update the eWeLink Cube Palette in Node Red and it doesn’t matter what device I select it has no actions.
There’s a new section in the register device node about permissions and there is a JavaScript settings bit. I thought I was messing up the code but have realised if I attempt to control any real device using the Control Device section I also see no Actions.
The Help section of the register device section hasn’t been updated to say anything about the new section and there are no example flows included with the palette to look at.
My iHost, Node Red Docker and the eWink Cube Palette are all on the newest versions. I’ve tried rebooting the iHost. Is this what everyone else is finding or is it just me?
I’ve had these on the register node for some time now (since the 1.3 update last month?) and haven’t really paid much attention to them. I only add the capability and tick the Device Control and Device Status Reporting permissions. The JSON settings attached to each I haven’t touched - why?
Because I haven’t been able to find any documentation on this anywhere and as its worked so far that’s the way I’ve left it! I did post something on this last month but no reply yet. Looking through the API documentación I find nothing.
@ward@SuiKa
Can we have some more information on this please?
When I found this didn’t work I tried changing this setting, figuring it was the new bit. I left it blank at first. I didn’t realise the Device Control Node was not working on real devices too, so I spent hours trying to code something here. I never managed to figure out what it did. The Help section on the node definitely needs updating. In particular the default state needs some more examples for all these new device abilities.
Sure. Yesterday it wouldn’t let me submit a ticket and told me try again later. I will try again later. I think it automatically attaches some logs. Is there anything else in particular you would like?
In particular the ‘node information’ I’m not clear on. I tried creating a new Device Control node in case it was just old nodes but it is the same. All Device Control nodes have a blank Actions section.
I thought you meant the iHost firmware and typed 1.3.1 as a typographic error, but it was the node-Red-contrib-eWeLink-cube, yes? I just spotted the update.
Plus the Help file for the register-device node is not changed https://share.icloud.com/photos/090vEVTYHRXq6cCmycXiLcWZg
It is like I am using an outdated NR palette but I restarted the iHost and refreshed the browser window. I also tried 2 browsers in case it was just one of them: Edge and Firefox.
I follow on from what @eerke mentions above, as a help documentation this is very basic and explains next to nothing about the newer features found when creating a virtual device.
A simple one line reference of “Ability - Supported capabilities of the device” is all I can see
OK, so you must select first each capability from the extensive list, and then in each case select what…?
Device Control
Device Status Reporting
Device Configuration
Device Query
All of these, or they need specific selections? The permissions are then granted using the binary strings like “0100” found in the API documentation? What exactly is the “Settings” (JSON) field for?
I think a better explanation is due for users, at least a simple example of how to register a virtual device using, and taking advantage of, all the parameters now available.
Particularly with no examples in the import section. I learns a lot from examples on other palettes. With their need for a unique UUID I understand why there are no register-device examples, but I have spent much time guessing the JavaScript baseline settings wording, so now I just use empty {} and turn it on/off or wait for a sensor to activate thereby populating that setting. With all these extra capabilities I would like a list of the associated words like Powerstate etc. Is Fan speed {“fan speed”: {“speed”: “5”}}? I don’t know what units it is in: ms-1, KMPH, MPH, RPM, String etc.
We didn’t updated much on the description of the node.
We just add some simple description about our new key, like settings and permission.
What’s really tell you how to set the settings and permission is in open api v2 documentation which shows in this link:
We did received your ticket.
But nothing in it except the word: “FAO SuiKa file they requested in forum”.
Did you failed to upload the log file?
Maybe try send it to me via message or google drive?
Too big a file for the DM. Suspect the Google drive is full but I think I can create a OneDrive link. I never use that. Think I just need to move it from downloads to documents next time I am on my big computer and it’ll automatically appear on one drive.
All devices whether real or virtual have no actions.
I have quite a few flows and some update MQTT so they will be quite often operating.
I restarted the entire iHost, which means restarting the Node Red. Do you think I should restart the docker image separately too? I checked it was updated. The only changes I made to it is that it is password protected and context storage is to a non-volatile disk.
Next time I am on a big screen I will recreate it using a simple real device (basic R2) and send the new log.
Incidentally, my old flows are working (atleast with sensors, not sure about effectors). For instance if the front door is opened the Zigbee door/window sensor tells the iHost which notifies me by sending a message through Pushover (a Push notification with a Node Red Palette). The Cast dashboard also turns on devices but I don’t think that requires Node Red.
Also, before you added the battery icon to the Cast dashboard I created a flow that alerted me to all low batteries so it would have run when any Zigbee battery device ran. That is probably creating a lot of the log. I should disable that flow now battery status appears in Cast. That is a really helpful addition by the way.
The log is blank. I looked at the log for File Browser, Tailscale, Homebridge and the logs for all of the are blank. Here is nothing in the watch bar and I have not done anything to the time frame. It has just vanished. I can do things in Node Red port 1880 though.
