adorkable / node-red-contrib-ui-led Goto Github PK

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. ...
2. ...

Expected behavior
A clear and concise description of what you expected to happen vs what actually happens.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

I suspect this is because most of my NR modules are in /usr/lib? (Because I used apt to install it).
Here is the error I get.

{ Error: Cannot find module '../../../../../../../../home/craig/.node-red/node_modules/node-red-dashboard'
    at Function.Module._resolveFilename (module.js:548:15)
    at Function.Module._load (module.js:475:25)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at Object.requireModule [as require] (/usr/lib/node_modules/node-red/red/runtime/nodes/registry/loader.js:69:16)
    at new LEDNode (/home/craig/.node-red/node_modules/node-red-contrib-ui-led/led.js:35:26)
    at createNode (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/Flow.js:305:18)
    at Flow.start (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/Flow.js:89:35)
    at start (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/index.js:328:29)
    at /usr/lib/node_modules/node-red/red/runtime/nodes/flows/index.js:164:25 code: 'MODULE_NOT_FOUND' }

I modified nodered.service to be able to run Node Red as root. After I restarted Node Red I had to reinstall Dashboard, LED node and then re-imported the flows. Now The Led not showing.

Although getting away from a "simple" LED, the NEOPIXELs are popular.

For people wanting to simulate a Neopixel LED, adding that to the LED would/may/could be nice.

The input would be the same as the NeoPixel LEDs so as to maintain a standard so any code could easily be ported to the real ones.

Describe the bug
I could not insert the color in the color selection

Screenshots

Desktop (please complete the following information):

• OS: windows 10
• Browser chrome

Without wanting to make it too complicated:

4 (5 actually?) levels of "brightness" for the LED.
I'll pick 4 as I am trying to keep it practical and a base of 2 (to maybe help with byte optimisation)
8 would be too many.
2 would be a bit too few.
4 seems like a good choice.

Levels would be (something like):
5 - FULL
4 - NOT QUITE FULL
3 - MEDIUM
2 - NOT SO DULL
1 - DULL
0 - OFF

Names are nominal. Just to explain for people to get the idea.

I know LEDs are usually ON/OFF indications.
But sometimes it may be nice to have different brightnesses. (?)

Either for dark screens/modes or to act as a progress indicator with how bright the LED is.

I know this could be done with colours. But sticking to their names: (eg)
red, green, blue, lime, yellow, (etc)
you send a message with the brightness of the LED.
FULL/MAXIMUM is the default.

Only a suggestion.

Should be allowed to toggle between realistic and cartoonish LED visuals

Hello.
I tried to put a few leds on a tab but I'm having problems.
It seems if you put a few leds and position them and then if you try to rearrange after you deploy thre is a good chance that the whole layout is randomly changed.
Could this have anything to do with the fact that you can't change the name of the led in a flow (also causes big problems identifying the leds)

We allow customizing beyond true and !true and allow any number of customized value -> color combinations

So what is the difference between ui-led and ui-led-fork?

Describe the bug
Changing the color of the led and redeploying will not change the color of the led when that state is sent to the LED. You must change the state in order to get the new color.

i.e. have two buttons - one sends true the other false. Set false to RED deploy and press the false button. The LED shows RED.

To Reproduce
Steps to reproduce the behavior:

1. create wo buttons - one sends true the other false.
2. attach them to the LED node
3. Deploy
4. press the 'false' button - led turns RED
5. edit led node and change false to show the color BLUE
6. deploy
7. press the 'false' button - led still shows RED
8. press the 'Tue' button - led turns GREEN
9. press the 'false' button - led turns BLUE

Expected behavior
after the changing the color and deploying, sending the same signal that was last sent should change the color (I.e. in step 7, the color should now be BLUE)

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: macOS 10.13.6
• Browser: Safari
• Version: [e.g. 22]
  Node-red: v0.20.5
  node.js; v10.15.3
  ui_led: v0.2.3

Additional context

