So he proved his point, didn’t he…
So he proved his point, didn’t he…
Good news: The gauge card is a standard component.
I like the low battery panel. I might copy that. I have a general overview over all batteries, but it didn’t occur to me that I could filter the values and show only the ones needing replacement.
My default dashboard is maybe a little bit unusual:
It’s the blood glucose levels of my daughter (and mine in the next tab) as we are both T1 diabetics. The levels are transmitted via a tool called Nightscout and then shared with Home Assistant. This allows my wife and myself to get notified via light signals at night (in addition to the alarm her blood glucose sensor sounds). The dashboard also contains average levels for several timespans as well as an estimated long time level (Hb1Ac).
The second dashboard is an overview of all the lights, sensors and appliances located on a floorplan of the house:
There are several tabs grouping lights (and appliances), sensor readings and battery levels.
I would love to see this as well. It’s definitely a challenging topic as crossposts can happen across instances, but I think it would greatly improve the discoverability of content and new communities.
I have a motion sensor in the bedroom that turns the light on when you enter it (or leave it) and turns it off after some time once there is no motion detected anymore. But there is also a button right next to the door which disables the automation for 10 minutes for entering the bedroom at night when our youngest is already sleeping in the room.
Simple but very useful and even my wife likes it alot.
Oh yes. Creating an empty environment can easily take up several gigabytes…
So your tooling was at fault for assuming something that has always been declared a convention not a rule. It is like assuming we will never reach the year 2000 and there only storing the last to digits for the year…
You don’t have to, but if you do you may have the ability to stand up against a company trying to shut down your open source project…
You can. The STL files for the case and the PCB layout are available on GitHub: https://github.com/nplan/HomeButtons There even is a section on soldering and building it yourself on the documentation.
I also have some of the IKEA buttons. They are nice and I like the interchangeable labels which make it easy to print something yourself and just put it under the clear plastic lid if you want to customize them.
If you like it a little bit more fancy: There’s a guy in Slovenia who designed HomeButtons and also sells them if you don’t want to print and build them yourself (links are on the docs page). They speak via WiFi to a MQTT server and are easily integrated into Home Assistant. You can remotely change the labels if you want to and the battery life is very good.
I really hope somebody finds a way to upload custom firmware to Google or Alexa speakers. I like the hardware and the sound and I know I will not be able to build something as nice myself…
Shelly devices are also my goto. Never had any problems with them and they are very versatile and well built.
Would somebody share some screenshots?
That is really a missing part of this whole thing. I get that I could build something myself, but I don’t want to have the hassle of doing it and keeping it working all the time (because I am able to build it, but not on a “works perfectly all the time” level). I really hope that sometime in the future there is a standard for smart speakers (and screens maybe) that allows me to add them to my cloud service of choice.