No announcement yet.

MQTT On/Off plus Color Control

  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    I was able to duplicate your findings. It seems that any primary color (red, green, blue) works fine from Alexa. When you request a none-primary color, Alexa briefly displays 'Device malfunction', although eventually the color changes correctly and Alexa catches up and shows correct status. Requesting a primary color again is immediate and without error. Quite strange.

    This is all with Hue emulation enabled, which I was able to do thanks to your advice on using firmware built on Arduino 2.3.0.


    • #17
      I implemented the XY color translation and think it is pretty much working. What I do not know how to do is coax Alexa to sending XY rather than hue/sat to finish my checkout. I also find the requesting brightness works, but Alexa thinks device is malfunctioning. I do not know if it was doing that before I put my XY mods in place. Low brightness levels under 5% are problematic as the translation sometimes results in RGB color of 0 so the strip looks to turn off. This is probably a function of the specific LED hardware.


      • #18
        The XY color control looks to be working. I also implemented a minimum brightness for both Hue/Sat and XY Color so that on a color change the brightness dimmer value will not go to 0. Dimmer changes to 0 are still valid. It is mcsTasmota641A.bin at

        I still do not know why Alexa selects XY sometimes but most of the time Hue/Sat. With this update both will be handled.


        • #19
          Which controller are you using again? I have an H801, and a ZX-2844 controller. Both will load your image but seem to crash (I assume I'm looking at a stack dump in the serial window) then reboot. I know the H801 has only 512K of flash, so I am wondering if this is a low memory condition.


          • #20

            I believe these are setup with SSID/pw of Default and Default. I can build one for you with a different SSID/PW if you want to give me what to use at mcsSolutions at CenturyTel dot net. I thought it would create a AP if it could not find the SSID on your network.

            512K should only be a problem if you want to do OTA update.


            • #21
              I have no problem with the WiFi settings, I reset them using the serial console through the Arduino IDE that way there is no need to do the whole SoftAP thing. However once I get them on my WiFi and specify MQTThost, they just start resetting continually and dumping memory. It looks like this:

              ets Jan 8 2013,rst cause:2, boot mode3,0)

              load 0x4010f000, len 1384, room 16
              tail 8
              chksum 0x2d
              csum 0x2d

              00:00:00 CFG: Use defaults

              Exception (0):
              epc1=0x40237100 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

              ctx: sys
              sp: 3fff17f0 end: 3fffffb0 offset: 01a0

              3fff1990: 40103de5 40103de2 00000000 4000050c
              3fff19a0: 400005e1 401018b4 3fffc200 00000022
              3fff19b0: 40237100 00000033 00000017 00000000
              3fff19c0: 40103deb 04000102 00000000 00000001
              3fff19d0: fbf8ffff 04000002 3feffe00 00000100
              3fff19e0: 0000001a 00000018 04000102 40103dcc


              • #22
                when I get back home I will see if there are compile settings for 512k. All of mine have 1M.


                • #23
                  I looked at the compiler directive and it does indicate 1M flash size. There are instructions for Tasmota for other sizes using Arduino IDE, but I use platformIO/Atom so it was not clear to me what needs to be done in this environment. I did put the source at if you would like to give it a try.


                  • #24
                    Is it possible that mcsTasmota641A is based on mcsTasmotaMinimal.bin? The reason I ask is that I can't seem to set the SSID and Password parameters tonight. The first line of the serial log shows:

                    00:00:00 CFG: Use defaults
                    Init1 00:00:00 Project HUE CID Version

                    which implies the TasmotaMinimal image, where settings are not saved across a reset.


                    • #25
                      There are several options that are not included in the compile (e.g. WS2812, MHZ19) to minimize the binary size and not need to be concerned with a two step flash. BE_MINIMAL is not defined so it is not based on the minimal image.

                      For the "use defaults", Tasmota looks for a configuration word and if it is different than the image's then it will load the settings from the .bin. If it is the same (i.e. updated image with same config word) then it will not load the settings from the .bin.

                      I have not worked with the management of the settings, nor have I used the buttons on the main page to reset settings etc. When I want to assure old settings are not affecting a build I will first flash with a zero image which I get for ESPEasy Mega distribution. When I compile I used the settings that I want so after flashed everything is setup for my environment.