LED / Label not appearing on dashboard

In NR editor no problem to define, but nothing is showing up on dashboard. Space where it should be gets filled up with other following dashboard elements. All other dashboard elements working fine.

Raspi Linux 5.4.72-v7+ armv7l

Versions

• node-red-contrib-ui-led: 0.3.3
• node-red: 1.0.6
• node-red-dashboard: 2.24.1

In previous versions doing well

Describe the bug
If you install the ui-led node before installing the dashboard, then install the dashboard, using the led node in a flow will show an error in the log and the led will not appear in the dashboard

To Reproduce
Steps to reproduce the behavior:

1. ...install the ui-led node
2. ...instll node-red-dashboard
3. ...use the led node in a flow

Expected behavior
the led should appear and no error should happen

Screenshots
here is what hows up in the log

4 Oct 06:32:00 - [info] Starting flows
While constructing LEDNode widget: Error: Cannot find module 'node-red-dashboard'
    at Object.requireModule [as require] (/usr/lib/node_modules/node-red/node_modules/@node-red/registry/lib/util.js:48:19)
    at new LEDNode (/home/pi/.node-red/node_modules/node-red-contrib-ui-led/led.js:13:26)
    at Object.createNode (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/flows/util.js:483:31)
    at Flow.start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/flows/Flow.js:189:48)
    at start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/flows/index.js:329:33)
    at /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/flows/index.js:196:21
    at processTicksAndRejections (internal/process/task_queues.js:94:5) {
  code: 'MODULE_NOT_FOUND'
}
TypeError: Cannot read property 'padEnd' of undefined
    at Flow.start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/flows/Flow.js:237:62)
    at start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/flows/index.js:329:33)
    at /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/flows/index.js:196:21
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
4 Oct 06:32:00 - [info] Started flows

Versions

• node-red-contrib-ui-led: 0.3.3
• node-red: 1.0.3 - 1.1.3
• node-red-dashboard: 2.23.4

Platform

• OS: [e.g. iOS] rpi - buster 10
• Browser [e.g. chrome, safari] safari
• Version [e.g. 22] 0.13.04

Additional context
shutting node-red down and restarting it fixes the issue.

To all for in Editor debugging

https://nodered.org/docs/creating-nodes/status

Great idea suggested by @Nokomis449 in #3

I imagine it would be a single pixel size or optionally a different width and height pixel size (have to make sure this actually looks good with our current LED).

My instinct is to keep the text at the default text size but should it grow to fill the height?

22 Sep 09:33:59 - [info] Node-RED version: v1.1.3
22 Sep 09:33:59 - [info] Node.js version: v12.18.3
22 Sep 09:33:59 - [info] Windows_NT 10.0.18363 x64 LE

if i inject a msg.glow = false the glow is still there!?

Should allow to specify rectangular shape, potentially ratio of width to height

The size of the LED is too powerful compared to the label. An adjustment of the size would be desirable.

Describe the bug
node red version = 0.20.8

To Reproduce

1. install led-ui from "Manage palette"
2. add the led to a flow, set the label

Expected behavior
after deploying I get this error "TypeError: Cannot read property 'length' of undefined" and no led appears on the dashboard.

I'm installing today the node in a new docker container, but when executing my installation script there was some dependencies problems, due to the newly updated node-red-dashboard 5 days ago.

I guess in the meantime I'll keep using the 2.23.0 version, but an update on the node will be appreciated.

Thanks, have a very good day :)

hi, there is an option to select JSON input for the msg.payload, but it seems to only test the whole string. So the LED would only colorize when the complete string is matched.
Is it possible to select which JSON element & value to test?
For example: an input would look like: { "Light1":0,"Light2":1,"Light3":0,"Light4":1 }
And then have the led node to test:
if "Light1" == "1" then color = "green"
if "Light1" == "0" then color = "grey"
That way you can connect many ui-leds to a single input and select on what element to light up.

see: https://discourse.nodered.org/t/simple-json-input-string-to-leds-on-dash/20003

