Hallo
der RAM verbrauch war bei mir knapp bei 400MB und nach dem neustart des adapters auf 50MB
evtl sollte dieses Problem behoben werden.

grüße :D

Ein Dropdown-Liste in den fx datenpunkt anlegen damit man die Effekte auswählen kann

Benefit : No data polling
Possible : Yes since latest version of WLED firmware

ToDo : rebuild complete data and state change logic

Dear Adapter develop,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

After Update to JS Controler 3.0.7 i get a warning:
wled.0 2020-04-13 09:57:17.397 warn (25893) This value will not be set in future versions. Please report this to the developer. wled.0 2020-04-13 09:57:17.397 warn (25893) State value to set is invalid for wled.0.cc50e304f753.seg.0.col.0: The state is missing the required property val! wled.0 2020-04-13 09:57:17.394 warn (25893) This value will not be set in future versions. Please report this to the developer. wled.0 2020-04-13 09:57:17.393 warn (25893) State value to set is invalid for wled.0.cc50e304f753.seg.0.ix: The state is missing the required property val!

JS Controler 3.0.7
NPM 6.14.4
NodeJS 12.16.2

[https://i.imgur.com/gMdKll3.png]

Das Spukt der log bei TypeError aus.

Brightness Value
should be between 0-100% but currently is 0-255

• When changing "Preset Cycle" (pl = 0 / -1) in web frontend the value will not be changed in ioBroker
• fx will not set to "Solid" (0). Other Effects work fine

Changing both in ioBroker works fine and will be set in WLED

Versions:

• Adapter version: v0.5.4
• JS-Controller version: v3.1.6
• Node version: v12.18.3
• Operating system: linux / docker

is this a bug or normal and just not possible?
If it is possible, what could be a reason that it doesn't work?
No problem to change other settings.

wLED löscht alle angelegten Segmente wenn man den Strom wegnimmt.
ist es möglich das der Adapter die Segmente wieder schreibt, nachdem dieser vom Strom getrennt war?

WLED supports playlists, that are quite useful.
I have not found a way to control these over the ioBroker.wled adapter.

It would be great if we could get either native support for this feature, or a possibility to transmit json to the wled device via the adapter.

starting the adapter (0.5.6) with sentry disabled, starting the instance seem to trigger sentry, followed by an error:
2021-03-26 21:21:55.289 - ESC[32minfoESC[39m: wled.0 (12313) Try to contact : "WLED-2" on IP : 10.10.10.120 2021-03-26 21:21:55.817 - ESC[32minfoESC[39m: wled.0 (12313) [Error catched and send to Sentry, thank you collaborating!] error: State attribute definition missing for + &#x26A1; Ping fix pings<span style="display:block;padding-left:25px;">Delay <input type="number" min="5" max="300" value="30" onchange="requestJson({PingDelay:parseInt(this.value)});">sec</span> 2021-03-26 21:21:55.819 - ESC[31merrorESC[39m: wled.0 (12313) Create state error = TypeError: Cannot read property 'captureException' of undefined 2021-03-26 21:21:55.819 - ESC[32minfoESC[39m: wled.0 (12313) [Error catched and send to Sentry, thank you collaborating!] error: State attribute definition missing for + &#x26A1; Reconnects 2021-03-26 21:21:55.820 - ESC[31merrorESC[39m: wled.0 (12313) Create state error = TypeError: Cannot read property 'captureException' of undefined 2021-03-26 21:21:56.142 - ESC[32minfoESC[39m: wled.0 (12313) [Error catched and send to Sentry, thank you collaborating!] error: State attribute definition missing for + PingDelay 2021-03-26 21:21:56.143 - ESC[31merrorESC[39m: wled.0 (12313) Create state error = TypeError: Cannot read property 'captureException' of undefined 2021-03-26 21:21:56.564 - ESC[32minfoESC[39m: wled.0 (12313) Device : "WLED-2" Successfully connected on IP : 10.10.10.120

JS controller version: 3.2.16, admin version: 4.2.1

Moin :-)

Der Adapter fängt ja die WLED Module ein, wenn man aber z.B. viele Geräte konfiguriert (z.B. für Freunde etc.) tauchen diese natürlich alle in der Admin-Übersicht, sowie in der Objekt-Liste auf. Hier wäre es schön die Module die nicht mehr im Einsatz sind, einfach über die Admin-Oberfläche (inkl. Löschung im Objekt-Baum) löschen zu können.

reminder : https://forum.iobroker.net/topic/29833/wled-led-streifen-ws2812b-ws2811-sk6812-apa102-bedienen/313

2020-12-25 19:40:09.073 - info: host.iobroker-deb instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
--
  | 2020-12-25 19:40:39.224 - info: host.iobroker-deb "system.adapter.wled.0" disabled
  | 2020-12-25 19:40:39.225 - info: host.iobroker-deb stopInstance system.adapter.wled.0 (force=false, process=true)
  | 2020-12-25 19:40:39.226 - info: host.iobroker-deb stopInstance system.adapter.wled.0 send kill signal
  | 2020-12-25 19:40:39.229 - info: wled.0 (16106) Got terminate signal TERMINATE_YOURSELF
  | 2020-12-25 19:40:39.236 - info: wled.0 (16106) terminating
  | 2020-12-25 19:40:39.237 - info: wled.0 (16106) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
  | 2020-12-25 19:40:39.237 - info: wled.0 (16106) cleaned everything up...
  | 2020-12-25 19:40:39.783 - info: host.iobroker-deb instance system.adapter.wled.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
  | 2020-12-25 19:41:20.861 - info: host.iobroker-deb "system.adapter.wled.0" enabled
  | 2020-12-25 19:41:20.904 - info: host.iobroker-deb instance system.adapter.wled.0 started with pid 22618
  | 2020-12-25 19:41:22.600 - info: wled.0 (22618) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
  | 2020-12-25 19:41:22.610 - info: wled.0 (22618) starting. Version 0.5.4 in /opt/iobroker/node_modules/iobroker.wled, node: v12.20.0, js-controller: 3.1.6
  | 2020-12-25 19:41:22.637 - info: wled.0 (22618) Try to contact known devices
  | 2020-12-25 19:41:22.638 - info: wled.0 (22618) Try to contact : "Wohnzimmer Schrank" on IP : 192.168.0.193
  | 2020-12-25 19:41:26.399 - info: wled.0 (22618) Device : "Wohnzimmer Schrank" Successfully connected on IP : 192.168.0.193
  | 2020-12-25 19:41:26.404 - info: wled.0 (22618) Bonjour service startet, new devices will be detected automatically :-)
  | 2020-12-25 19:41:26.405 - info: wled.0 (22618) WLED initialisation finalized, ready to do my job have fun !
  | 2020-12-25 19:42:59.247 - info: wled.0 (22618) New WLED device found wled-5d9de3 on IP 192.168.0.192
  | 2020-12-25 19:43:00.458 - info: wled.0 (22618) [Error catched and send to Sentry, thank you collaborating!] error: State attribute definition missing for + u
  | 2020-12-25 19:43:00.459 - error: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
  | 2020-12-25 19:43:00.459 - error: wled.0 (22618) unhandled promise rejection: Cannot read property 'captureException' of undefined
  | 2020-12-25 19:43:00.460 - error: wled.0 (22618) TypeError: Cannot read property 'captureException' of undefined
  | at Wled.sendSentry (/opt/iobroker/node_modules/iobroker.wled/main.js:802:37)
  | at Wled.create_state (/opt/iobroker/node_modules/iobroker.wled/main.js:698:11)
  | at Wled.readData (/opt/iobroker/node_modules/iobroker.wled/main.js:426:18)
  | at runMicrotasks ()
  | at processTicksAndRejections (internal/process/task_queues.js:97:5)
  | 2020-12-25 19:43:00.461 - info: wled.0 (22618) cleaned everything up...
  | 2020-12-25 19:43:00.477 - info: wled.0 (22618) [Error catched and send to Sentry, thank you collaborating!] error: State attribute definition missing for + t
  | 2020-12-25 19:43:00.478 - error: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
  | 2020-12-25 19:43:00.478 - error: wled.0 (22618) unhandled promise rejection: Cannot read property 'captureException' of undefined
  | 2020-12-25 19:43:00.478 - error: wled.0 (22618) TypeError: Cannot read property 'captureException' of undefined
  | at Wled.sendSentry (/opt/iobroker/node_modules/iobroker.wled/main.js:802:37)
  | at Wled.create_state (/opt/iobroker/node_modules/iobroker.wled/main.js:698:11)
  | at Wled.readData (/opt/iobroker/node_modules/iobroker.wled/main.js:426:18)
  | at runMicrotasks ()
  | at processTicksAndRejections (internal/process/task_queues.js:97:5)
  | 2020-12-25 19:43:00.479 - info: wled.0 (22618) terminating
  | 2020-12-25 19:43:00.480 - info: wled.0 (22618) Terminated (NO_ERROR): Without reason
  | 2020-12-25 19:43:00.530 - info: wled.0 (22618) [Error catched and send to Sentry, thank you collaborating!] error: State attribute definition missing for + pmt
  | 2020-12-25 19:43:01.008 - info: host.iobroker-deb instance system.adapter.wled.0 terminated with code 0 (NO_ERROR)
  | 2020-12-25 19:43:01.013 - info: host.iobroker-deb Restart adapter system.adapter.wled.0 because enabled
  | 2020-12-25 19:43:31.033 - info: host.iobroker-deb instance system.adapter.wled.0 started with pid 22878
  | 2020-12-25 19:43:32.552 - info: wled.0 (22878) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
  | 2020-12-25 19:43:32.608 - info: wled.0 (22878) starting. Version 0.5.4 in /opt/iobroker/node_modules/iobroker.wled, node: v12.20.0, js-controller: 3.1.6
  | 2020-12-25 19:43:32.646 - info: wled.0 (22878) Try to contact known devices
  | 2020-12-25 19:43:32.646 - info: wled.0 (22878) Try to contact : "Wohnzimmer Schrank" on IP : 192.168.0.193
  | 2020-12-25 19:43:35.994 - info: wled.0 (22878) Device : "Wohnzimmer Schrank" Successfully connected on IP : 192.168.0.193
  | 2020-12-25 19:43:35.994 - info: wled.0 (22878) Try to contact : "Stehlampe" on IP : 192.168.0.192
  | 2020-12-25 19:43:37.602 - info: wled.0 (22878) [Error catched and send to Sentry, thank you collaborating!] error: State attribute definition missing for + u
  | 2020-12-25 19:43:37.605 - error: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
  | 2020-12-25 19:43:37.606 - error: wled.0 (22878) unhandled promise rejection: Cannot read property 'captureException' of undefined
  | 2020-12-25 19:43:37.607 - error: wled.0 (22878) TypeError: Cannot read property 'captureException' of undefined
  | at Wled.sendSentry (/opt/iobroker/node_modules/iobroker.wled/main.js:802:37)
  | at Wled.create_state (/opt/iobroker/node_modules/iobroker.wled/main.js:698:11)
  | at Wled.readData (/opt/iobroker/node_modules/iobroker.wled/main.js:426:18)
  | at runMicrotasks ()
  | at processTicksAndRejections (internal/process/task_queues.js:97:5)
  | at async Wled.tryKnownDevices (/opt/iobroker/node_modules/iobroker.wled/main.js:638:19)
  | at async Wled.onReady (/opt/iobroker/node_modules/iobroker.wled/main.js:49:3)
  | 2020-12-25 19:43:37.609 - info: wled.0 (22878) cleaned everything up...
  | 2020-12-25 19:43:37.628 - info: wled.0 (22878) terminating
  | 2020-12-25 19:43:37.629 - info: wled.0 (22878) Terminated (NO_ERROR): Without reason
  | 2020-12-25 19:43:37.635 - info: wled.0 (22878) [Error catched and send to Sentry, thank you collaborating!] error: State attribute definition missing for + t
  | 2020-12-25 19:43:37.685 - info: wled.0 (22878) [Error catched and send to Sentry, thank you collaborating!] error: State attribute definition missing for + pmt
  | 2020-12-25 19:43:38.164 - info: host.iobroker-deb instance system.adapter.wled.0 terminated with code 0 (NO_ERROR)
  | 2020-12-25 19:43:38.165 - info: host.iobroker-deb Restart adapter system.adapter.wled.0 because enabled

To highlight an event, I use WLED to blink in another color a few times. For this, I have to create my own variables to cache the used color before I highlighted something. If there would be a data point like "last used color" or a few free template data points, I don't have to create my own variables and I could use only the data points directly at the controller. Also a data point "last used mode" would be helpful for this.

For example:
The LED Stripe is red, without any animation. If the telephone rings, the LED stripe changes his color to blue for 10 seconds and starts blinking. After 10 seconds, the LED Stripe turns back to red (or the last used color before it wents blinking blue) without blinking.

Thank you in advance.

Dear Adapter developer,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

I am using an ESP32 with WLED 0.10. After disconnecting the ESP and LED strip from power and reconnecting it I cannot turn on the LED strip via the datapoints. I have to manually log in to the ESP and power it on manually once. After that I can instantly turn on and off the strip via the data points.

Adapter Version is 0.5.1
js-controller: 3.1.4

Edit: It only happens if I use the on data point under seg.0. If I use the on data point on the top level it works fine.

Detailled log:

`

User error.

Moin,

in der Adminoberfläche werden die WLED Module ja mit der MAC-Adresse dargestellt. Hier wäre es noch schön, wenn das Device bereits einen Hostnamen zugewiesen bekommen hat (über die WLED Oberfläche), das dieser auch in der Admin bzw. vielleicht sogar in der Objekt-Liste auftaucht und dort zugewiesen wird.

Wenn das Device nachträglich geändert wird, dann sollte er diese Änderung mitnehmen :-)

Hello,
I want to turn on or off the Hue Sync for wled.
Will this be possible in a future version?

API from WLED is supporting this:
&HP= | 0 to 99 | Sets Hue polling light ID (0 is off) | 0.5.1

Thanks!

my WLEDs do have the usermod "usermod_Fix_unreachable_netservices" enabled, to keep them connected (without, the web ui stops responding after some minutes being idle). This mod does extend the json info object (as it is intended), with the little 'speciality' that this extension contains some (seemingly properly quoted) HTML.
I think the json result is valid, at least common parsers do not complain, and results do look proper; however, WLED-adapter throws warnings which look like as if the request is not properly parsed.

The json request result (/json/info):
{"ver":"0.11.1","vid":2101130,"leds":{"count":150,"rgbw":false,"wv":false,"pin":[2],"pwr":250,"maxpwr":4000,"maxseg":12,"seglock":false},"str":false,"name":"WLED-2","udpport":21324,"live":false,"lm":"","lip":"","ws":0,"fxcount":118,"palcount":56,"wifi":{"bssid":"78:8A:20:B7:0D:74","rssi":-64,"signal":72,"channel":1},"fs":{"u":49,"t":1024,"pmt":1615056140},"arch":"esp8266","core":"2_7_4_7","lwip":1,"freeheap":21048,"uptime":1883032,"u":{"&#x26A1; Ping fix pings<span style=\"display:block;padding-left:25px;\">Delay <input type=\"number\" min=\"5\" max=\"300\" value=\"30\" onchange=\"requestJson({PingDelay:parseInt(this.value)});\">sec</span>":[62762],"&#x26A1; Reconnects":[1]},"opt":127,"brand":"WLED","product":"FOSS","mac":"483fda7eae39"}

WLED adapter 0.5.6 in iobroker log:
2021-03-26 21:21:56.792 - ESC[33mwarnESC[39m: wled.0 (12313) Used invalid characters: wled.0.483fda7eae39._info.u.&#x26A1; Ping fix pings<span style="display:block;padding-left:25px;">Delay <input type="number" min="5" max="300" value="30" onchange="requestJson({PingDelay:parseInt(this.value)});">sec</span> changed to wled.0.483fda7eae39._info.u.&#x26A1_ Ping fix pings_span style=_display:block_padding-left:25px_Delay _input type=_number_ min=_5_ max=_300_ value=_30_ onchange=_requestJson({PingDelay:parseInt(this.value)})_sec_/span_ 2021-03-26 21:21:56.805 - ESC[33mwarnESC[39m: wled.0 (12313) State "wled.0.483fda7eae39._info.u.&#x26A1; Ping fix pings<span style="display:block;padding-left:25px;">Delay <input type="number" min="5" max="300" value="30" onchange="requestJson({PingDelay:parseInt(this.value)});">sec</span>" has no existing object, this might lead to an error in future versions 2021-03-26 21:21:56.806 - ESC[33mwarnESC[39m: wled.0 (12313) Used invalid characters: wled.0.483fda7eae39._info.u.&#x26A1; Reconnects changed to wled.0.483fda7eae39._info.u.&#x26A1_ Reconnects

Not sure if this is related to the fact that usermods are also using the "u:" key, though on root level; the existing "u:" is in "fs:" scope... Perhaps this could somehow be fixed in WLED adapter? Adapter version is 0.5.6, JS controller 3.2.16

Hallo Dutchmann,

leider funktionieren die aktuelleren Versionen vom WLED Adapter bei mir nicht mehr richtig.
Anscheinend bekommt der Adapter weder mit welcher Effekt / Farbschema gerade beim NodeMCU abläuft noch kann er einen Befehl senden.

Version 0.5.0 funktioniert hingegen einwandfrei sogar mit WLED Firmware 0.10.2

Fairnesshalber muss ich dazu sagen, dass ich tagsüber die WLED stromlos mache. Kann es sein, dass damit die Versionen über 0.5.0 ein Problem damit haben?

Falls du noch irgendwelche Sachen benötigst liefere ich die dir natürlich gerne. Vielen Dank :o)

wled Version 0.5.6
Admin 5.1.4
js-controller 3.3.11

Ich habe heute erstmals wled installiert und folgenden Fehler bekommen, welcher im Rahmen des Admin/js-controller Updates auch schon andere Adapter betroffen hat.

Es wundert mich nur, das hier noch kein Issue dazu eröffnet wurde - oder habe ich es übersehen? Die "Problematik" ist ja schon mit der ersten Admin 5.x.x Version aufgetreten.

`

`

DP werden bei jedem Pull neu geschrieben und nicht bei jeder Änderung.
Führt zu erhöhtem Traffic usw,

Describe the bug
All WLED Devices are not connected (red dots). Using the URL of the ESP works fine. So it is not in issue with the ESP or the LED stripe.

The log says:
`

• Adapter version: 0.5.6
• JS-Controller version: 3.2.16
• Node version: 14.16.0
• Operating system: debian stable

Edit: A restart of the RPI solved the error. I leave the issue open in case you want to have a look at what caused the error.

Hallo Raffi,
Hier ein kleines Problem mit einem State bei mir. In Aden Bildern siehst du es.

You query /json in every round trip. This costs a lot of heap (on my esp8266) which causes a forced WLAN disconnect. I have a lot of WLAN issues with my first WLED controller.

I set up a test ESP and got this DEBUG log

---DEBUG INFO---
Runtime: 25040896
Unix time: 1585766772
Free heap: 6880
Wifi state: 3
State time: 24710446
NTP last sync: 6010
Client IP: 192.168.120.48
Loops/sec: 2430
Heap too low! 6880
Forcing reconnect.
Access point disabled.
Connecting to IoT...

Connected! IP address: 192.168.120.48
Init STA interfaces
mDNS started
Disconnected!
Access point disabled.
Connecting to IoT...

Connected! IP address: 192.168.120.48
Init STA interfaces
mDNS started
...

A heap below 9k will cause a WLAN forced reconnect

    if (heap < 9000 && lastHeap < 9000) {
      DEBUG_PRINT("Heap too low! ");
      DEBUG_PRINTLN(heap);
      forceReconnect = true;
    }

To Reproduce
Try to load /json form your WLED serveral time by browser. At some point the ESP not response anymore and will disconnect itselfs from WLAN.

But you doesn't need to request the whole JSON. You can request every part using /json/state, /json/info, /json/effects and /json/palettes. State could be requested every round trip. The rest could be requeste at startup only or e.g. every 5 minutes.

I don't know if this is the root cause of my ESP being unreachable after a while. I'll disable

Volker

(22797) Create state error = ReferenceError: initialise is not defined

Zu unterschiedlichen Zeiten verliert WLED die Verbindung zum NodeCU. Ein Reset oder Neustart des Adapters hilt nicht.
Ich muss den Adapter löschen und neu installieren

`

2021-03-17 17:39:11.857 - error: wled.0 (9571) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-03-17 17:39:11.858 - error: wled.0 (9571) unhandled promise rejection: Cannot read property 'error' of undefined
2021-03-17 17:39:11.860 - error: wled.0 (9571) TypeError: Cannot read property 'error' of undefined
at Wled.onUnload (/opt/iobroker/node_modules/iobroker.wled/main.js:97:13)
at Wled.emit (events.js:314:20)
at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:8620:22)
at Object.onceWrapper (events.js:421:26)
at process.emit (events.js:314:20)
at process.exit (internal/process/per_thread.js:168:15)
at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:352:25)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
2021-03-17 17:39:11.860 - error: wled.0 (9571) Cannot read property 'error' of undefined

`

Versions:

• Adapter version: 0.5.6
• JS-Controller version: 3.2.16
• Node version: 12.21.0
• Operating system: Debian 10.2.0

Think about update stable version to 0.5.4

Version: stable=0.5.2 (35 days old) => latest=0.5.4 (30 days old)
Installs: stable=212 (37.26%), latest=201 (35.33%), total=569
Click to edit

Describe the bug
3 attributes are missing
wled.0 | 2020-07-19 19:08:59.081 | warn | (15662) State attribute definition missing for + lor
wled.0 | 2020-07-19 19:08:58.914 | warn | (15662) State attribute definition missing for + lip
wled.0 | 2020-07-19 19:08:58.906 | warn | (15662) State attribute definition missing for + lm

To Reproduce
Update yout wled to 0.10.0

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

Description
Ich schreibe mittels Blockly die aktuelle Farbe (Primary Color RGB) in einen Datenpunkt.
Ändere die primary Color RGB manuell per Blockly auf eine andere Farbe (0,0,255)
Nach einer Zeit, überschreibe ich den Datenpunkt mit Primary Color RGB erneut mit der in der Variable gespeicherten Farbe.

Seit dem letzten Update, entstehen hierbei sämtliche Fehlermeldungen im Log. Die Funktion ist jedoch nicht beeinträchtigt.

Versions:

• Adapter version: 0.5.4
• JS-Controller version: 3.1.6
• Node version: 10.22.0
• Operating system: Ubuntu 20.04 LTS

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

Hi @DutchmanNL,

seems like Aircoookie updated the API properties...

Can you implement them as well?

More Infos: Aircoookie/WLED@94c5f0d

Thank you for this gread Adapter!

Best regards,
xengosam

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

If something is not correct this is logged as 'warning' or 'info' log.

Please take the time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1301

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

relates to Aircoookie/WLED#975 (comment)

Warum kann man im iot-Adapter keinen Befehl für Alexa anlegen?

Describe wanted Enhancement !
Api error indicates new values with version 0.10.2, state attributes logic and propper values must be set

Why should we put effort in it ?
Ensure support of newest firmware

Additional context
Sentry messages :

State attribute definition missing for + ws
State attribute definition missing for + mode
State attribute definition missing for + mi

feature requst, das man über den Adapter UDP / API Sequenzen schicken kann.

Sowas in der Art, muss aktuell über umwege MQTT gemacht werden.
SM=0&SS=0&SV=2&S=15&S2=299&GP=7&SP=30&RV=0&SB=255&A=255&W=255&R2=0&G2=0&B2=0&W2=&FX=0&T=1

grüße

please update for support v0.11.0 "Mirai"

controlling this version is possible now, but it doeas not read the states. especially on/off, colors, effects

depending ioBroker/testing#238

After add the Wled in Iobroker I get a lot of error message always the same message

Would be nice to have a datapoint in the segments to control the brightness in percent.
This will allow to ise the datapoint directly in Google Assistant.

Using the current value for the brightness in Google Assistant only allows the user to tune from 0-100 instead of 0-255.

I have a workaround with a small blockly which calculates the decimal value out of the percentage value and vice versa, but it would be much more comfortable to have it directly out of the adapter.

It also would be nice to control the effect ID directly with a number, to enable Google Assistant to say something like "turn on effect 2". At the moment it is not possible to change the effect by a single number, just by the dropdown.

Thanks!

Nowhere can I find the button to remove old devices from the list.
There is a button to add, but not to delete.

Wenn der on (On/Off) Status auf false gesetzt wird gehen ja, wie gewünscht die LEDs aus.
Wenn nun etwas geändert wird wie Farbe oder ähnliches, bleiben diese weiterhin aus.
ist es möglich, den on/off status, dann nur für das geänderte Segment einzuschalten?
die anderen Segmente bleiben weiterhin abgeschalten

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/DrozmotiX/ioBroker.wled

• [E154] common.dependencies must contain {"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}
• [E603] NO "## Changelog" found in README.md
• [E605] No actual year found in copyright. Please add "Copyright (c) 2022 DutchmanNL [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2022 DutchmanNL [email protected]" at the start of LICENSE

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.wled

• [E019] Invalid repository URL: https://github.com/DrozmotiX/ioBroker.wled. Expected: git+https://github.com/iobroker-community-adapters/ioBroker.wled.git

Thanks,
your automatic adapter checker.

Hallo,

bei mir wir seit v.0.5.1 der Status On/Off nur einmalig auf true gesetzt, danach wird nicht mehr aktualisiert.
Ist das so gewollt?

Hallo allerseits,

kurze Frage allgemein:

Normalerweise bin ich es gewohnt, dass Plugins die in ioBroker integriert werden "instant" nach einer Änderung auf einem Objekt reagieren und den neuen Status anzeigen. In dem Plugin hier hat man den 30 sec Timer der natürlich für sofortige Änderungen von irgendwelche Switches auf einem Dashboard ungeeignet ist.

Gibt es dafür ein Workaround? Den Timer auf 0 sec setzen ist denke nicht die Lösung da dann zu viele Abfragen gesendet werden an die kleinen Wemos.