2021.5: Stability, performance, triggers, color modes!

JakeK · May 8, 2021, 11:56am

I’m also still able to set the white channel directly with a service call, it appears only the UI has s*** the bed.

service: light.turn_on
target:
  entity_id:
    - light.qubino_goap_zmnhwd1_flush_rgbw_dimmer_level
data:
  white_value: 255

For those having issues with RGBW lights with this latest update this allows control of all four channels still.

service: light.turn_on
target:
  entity_id:
    - light.YOUR_LIGHTS_NAME_HERE
data:
  white_value: 255
  rgb_color:
    - 255
    - 255
    - 255

ThePirat · May 8, 2021, 12:43pm

The old web scraping worked (flawlessly) for me too…

rob1303 · May 8, 2021, 2:43pm

Not sure why this worked - but I now have the color wheel in HA working with no issues for my Tasmota lights (Tasmota integration).

I went to the IP address for each light adjusted the colour using the Tasmota sliders.

After doing this the colour wheel in HA has been working with no issues. Including continuing to work after rebooting of HA and cycling power/off/restarts of each light.

Hope this works for you.

carsten_h · May 8, 2021, 3:03pm

If I set the color via the tasmota website, the color wheel is showing me the correct values, but when I try to set it in HA, it still jumps to white in the middle.

Which version of tasmota are you using? I have 9.4.0.3 running.

Here is the tasmota log when switching to green:

16:07:09.363 MQT: tas-li-E14-1/tele/STATE = {"Time":"2021-05-08T16:07:09","Uptime":"0T00:06:23","UptimeSec":383,"Heap":26,"SleepMode":"Dynamic","Sleep":10,"LoadAvg":99,"MqttCount":1,"POWER":"ON","Dimmer":87,"Color":"0,222,0,0","HSBColor":"120,100,87","White":0,"Channel":[0,87,0,0],"Scheme":0,"Fade":"OFF","Speed":1,"LedTable":"ON","Wifi":{"AP":1,"SSId":"BleibWeg!","BSSId":"2C:3A:FD:D4:F9:91","Channel":11,"RSSI":96,"Signal":-52,"LinkCount":1,"Downtime":"0T00:00:04"}}
16:07:09.400 MQT: tas-li-E14-1/stat/RESULT = {"POWER":"ON","Dimmer":87,"Color":"0,222,0,0","HSBColor":"120,100,87","White":0,"Channel":[0,87,0,0]}
16:07:09.419 MQT: tas-li-E14-1/tele/STATE = {"Time":"2021-05-08T16:07:09","Uptime":"0T00:06:23","UptimeSec":383,"Heap":24,"SleepMode":"Dynamic","Sleep":10,"LoadAvg":104,"MqttCount":1,"POWER":"ON","Dimmer":87,"Color":"0,222,0,0","HSBColor":"120,100,87","White":0,"Channel":[0,87,0,0],"Scheme":0,"Fade":"OFF","Speed":1,"LedTable":"ON","Wifi":{"AP":1,"SSId":"BleibWeg!","BSSId":"2C:3A:FD:D4:F9:91","Channel":11,"RSSI":96,"Signal":-52,"LinkCount":1,"Downtime":"0T00:00:04"}}
16:07:09.457 MQT: tas-li-E14-1/stat/RESULT = {"POWER":"ON","Dimmer":87,"Color":"0,222,0,0","HSBColor":"120,100,87","White":0,"Channel":[0,87,0,0]}
16:07:09.476 MQT: tas-li-E14-1/tele/STATE = {"Time":"2021-05-08T16:07:09","Uptime":"0T00:06:23","UptimeSec":383,"Heap":24,"SleepMode":"Dynamic","Sleep":10,"LoadAvg":108,"MqttCount":1,"POWER":"ON","Dimmer":87,"Color":"0,0,0,222","HSBColor":"120,100,0","White":87,"Channel":[0,0,0,87],"Scheme":0,"Fade":"OFF","Speed":1,"LedTable":"ON","Wifi":{"AP":1,"SSId":"BleibWeg!","BSSId":"2C:3A:FD:D4:F9:91","Channel":11,"RSSI":96,"Signal":-52,"LinkCount":1,"Downtime":"0T00:00:04"}}
16:07:09.514 MQT: tas-li-E14-1/stat/RESULT = {"POWER":"ON","Dimmer":87,"Color":"0,0,0,222","HSBColor":"120,100,0","White":87,"Channel":[0,0,0,87]}

It seems that HA is sending RGBW as: 0,222,0,0 but it is set as: 0,0,0,222. Very strange!

Bartem · May 8, 2021, 3:23pm

I just wanted to throw some kudos out there for the database/performance improvements… I believe I read something about possible memory leaks but can’t find it now… but either way my idle CPU now sits between 1-2% instead or 3-5% and I was actually able to bump up the quality of my image processing. Thanks for your hard work guys! Much appreciated!

majorsl · May 8, 2021, 4:18pm

You aren’t the only ones, even with 2021.5.1 the UI color wheel for Tasmota (in my case Tasmota via MQTT) is horribly broken. Like you all note: I can set it via Tasmota and it fine on the color wheel, but when I try to change it is goes white. Automations that control the RGB values continue to work as expected. I have Tasmota bulbs (RGB, RGBW, RGB CCL) as well as LED strips. All fail to work with the color wheel now since 2021.5.0.

rob1303 · May 8, 2021, 4:49pm

I am using 9.3.1

This is what appears in Tasmota Console when I set green on the dial in HA:

