Hallo VBS,

ist es eventuell möglich, dem MQTT noch zwei weitere Topics zuzuweisen ? Um weitere Integrationen außer FHEM herzustellen ?

Ich nutze derzeit HA und habe 3x die RGBWW Controller im Einsatz.

Diese würde ich gerne per MQTT anbinden, doch dazu ist das JSON was derzeit über den Command gesendet wird fehlerhaft oder falsch angeordnet.

wenn es nun 2 neue Topics geben würde wie z.b. command-ha und state-ha wäre das schon grandios.. oder nur einer als command-ha wäre schon verdammt geil. HA hätte gerne mit HSV und/oder RGB Settings diese Eingabe / Ausgabe als MQTT:

{ "brightness": 100, "color_temp": 155, "color": { "r": 1023, "g": 1023, "b": 1023, "h": 0, "s": 0 }, "state": "ON", "transition": 2, "white_value": 150 }

Usually fade timings are really accurate for me and do match well with the passed fade time in the command. But sometimes when issueing a fade command then the fade takes significantly longer to execute than desired.

I am not sure if this is an issue with the firmware or maybe with the RGBWWLed library. Also I tested only with FHEM so it might also be an issue with the FHEM module. But my best guess is that it is related to the firmare.

The issue is 100% reproducible for me using these commands:

set sz_lightLedWall hue 0
set sz_lightLedWall hue 100 60
set sz_lightLedWall hue 50
set sz_lightLedWall hue 200 60
set sz_lightLedWall hue 100
set sz_lightLedWall hue 200 60

I always issue one command then wait until it completes. Then I send the next command (manually). All fades work fine but the last one takes about 74 seconds to complete instead of the targeted 60 seconds.

I am using latest firmware 0.3.1.

When the controller is in a closed case, it's hard to see if a reboot was successful.
It would be good to have a short light signal, to show that the firmware has initialized and maybe connected to the network.
This could be implemented as a configurable mode so the old behavior is kept the default.
Taking the idea a bit further, different light signals could be defined to help debug the controllers current state like, probably the most typical error, unable to connect to wlan, but also things like states of OTA etc.

I'd love to be able to do the following:

• POST a sequence of fade commands for storage in SPIFF under a unique name for later execution.
• POST some kind of "execute sequence" command to start the sequence of fades.
  Also, it should be possible to make the controller execute a given sequence a defined number of times or indefinitely (looping).
  This would essentially make the controller truly programmable, e.g. store a fire simulation for creating a cosy atmosphere when cuddling on the sofa with your SO or pre-program some wild color sequences for the next party.

Many simple FET driver circuits require low-active driving.
For example, simply adding a small NPN and two resistors per channel to your original schematic would allow the IRLZ44N FETs to switch much higher currents than currently possible with only 3.3V of gate voltage.

This would be useful for people building their own hardware.

19:05:52 **** Build of configuration Sming for project RGBCTRLfw ****
make -k all
OC out/build/libmain2.a
make -C /c/tools/sming/sming/rboot
make[1]: Entering directory /c/tools/sming/sming/rboot' CC rboot-stage2a.c LD /c/Development/esp_rgbww_firmware/out/build/rboot-stage2a.elf E2 /c/Development/esp_rgbww_firmware/out/build/rboot-hex2a.h CC rboot.c LD /c/Development/esp_rgbww_firmware/out/build/rboot.elf E2 /c/Development/esp_rgbww_firmware/out/firmware/rboot.bin make[1]: Leaving directory/c/tools/sming/sming/rboot'
C+ app/application.cpp
In file included from include/user_config.h:29:0,
from include/RGBWWCtrl.h:55,
from app/application.cpp:23:
c:/tools/sming/sming/system/include/esp_systemapi.h:6:21: fatal error: ets_sys.h: No such file or directory
compilation terminated.
make: *** [out/build/app/application.o] Error 1
C+ app/ledctrl.cpp
In file included from include/user_config.h:29:0,
from include/RGBWWCtrl.h:55,
from app/ledctrl.cpp:22:
c:/tools/sming/sming/system/include/esp_systemapi.h:6:21: fatal error: ets_sys.h: No such file or directory
compilation terminated.
make: *** [out/build/app/ledctrl.o] Error 1
C+ app/mqtt.cpp
In file included from include/user_config.h:29:0,
from include/RGBWWCtrl.h:55,
from app/mqtt.cpp:22:
c:/tools/sming/sming/system/include/esp_systemapi.h:6:21: fatal error: ets_sys.h: No such file or directory
compilation terminated.
make: *** [out/build/app/mqtt.o] Error 1
C+ app/networking.cpp
In file included from include/user_config.h:29:0,
from include/RGBWWCtrl.h:55,
from app/networking.cpp:22:
c:/tools/sming/sming/system/include/esp_systemapi.h:6:21: fatal error: ets_sys.h: No such file or directory
compilation terminated.
make: *** [out/build/app/networking.o] Error 1
C+ app/otaupdate.cpp
In file included from include/user_config.h:29:0,
from include/RGBWWCtrl.h:55,
from app/otaupdate.cpp:22:
c:/tools/sming/sming/system/include/esp_systemapi.h:6:21: fatal error: ets_sys.h: No such file or directory
compilation terminated.
make: *** [out/build/app/otaupdate.o] Error 1
C+ app/tcpserver.cpp
In file included from include/user_config.h:29:0,
from include/RGBWWCtrl.h:55,
from app/tcpserver.cpp:22:
c:/tools/sming/sming/system/include/esp_systemapi.h:6:21: fatal error: ets_sys.h: No such file or directory
compilation terminated.
make: *** [out/build/app/tcpserver.o] Error 1
C+ app/udpserver.cpp
In file included from include/user_config.h:29:0,
from include/RGBWWCtrl.h:55,
from app/udpserver.cpp:22:
c:/tools/sming/sming/system/include/esp_systemapi.h:6:21: fatal error: ets_sys.h: No such file or directory
compilation terminated.
make: *** [out/build/app/udpserver.o] Error 1
C+ app/webserver.cpp
In file included from include/user_config.h:29:0,
from include/RGBWWCtrl.h:55,
from app/webserver.cpp:22:
c:/tools/sming/sming/system/include/esp_systemapi.h:6:21: fatal error: ets_sys.h: No such file or directory
compilation terminated.
make: *** [out/build/app/webserver.o] Error 1
CC /c/tools/sming/sming/rboot/appcode/rboot-api.c
c:/tools/sming/sming/rboot/appcode/rboot-api.c:10:21: fatal error: c_types.h: No such file or directory
compilation terminated.
make: *** [out/build//c/tools/sming/sming/rboot/appcode/rboot-api.o] Error 1
CC /c/tools/sming/sming/rboot/appcode/rboot-bigflash.c
In file included from c:/tools/sming/sming/system/include/rboot-integration.h:11:0,
from c:/tools/sming/sming/rboot/appcode/rboot-bigflash.c:9:
c:/tools/sming/sming/system/include/esp_systemapi.h:6:21: fatal error: ets_sys.h: No such file or directory
compilation terminated.
make: *** [out/build//c/tools/sming/sming/rboot/appcode/rboot-bigflash.o] Error 1
Checking for spiffs files
No files found in ./webapp.
Creating empty out/firmware/spiff_rom.bin
Creating rom 'out/firmware/spiff_rom.bin' of size 0xf4240 (1000000) bytes.
Creating empty filesystem.
make: Target `all' not remade because of errors.