Multiple Same Capability on Register Device Node


these are the device types I see. I’ve tried turning it into a switch or TH sensor.
have a single capability pressure sensor. Tried turning on permissions inside (11) and out (all4) still invisible.

@SuiKa

Notice that you don´t include the 2 lines e.g.

"capability": "barometric-pressure",
      "permission": "0100",

in the Capability Settings although the API documentation shows them - avoids potential errors?

Also note that in nearly all cases you only use the “Device Status Reporting” permission.

@SuiKa you cannot use the (sensor) value in “Category” because the created device will not be displayed in ( put-device-state node).
(put-device-state node) does not display the sensor category. Error to be corrected.

we can use the smoke detector category then the device appears in ( put-device-state node)

1 Like

That’s a bug.
We’ve already released a new version for our plugin(v1.3.2) to fix the problem.
It’ll need some time to see the update in node-red.

Upgrade to v1.3.2 and see if the problem solved.
Sorry about the inconvenience we caused.

Can you provide some pic of the error?

The permission is not our choice, we are creating the device base on the node provided by @eerke.

We’ve already released a new version for our plugin(v1.3.2) to fix the problem.
Please upgrade to v1.3.2 and see if the problem solved.
Sorry about the inconvenience we caused.

No, this is no real error, more confusion on my part! but from the API documentation I understood that it was necessary to specify these 2 lines on capability and permission in the Settings box. I can now see that as they are specified before in the permission menu I don’t need to - much better.

Edit : On upgrading to 1.3.2 can now see sensors in the put-device-state node :ok_hand:

update v1.3.2 fixed category (sensor) issue

My interpretation of the API and the Node was that the four digit permissions was replicated in the Node but not the 2 digit permissions within the settings curly brackets and I then copied the 4 digit permissions from the API document into the Node (Once I realised it ran right to left and not left to right), so most capabilities only need a reporting permission, such as wind-speed. I did wonder about if the Set-Device-state node needed querying permissions but that made no difference to it appearing and wasn’t in place for past nodes. Haven’t updated my palette yet as not at computer and Node Red is worse than the iHost at being on a small screen. I don’t think you could create this 8 capability sensor on a HD monitor on 100% windows screen setting and can only see 9 capabilities on my 4K monitor with text size set to the smallest. Their node settings dialogue doesn’t allow scrolling even when there is part of the page out of the bottom.

1 Like

No problem. The first time I added capabilities one by one but couldn’t set it, so just copied and pasted from API and then you mended it when it didn’t work anyway, so I didn’t end up doing much extra anyway.

Thanks. Is better now.

Can you specify what node doesn’t allow scrolling?
Any pic or video to show?

I don’t think it’s an eWeLink thing. never seen a scroll bar. Put any node and double click. If you’ve still got the weather station register device node open it on equivalent of 150% on 4k monitor (I have bike Infront of monitor) on default browser zoom. Can’t access default script box without going to100% and standing next to bicycle. See:
.

a pressure only sensor that is fine on NR and iHost should be option to cast?

also why isn’t there a time stamp on UV index (of weather station) only?

the graph has data. it’s night so 0.

edit: no timestamp on your screenshot above either.

Plus only the top three capabilities appear on the Cast of the weather station (Temperature, Humidity and Illumination). Wondering if some capabilities are cast and some not? If so how do we know which is which?

  1. I can see scroll bar in my node-red, is this what you need?

  2. Barometric pressure is not supported in cast for now. We are supporting it now and release it.

  3. UV index not showing update time is a bug. We’ll fix it in next version.

yes, but I don’t have that scrollbar in Edge, Firefox or Chrome and the only extensions I have in Chrome are ICloud, Sticky Password Manager and a youtube specific thing.

Edge, Firefox and Chrome had the same extension and they all failed to show scroll bar?

Firefox I use most and Edge a fair bit because its websites can be pinned to the taskbar (for frequent sites) but I hardly use Chrome so it doesn’t have many extensions. I don’t see that scrollbar in any of the three.

It’s there on 2.4👍