02:39:41.994 MQT: GenBbC04/tele/STATE = {"Time":"2021-05-09T02:39:41","Uptime":"0T00:03:04","UptimeSec":184,"Heap":24,"SleepMode":"Dynamic","Sleep":10,"LoadAvg":103,"MqttCount":1,"POWER":"ON","Dimmer":100,"Color":"0,255,0,0","HSBColor":"120,100,100","White":0,"Channel":[0,100,0,0],"Scheme":0,"Fade":"OFF","Speed":1,"LedTable":"ON","Wifi":{"AP":1,"SSId":"xx_NOT","BSSId":"XX:63:DA:03:4B:67","Channel":10,"RSSI":40,"Signal":-80,"LinkCount":1,"Downtime":"0T00:00:03"}}
02:39:42.002 MQT: GenBbC04/stat/RESULT = {"POWER":"ON","Dimmer":100,"Color":"0,255,0,0","HSBColor":"120,100,100","White":0,"Channel":[0,100,0,0]}

Definitely not reverting to centre/ white for me.

If you set color on sliders in Tasmota does the bulb change to the correct color?

If you set color on wheel in HA (before it switches to white) does the bulb also change to the correct color?

arkoko · May 8, 2021, 5:27pm

With version 2021.05 systemmonitor disk usage sensors does not work properly - for all partitions show the same value.
Sensor definition:

platform: systemmonitor

  resources:
    - type: disk_free
      arg: /
    - type: disk_free
      arg: /share
    - type: disk_free
      arg: /media

df from terminal:

config $ df -hT
Filesystem           Type            Size      Used Available Use% Mounted on
overlay              overlay       195.9G      7.9G    178.0G   4% /
/dev/nvme0n1p2       ext4           27.4G      4.6G     21.3G  18% /share
/dev/nvme0n1p5       ext4          697.4G    593.6G     68.3G  90% /media

And result:

mirekmal · May 8, 2021, 5:32pm

Hm… I might be wrong I’m not familiar with disk layout on underlying OS, but since your agruments points to the same volume (I think), just different folders, free space will always be the same as it shared across all folders.

petro · May 8, 2021, 5:35pm

Ah yes, you are correct.

arkoko · May 8, 2021, 6:04pm

As df shows - those (at least /share and /media) are different partitions and mounts. Before last upgrade monitor worked correctly.

majorsl · May 8, 2021, 6:43pm

There is a nice video in there that shows what is happening to us with Tasmota and the color wheel. Also, yes, the color sliders in my Tasmota work fine for all my bulbs (and LED strips).

EDIT: Opened an issue for it: Tasmota Lights - Color Wheel not Working · Issue #50316 · home-assistant/core · GitHub

petro · May 8, 2021, 9:38pm

then write up the issue on github

carsten_h · May 8, 2021, 9:46pm

Yes! And the colorwheel in HA is showing this also.

Yes.

carsten_h · May 8, 2021, 9:51pm

That is interesting. I don’t have the buttons “Color” and “Temperature” for my tasmota LED as you can see in my screenshots above. I only have these for ZigBee LED.

Strange, strange!

majorsl · May 8, 2021, 10:07pm

That depends on your LED/Bulb. RGBW or RGBWW won’t have it because the white is whatever you bought, usually “daylight” or “warm white.” Newer devices are RGB CCT where you can adjust between the warm white and daylight color temp in addition to the RGB colors.

123 · May 8, 2021, 10:26pm

I just discovered it also thwarts my ability to quickly and easily patch a container’s source code. For example, Supervisor now detects if its code has been altered and then declares my instance to be both unsupported and unhealthy.

“unhealthy” blocks the installation of new Add-ons (amongst other things). It rendered the switch I made from Ubuntu to Debian kind of pointless because now I’m back to having an unsupported system (and unhealthy).

I also patch the code in the homekit_controller integration. It’s just a little tweak (change light levels from float to int) and at least that still works without complaint. However, I suspect it’s only a matter of time before that also becomes impossible.

At that point, I will have to give serious thought to switching from Home Assistant Supervised to Home Assistant Container to bypass these ever-growing constraints. I already gave up on Home Assistant OS because the darn thing cannot be stopped from checking Internet connectivity ever 5 minutes (with multiple calls each interval).

NOTE

In case anyone is wondering why not just ask to have these little modifications incorporated into the source code, I have and the respective authors expressed no interest. Unfortunately, I don’t have the needed skills to submit PRs to the official repos so my only remaining avenue is to patch the source code (within the docker container).

Dolores · May 9, 2021, 1:15am

Thank you for sharing this. My understanding of git is intensely limited. Is this allegedly already fixed? Or will it be in the next release of adaptive lighting?

Edit: my issue seems to have magically gone away, without an update to HA or adaptive lighting… Maybe I just needed another reboot?

rob1303 · May 9, 2021, 3:34am

Major - edit to originally written as I have managed to ‘break’ my fix and find another data point.

My ‘fix’ broke when some time based brightness level automations ran.

I could however get the colour wheel to work in HA by moving the “White Brightness” slider on the wheel page the far left (0). The color wheel then starts working again.

It then stops working again when the “White Brightness” slider is anywhere other than 0.

So basically for me:

in HA - white brightness 0 = colour wheel working
In HA - white brightness level >0 = colour wheel snapping back to centre.
In Tasmota console - where ‘W’ (in RGBW color) is anything other than 0 = colour wheel snapping back to centre.

Are you able to replicate?

pedolsky · May 9, 2021, 9:32am

That was a very short pleasure - with 21.5 everything got editable again on IOS … and went away with 21.5.1. Is someone able to confirm the issue?