any chance we could up the granularity on the battery colors? experience shows that many batteries remain in the green zone for a long time, and only after lowering into the mid 50% or so, start accelerating downwards. Having more than 3 colors for high, medium and low is a ‘nice to have’
think:
icon_color: >
if (['unavailable','unknown'].includes(state)) return 'steelblue';
if (state > 75) return 'green';
if (state > 50) return 'gold';
if (state > 25) return 'orange';
if (state > 10) return 'brown';
return 'red';
I might have overlooked device_class: heat? was thrown off by the ‘off’ icon to be thermometer. So I didnt associate that with a heating device. Made a PR to change that to flame-off
Post your errors, It’s working for me. FYI reporting issues like this usually require all information, not abridged versions from the user. I.e. Post fully un-paraphrased errors accompanied with a description of what’s not working.
Source: components/hassio/http.py:111
First occurred: 07:32:58 (3 occurrences)
Last logged: 08:25:05
Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py”, line 433, in _handle_request
resp = await request_handler(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py”, line 504, in _handle
resp = await handler(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py”, line 117, in impl
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/security_filter.py”, line 60, in security_filter_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/forwarded.py”, line 100, in forwarded_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/request_context.py”, line 28, in request_context_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/ban.py”, line 81, in ban_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/auth.py”, line 236, in auth_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/view.py”, line 136, in handle
result = await result
File “/usr/src/homeassistant/homeassistant/components/hassio/http.py”, line 75, in _handle
return await self._command_proxy(path, request)
File “/usr/src/homeassistant/homeassistant/components/hassio/http.py”, line 111, in _command_proxy
await response.prepare(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py”, line 421, in prepare
return await self._start(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py”, line 429, in _start
await self._write_headers()
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py”, line 502, in _write_headers
await writer.write_headers(status_line, self._headers)
File “/usr/local/lib/python3.10/site-packages/aiohttp/http_writer.py”, line 131, in write_headers
self._write(buf)
File “/usr/local/lib/python3.10/site-packages/aiohttp/http_writer.py”, line 76, in _write
raise ConnectionResetError(“Cannot write to closing transport”)
No idea where to change it and I will not build theme for scratch because some mad scientist came with bright idea of his own hardcoded colors not reachable in File Editor in HA
Using the Local calendar - is there a way to use the event title as a trigger? Like I have a vacuum cleaning scheduled to start at 12 o’clock and a heater at 11 PM. From what I see I can only create two separate calendars to distinguish the trigger? Also is there an option to edit an event? Like I want to start the cleaning at 7PM from now on.
The trigger variable contains information about the Calendar Trigger. You can reference trigger.calendar_event.summary in a template and determine if its value refers to the vacuum or the heater.
In addition, you can put information in the Calendar event’s description and reference it using:
Just a small question then - why users cannot define colors like “rgb”, “#ff0000” etc - why they have to use “255,0,0”? Why all new vars accept this “255,0,0” format?
Not exactly.
These vars are used only for SOME cases, all binary_sensors still use “paper-item-icon-color”:
– possible colors “state-binary-sensor-alerting-color” & “paper-item-icon-color” - for “tamper, smoke, safety,problem moisture,heat, gas,carbon_monoxide,battery” classes (may be more classes are added, checked only these documented);
– possible colors “state-binary-sensor-color” & “paper-item-icon-color” - for other classes.
We all do respect your personal efforts, it is great when people spend their life not only for themselves, but please think about possible solutions:
Reconsider colors - make them at least more different from each other, currently they look same, like here:
Allow using “green”, “rgb(0,255,0)”, “#00ff00” values for vars. And allow using these values not only in themes - but in card-mod & Code Inspector (see a glitch described here).
Solve issues like “all trackers at Home have different colors”.
Thanks