THANKS!

I can't get the node to show anything other than grey.
I have configured a simple flow with two inject nodes injecting boolean true and false into the led node and nothing happens when I do the inject. Here is the flow:

[{"id":"6d4c5778.575b6","type":"inject","z":"514a90a5.c7bae8","name":"","topic":"","payload":"false","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":174,"y":517,"wires":[["a5be5c13.23cc"]]},{"id":"c4a9d112.426b18","type":"inject","z":"514a90a5.c7bae8","name":"","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":174,"y":557,"wires":[["a5be5c13.23cc"]]},{"id":"a5be5c13.23cc","type":"ui_led","z":"514a90a5.c7bae8","group":"536f7750.317da8","order":3,"label":"LED","name":"","x":404.5,"y":540,"wires":[]},{"id":"536f7750.317da8","type":"ui_group","z":"","name":"Default","tab":"cefe4a16.8f56d8","disp":false,"width":"12","collapse":false},{"id":"cefe4a16.8f56d8","type":"ui_tab","z":"","name":"Home","icon":"dashboard"}]

Running on Ubuntu 18.10 the node red log shows nothing unusual on startup. Any suggestions will be gratefully received.

Welcome to Node-RED
===================
2 Feb 15:51:31 - [info] Node-RED version: v0.19.5
2 Feb 15:51:31 - [info] Node.js  version: v10.15.1
2 Feb 15:51:31 - [info] Linux 4.18.0-13-generic x64 LE
2 Feb 15:51:32 - [info] Loading palette nodes
2 Feb 15:51:33 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
2 Feb 15:51:33 - [warn] rpi-gpio : Cannot find Pi RPi.GPIO python library
2 Feb 15:51:34 - [info] Dashboard version 2.13.2 started at /ui
2 Feb 15:51:34 - [info] Settings file  : /home/me/.node-red/settings.js
2 Feb 15:51:34 - [info] HTTP Static    : /home/me/.node-red/static
2 Feb 15:51:34 - [info] Context store  : 'default' [module=memory]
2 Feb 15:51:34 - [info] User directory : /home/me/.node-red
2 Feb 15:51:34 - [warn] Projects disabled : editorTheme.projects.enabled=false
2 Feb 15:51:34 - [info] Flows file     : /home/me/.node-red/flows_tigger.json
2 Feb 15:51:34 - [info] Server now running at http://127.0.0.1:1880/
2 Feb 15:51:34 - [info] Starting flows
2 Feb 15:51:34 - [info] Started flows

When change the position on the layout no changes on the UI.

Just as something which has become of interest to me playing with JavaScript.

Could the colours be set by the message properties like:
msg.truecolour
msg.falsecolour

Then if the true value is received, the truecolour is displayed.

This contrib doesn't seem to work on the latest version of nodejs - is that true? Seems to only work on v10.16.3

When you open the Node-Red HTML page with the UI on it, the LED(s) are grey as if there is no data even though the Node is getting message data regularly. It is not until the next message is sent to the Node that the LED will illuminate.
To Reproduce*
Steps to reproduce the behaviour:

1. setup a flow which sends a toggling data message to the node-red-contrib-ui-led Node, changing payload between different values (mine were 'Good', 'Slow' and 'Down' every 60 seconds). Deploy.
2. Open the HTML page with the UI after approx 60 seconds all the LEDs will display the correct state, navigate to another page (without this LED UI), then navigate back to the UI page with the LED UI. The LED will be grey until the next message arrives (up to 60 seconds).

I would expect the LED to show the colour from the last message received by node before the HTML page is opened, not wait for next msg

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: W10 and Android 9
• Browser: Chrome (on all OS) and IE 11
• Version: latest

Additional context
NB this seperate to another problem reported separately where the LED stays grey even though it is getting messages which can display grey on some computers and properly on others.

