Just got a few Zigbee Smoke sensors and tried to integrate them in your theme.
I tried to use this for the room:
safety: binary_sensor.wohnzimmer_rauch
and in global.yaml the normal String :
safety_ok_strings: [“Ok”, “Idle”, “off”]
Sadly I don’t see anything in the room even if I change the value of the sensor to on, which indicates smoke detected.
Is this still working or am I doing something wrong ?
Thank you for clarifying
P.s. You are doing a really good job.
I’m really looking forward to 1.5. I no longer update until 1.5 is out just
to be sure it is working fine until release ^^
I had a discussion about the name “Dwains Theme” on my themes Discord server. Home Assistant uses the name theme for some files you can make for customizing the colors of HA itself. As this project is a fully working interface. I was thinking about renaming it to Dwains Interface or Dwains Dashboard. It also confuses people, because they think Dwains Theme is just a file with some colors and not a fully worked-out working interface.
I did a small poll and the outcome was simple. We are going to rename Dwains Theme to Dwains Dashboard.
Just a little question as for now my nuki lock gets unlocked and locked very well.
For 1.5 I would wish to open the door fully not just lock and unlock (lock.open service)
If it doesn’t make too much work ^^
(I mean I can change it by my own But natively supported feels better ^^)
Edit:
As for now I changed the hold_action to call lock.open ^^ (the popups currently not working that well so no disadvantages)
I’ve got a question which may or may not be possible, but curious if anyone knows none the less. I have updated my smart bulb line up to consist solely of Inovelli LZW42’s. These are great bulbs, with a minor annoyance that they ramp up/down very slowly by default (could take up to around 5 seconds to ramp down from max brightness for example).
There are a few methods that can be used to address this; I could go into the bulb itself and set the transition time directly within the bulb config options. This would resolve all issues, at the cost of me being unable to use a unique transition time within future automation’s… Unfortunately I rely on manually defined transition times in a couple of my automation’s, so I cannot do this.
Option two is, as previously mentioned, define transition time manually in automations. This is the method I’ve used until now and it works well, but there’s no place I can see to do this within Dwains theme. So while it works perfectly (and looks the best out of every theme I’ve tried using in the past), if I use it to turn my bulbs on, they turn on/off very slowly.
Does anywhere know where I could set a defined transition time for this theme, if anywhere? It’s really not the end of the world if it takes a little longer than I’d like to turn bulb on/off, this just became more of a curiosity thing for me at this point.
Are you using the normal Philips Hue Bridge?
I’m using deConz and I don’t like Philips Hue as they do not provide firmware updates
for non Hue Bridge Users.
I do yes, I have Hue bridge with all lights + motion sensors. This way my house lights always work 100% uptime. I also have used zigbee2mqtt, cc2351 with ZHA, and conbee stick with ZHA and with Deconz for all my other sensors in the house.
while parsing a flow mapping in “/config/dwains-theme/addons/rooms/office/sonos/button.yaml”, line 6, column 10 expected ‘,’ or ‘}’, but got ‘[’ in “/config/dwains-theme/addons/rooms/office/sonos/button.yaml”, line 6, column 29