On all my devices, glow on the left side of the led is covered by the invisible border: maybe glow is too large or led is not centered in the box? I've this artifact whatever is the size of the widget.
Normally I use a widget size of 1x1 for the led with no label since the led is near a button and I've used yellow color instead of green for the 'true' value.

Nodered 0.19.4 running on Raspbian
browser: chrome on Windows and Android

A way to specify the label text's alignment as left, right, or center

Suggested by @Just-another-pleb in #18

My use case has messages updating the LED status very infrequently -- like once an hour or so. When I update my flows and re-deploy, I lose the state information on the LEDs -- but other UI elements like graphs don't forget their states.

Also, when I switch to a different page and then back to the one with the LED UI elements, they have lost their state.

Perhaps this is a case where the global context needs to be used to save states?

It would be good to maintain state in both cases. I understand that restarting Node-Red would be a loss of state.

I appreciate the LED.

The only thing I would like to see is a way to put it back to the "I have not received anything yet" state.

I am using it as an indicator and though maybe a FULL DEPLOY would be better.....
It would be nice if something could be injected to reset to to the blank state/mode.

Hi, I tried to add a led to my dashboard but it isn't added to the dashboard:

https://www.screencast.com/t/2nkMfFNoTj

[ { "id": "a82ff38b.4c666", "type": "tab", "label": "Sensors", "disabled": false, "info": "" }, { "id": "3c453b6.16f1e44", "type": "ui_led", "z": "a82ff38b.4c666", "group": "fe5704ed.b94c58", "order": 0, "label": "Connected", "colorForValue": [ { "color": "red", "value": "false", "valueType": "bool" }, { "color": "green", "value": "true", "valueType": "bool" } ], "name": "Connected", "x": 668, "y": 123, "wires": [] }, { "id": "66d4aae9.ae760c", "type": "ui_switch", "z": "a82ff38b.4c666", "name": "simple switch", "label": "switch", "tooltip": "", "group": "fe5704ed.b94c58", "order": 3, "width": 0, "height": 0, "passthru": true, "decouple": "false", "topic": "", "style": "", "onvalue": "true", "onvalueType": "bool", "onicon": "", "oncolor": "", "offvalue": "false", "offvalueType": "bool", "officon": "", "offcolor": "", "x": 460, "y": 140, "wires": [ [ "3c453b6.16f1e44" ] ] }, { "id": "fe5704ed.b94c58", "type": "ui_group", "z": "", "name": "UI LED", "tab": "1de68bdd.807364", "order": 1, "disp": true, "width": "6", "collapse": false }, { "id": "1de68bdd.807364", "type": "ui_tab", "z": "", "name": "Test", "icon": "dashboard", "order": 2, "disabled": false, "hidden": false } ]

Any idea on what I'm doing wrong?

UI dashboard with more than 1 tab and UI Leds in all the tabs
When you switch between one tab and the other, the status of the LEDs is always off

The leds turn gray and do not change state after switching the UI tabs. Refreshing the whole UI turns them back on (it seems that the state is stored - it's a display issue).

Will the name LED/led confuse folks and situations where flows signal actual leds?

Users potentially want to be able to store the LED's state in other contexts, such as global, and have that state retrained further than a single session.

There is the argument to keep a UI element dumb and only represent outside state, however in practice it isn't always worth the work to build a set of flows that robustly manage state in this way and a simple solution would get folks there sooner.

So we can have it both ways whatever this ends up being should be optional.

With node-red V1.0.2 the LED nodes are not displayed on the dashboard.
This is from your example:

There should be a LED, right?

Also using an own flow with these nodes, they are not displayed on the dashboard

When updating nodes I got this message after a node was removed:

[email protected] requires a peer of [email protected] but none is installed. You must install peer dependencies yourself.

Thing is the dashboard installed is 2.19.2

That is greater than 2.14.x

Is this a problem?

This is still not 100% proven to be a bug with the LED node, but when I inject a message which tells the LED to turn a certain colour and it doesn't.......

This is happening on a few flows, now and then.
A signal which is set in the LED node is sent and it simply doesn't change colour.

Out of curiosity I made a large flow with a lot of LEDs on it all different colours.
The colours were names (green, navy, cyan, etc) rather than RGB values.
So I could easily pick a colour for a LED if/when I wanted on.

It is one inject node with the inject at start set to 5 seconds.
Some times (on boot) the screen is all grey LEDs.
Now, with further testing even manually pressing the INJECT node, the LEDs don't change colour from GREY.

NR 0.20.5
LED 0.2.3
FF and Chrome tests fail.
Chrome pretty well virgin: no addons.

Flow available in/on node-red library.
Link:[https://flows.nodered.org/flow/7a2337014a09018eb7f14c9a93237997

It would be nice to work out what is going on.

A way to specify the label text's alignment as on the left or right side of the LED.

Suggested by @Just-another-pleb in #18

There is the option for the "name" of the LED.
This means (for instance) if you make it 3 wide...... It would be nice to control where/how the text is shown.
"Left justified", "Centered", or "Right format".
Maybe not having the LED so close to the edge? (See attached picture. Note red line.)
And maybe even the option to put the text AFTER the LED, rather than before.

trying to run the basic example, I get those messages:
23/11/2019 à 14:20:54msg : error
"TypeError: Cannot read property 'length' of undefined"
23/11/2019 à 14:20:54node: 2aae8fef.55ce8
msg : error
"TypeError: Cannot read property 'push' of undefined"

Nothing is left undefined in the configuration.
I'm running raspian(v10 buster) on a raspberry 4, MQTT and node-red(v13.1.0)

No luck getting it to actually show up in the UI. Even pasting the example and, as a result, having it create new subflows, still doesn't have it showing up in the UI. Currently on 0.17.5 for node-red

Ok, this is more a request than a bug.

When you create the LED on the dashboard, there is no means to edit the "size" that it takes up.

Explination:
Say I have a group which is 6 squares wide.
I have another node that is 3 squares wide in that group.
I want to put the LED on the same "line" (horizontal) as the a fore mentioned node.
Alas it can't be done. There is no way to make the LED 3 squares wide, so the two can fit in the 6 wide group and not the LED is an entire line by itself.

Could it be added at some time to allow this?

Thanks.

Describe the bug
Even when the LED are displayed correctly on another computer (same OS and Browser), when you open on a new browser the LED stay grey even though there is valid data being received. This does not occur all the time, it appears to be random although once not working it stays not working despite closing navigating away and back to page and then starts working again. (but not always)
I have had same page open on multiple tabs and in multiple browsers and on multiple PCs. one tab (that has been open a while and is working) is good, the rest have grey LEDs . see picture
Now one LED has a 'Slow" (yellow) sent to it every 6 seconds and the regular service ("NAS" which is "Good" (green) sent every 10 seconds. This appears to always work (flashes between green and yellow) reliability, but a seperate LED that gets the same NAS derived message stays grey usually (not green).
Another LED I added a UI button that sends "Down" (Red) whilst the LED Node is also getting regular 60 second messages from its source (Ping to a server, reports "Good"). It starts grey on navigating page and stays grey even after 60 seconds (ensures at least on message sent). I press the button and LED turns Red then within 60 seconds it changes to green! Starts to work properly.
Occasional a LED will start to work!

To Reproduce
I have pasted part of my flow below but this problem does appear whole flow wide....I tried to setup a sandpit to replicate problem (with several LEDs Nodes) and problem went away, few days later it reappeared.

Expected behaviour
LED should display colour from message sent to it

Screenshots
If applicable, add screenshots to help explain your problem
See picture attached, Chrome and Edge showing different data (NB Edge could have been anther Chrome tab but will still display faulty
.

Desktop (please complete the following information):
OS: W10 (also seen on Android 9 and 8)
Browser: Chrome (on droid and W10), Edge, IE
Versions: Node-Red, W10 and Browsers all at latest version

Additional context
THis is seperate from issue #25 where LEDs are grey when HTML page is opened until first message rx by node. #25 always happens, this issue sometimes happen and but once work appears to keep working until a ne page is opened (in another Tab, browser or Computer) but at other times it behaves normally.

Partial Flow

[{"id":"1e97aa16.e7a2f6","type":"ping","z":"12f44cb5.337193","name":"Weather Station ping","host":"10.0.0.171","timer":"60","x":140,"y":700,"wires":[["9f4c83d2.45f0d","a0df4b97.af7eb8"]]},{"id":"1efbff35.ac9cb1","type":"ping","z":"12f44cb5.337193","name":"Pool ping","host":"10.0.0.235","timer":"60","x":180,"y":660,"wires":[["9f4c83d2.45f0d","72fd4af2.61d874"]]},{"id":"2429bf0d.3aa6d","type":"ping","z":"12f44cb5.337193","name":"ShedCam ping","host":"10.0.0.100","timer":"60","x":160,"y":740,"wires":[["9f4c83d2.45f0d","bf23c9c0.d69fe8"]]},{"id":"54816b44.798704","type":"ping","z":"12f44cb5.337193","name":"WebBox ping","host":"10.0.0.122","timer":"60","x":170,"y":820,"wires":[["9f4c83d2.45f0d","b1857f1d.e1168"]]},{"id":"e536138c.3ed4f","type":"ping","z":"12f44cb5.337193","name":"Heating ping","host":"10.0.0.204","timer":"60","x":170,"y":780,"wires":[["9f4c83d2.45f0d","c2757a08.fb93e8"]]},{"id":"9f4c83d2.45f0d","type":"change","z":"12f44cb5.337193","name":"AddTopic","rules":[{"t":"change","p":"topic","pt":"msg","from":"10.0.0.","fromt":"str","to":"Ping","tot":"str"},{"t":"change","p":"payload","pt":"msg","from":"false","fromt":"bool","to":"9999","tot":"num"}],"action":"","property":"","from":"","to":"","reg":false,"x":420,"y":500,"wires":[["21a8d4ed.0fa2bc"]]},{"id":"21a8d4ed.0fa2bc","type":"rbe","z":"12f44cb5.337193","name":"Change>0.5 mSec","func":"deadband","gap":"0.5","start":"","inout":"out","property":"payload","x":640,"y":500,"wires":[["6730fc64.9e7824"]]},{"id":"6d773d88.1a3994","type":"ping","z":"12f44cb5.337193","name":"Vege Patch ping","host":"10.0.0.242","timer":"10","x":160,"y":620,"wires":[["9f4c83d2.45f0d","8816e835.675368"]]},{"id":"2ed0af50.2b067","type":"ui_led","z":"12f44cb5.337193","group":"996b46f6.ffc338","order":4,"label":"VegePatch","colorForValue":[{"color":"red","value":"Down","valueType":"str"},{"color":"green","value":"Good","valueType":"str"},{"color":"Yellow","value":"Slow","valueType":"str"}],"name":"VegePatch LED","x":660,"y":620,"wires":[]},{"id":"8816e835.675368","type":"change","z":"12f44cb5.337193","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"(payload = false)? "Down" : (payload >2.0) ? "Slow" : "Good"","tot":"jsonata"}],"action":"","property":"","from":"","to":"","reg":false,"x":440,"y":620,"wires":[["2ed0af50.2b067","62b5b4b3.dda95c"]]},{"id":"c163e6b1.9913f8","type":"ui_led","z":"12f44cb5.337193","group":"996b46f6.ffc338","order":3,"label":"Pool","colorForValue":[{"color":"red","value":"Down","valueType":"str"},{"color":"green","value":"Good","valueType":"str"},{"color":"Yellow","value":"Slow","valueType":"str"}],"name":"Pool LED","x":640,"y":660,"wires":[]},{"id":"72fd4af2.61d874","type":"change","z":"12f44cb5.337193","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"(payload = false)? "Down" : (payload >2.0) ? "Slow" : "Good"","tot":"jsonata"}],"action":"","property":"","from":"","to":"","reg":false,"x":440,"y":660,"wires":[["c163e6b1.9913f8"]]},{"id":"5c337833.b83eb8","type":"ui_led","z":"12f44cb5.337193","group":"996b46f6.ffc338","order":8,"label":"Weather","colorForValue":[{"color":"red","value":"Down","valueType":"str"},{"color":"green","value":"Good","valueType":"str"},{"color":"Yellow","value":"Slow","valueType":"str"}],"name":"Weather LED","x":660,"y":700,"wires":[]},{"id":"a0df4b97.af7eb8","type":"change","z":"12f44cb5.337193","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"(payload = false)? "Down" : (payload >2.0) ? "Slow" : "Good"","tot":"jsonata"}],"action":"","property":"","from":"","to":"","reg":false,"x":440,"y":700,"wires":[["5c337833.b83eb8"]]},{"id":"ffb64c06.b44da","type":"ui_led","z":"12f44cb5.337193","group":"996b46f6.ffc338","order":7,"label":"ShedCam","colorForValue":[{"color":"red","value":"Down","valueType":"str"},{"color":"green","value":"Good","valueType":"str"},{"color":"Yellow","value":"Slow","valueType":"str"}],"name":"ShedCamLED","x":660,"y":740,"wires":[]},{"id":"bf23c9c0.d69fe8","type":"change","z":"12f44cb5.337193","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"(payload = false)? "Down" : (payload >2.0) ? "Slow" : "Good"","tot":"jsonata"}],"action":"","property":"","from":"","to":"","reg":false,"x":440,"y":740,"wires":[["ffb64c06.b44da"]]},{"id":"7909d473.bfd9cc","type":"ui_led","z":"12f44cb5.337193","group":"996b46f6.ffc338","order":6,"label":"Heating","colorForValue":[{"color":"red","value":"Down","valueType":"str"},{"color":"green","value":"Good","valueType":"str"},{"color":"Yellow","value":"Slow","valueType":"str"}],"name":"Heating LED","x":650,"y":780,"wires":[]},{"id":"c2757a08.fb93e8","type":"change","z":"12f44cb5.337193","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"(payload = false)? "Down" : (payload >2.0) ? "Slow" : "Good"","tot":"jsonata"}],"action":"","property":"","from":"","to":"","reg":false,"x":440,"y":780,"wires":[["7909d473.bfd9cc"]]},{"id":"fd39548c.8e1598","type":"ui_led","z":"12f44cb5.337193","group":"996b46f6.ffc338","order":5,"label":"Sunny Webbox","colorForValue":[{"color":"red","value":"Down","valueType":"str"},{"color":"green","value":"Good","valueType":"str"},{"color":"Yellow","value":"Slow","valueType":"str"}],"name":"WebboxLED","x":650,"y":820,"wires":[]},{"id":"b1857f1d.e1168","type":"change","z":"12f44cb5.337193","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"(payload = false)? "Down" : (payload >2.0) ? "Slow" : "Good"","tot":"jsonata"}],"action":"","property":"","from":"","to":"","reg":false,"x":440,"y":820,"wires":[["fd39548c.8e1598"]]},{"id":"f6a9be43.87815","type":"ui_led","z":"12f44cb5.337193","group":"996b46f6.ffc338","order":2,"label":"NAS","colorForValue":[{"color":"red","value":"Down","valueType":"str"},{"color":"green","value":"Good","valueType":"str"},{"color":"yellow","value":"Slow","valueType":"str"}],"name":"NAS LED","x":640,"y":540,"wires":[]},{"id":"38f49c90.d77554","type":"change","z":"12f44cb5.337193","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"(payload = false)? "Down" : (payload >2.0) ? "Slow" : "Good"","tot":"jsonata"}],"action":"","property":"","from":"","to":"","reg":false,"x":440,"y":540,"wires":[["f6a9be43.87815","1ce82bd0.f41234","ec2bc2e7.8f555"]]},{"id":"975e0569.1d0b38","type":"ping","z":"12f44cb5.337193","name":"Router ping","host":"10.0.0.001","timer":"60","x":150,"y":580,"wires":[["4c1a3167.6b6a1"]]},{"id":"681f8993.420f88","type":"ui_led","z":"12f44cb5.337193","group":"996b46f6.ffc338","order":1,"label":"Router","colorForValue":[{"color":"red","value":"Down","valueType":"str"},{"color":"green","value":"Good","valueType":"str"},{"color":"yellow","value":"Slow","valueType":"str"}],"name":"Router LED","x":650,"y":580,"wires":[]},{"id":"4c1a3167.6b6a1","type":"change","z":"12f44cb5.337193","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"(payload = false)? "Down" : (payload >2.0) ? "Slow" : "Good"","tot":"jsonata"}],"action":"","property":"","from":"","to":"","reg":false,"x":440,"y":580,"wires":[["681f8993.420f88"]]},{"id":"a2b6682d.639468","type":"ui_button","z":"12f44cb5.337193","name":"set to Down","group":"996b46f6.ffc338","order":9,"width":0,"height":0,"passthru":false,"label":"button","tooltip":"just press me","color":"","bgcolor":"","icon":"","payload":"Down","payloadType":"str","topic":"","x":450,"y":880,"wires":[["fd39548c.8e1598"]]},{"id":"62b5b4b3.dda95c","type":"ui_led","z":"12f44cb5.337193","group":"c2749915.2e3758","order":4,"label":"VegePatch","colorForValue":[{"color":"red","value":"Down","valueType":"str"},{"color":"green","value":"Good","valueType":"str"},{"color":"Yellow","value":"Slow","valueType":"str"}],"name":"VegePatch LED","x":900,"y":620,"wires":[]},{"id":"c6481e37.87eeb","type":"inject","z":"12f44cb5.337193","name":"","topic":"","payload":"Slow","payloadType":"str","repeat":"6","crontab":"","once":false,"onceDelay":0.1,"x":870,"y":520,"wires":[["ec2bc2e7.8f555","1ce82bd0.f41234"]]},{"id":"1ce82bd0.f41234","type":"ui_led","z":"12f44cb5.337193","group":"996b46f6.ffc338","order":4,"label":"{{msg.payload}}","colorForValue":[{"color":"red","value":"Down","valueType":"str"},{"color":"green","value":"Good","valueType":"str"},{"color":"yellow","value":"Slow","valueType":"str"}],"name":"","x":1070,"y":560,"wires":[]},{"id":"ec2bc2e7.8f555","type":"debug","z":"12f44cb5.337193","name":"","active":false,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","x":1090,"y":480,"wires":[]},{"id":"996b46f6.ffc338","type":"ui_group","z":"","name":"Status","tab":"4fcb4fe9.d6391","order":2,"disp":true,"width":"6","collapse":false},{"id":"c2749915.2e3758","type":"ui_group","z":"","name":"Manual Control","tab":"15398257.058b8e","order":1,"disp":true,"width":"6","collapse":false},{"id":"4fcb4fe9.d6391","type":"ui_tab","z":"","name":"Network","icon":"usb","order":4},{"id":"15398257.058b8e","type":"ui_tab","z":"","name":"Irrigation","icon":"fa-tint","order":2}]

Describe the bug
On some browser/OS combinations, the UI displays controls for vertical scrolling unnecessarily. Scrolling range is limited to one click of the controls. This is always displayed and there appears to be no parameter that can be set to make the UI element higher so it does not need to scroll.

Been seen with W10/Chrome
Does not occur on W10/Edge or W10/IE or Droid 9/Chrome

Screenshots
Attached

Desktop (please complete the following information):

• OS: W10
• Browser Chrome
• Version Latest (all updates applied