Let me introduce yet another rabbit hole to go into.
It occurred to me that I have a similar device myself. I built some devices that display the time and other data using MQTT. Every ten seconds an MQTT message is published with the time and other data topics. This was all done before I discovered Home Assistant.
I use Node-Red to publish the MQTT data and it only takes five nodes:
Thank you for this info. The creator of the firmware for the clock I build also uses Node Red, but his is much more complicated.
If I can accomplish this using ESPhome, would you recommend going that route instead of MQTT/Node Red?
The only thing I’m not sure of with the ESPhome clock firmware I have is that my data wiring is a different order than the person I got this code from. I assume that will need to be changed, but I’m not sure how to do that. If I post the code, would you be able to print me in the right direction?
It’s entirely your choice. As I said, I would prefer my project be on ESPHome, but the necessary platform doesn’t exist. In your case, you can buy another ESP module and use this project as a way to learn ESPHome. Or you could install the Node Red Add-on in Home Assistant and publish the same time in the same topic/data format that the clock uses today. Or you could send the MQTT messages directly from Home Assistant. Each method has advantages. As I said there are a lot of rabbit holes to get you to the same result.
Where? The only place I can find the ht16k33 14-segment LED display in the docs is a couple of feature requests. I did find a three-year old project on GitHub using platform: lcd_ht16k33 but no such platform appears in my search.
I know this is getting a long way off-topic, but you are the one who said there was a platform for 14-segment LED displays (without a link), so show me ANY platform or component for a 14-segment LED display on Home Assistant or ESPHome. Please.
Passwords for ESPHome devices are for the paranoid. You only need
Passwords are optional.
When you first create the device in the ESPHome panel, ESPHome generates passwords for you. But you can use any password you want, and even the same password for every ESPHome device. Just put them in the secrets.yaml file.
API passwords are deprecated since half a year and shouldn’t be used at all anymore
“Also, ESPHome is deprecating the old password-based authentication for its API in favor of the more secure encryption key. If one of your ESPHome devices is still using a plain password, Home Assistant will notify you by creating an issue in your Repairs dashboard.”
Just use an encryption key which conveniently get’s created for you when using the ESPHome dashboard wizard to create a new node
That’s just incorrect. ESPHome by default does provide a key which is not a “random number” but a 32-byte base64 encoded string which is used as pre-shared key for encryption.
You know why ESPHome does that for you, me and others @stevemann? Because many (probably the majority) users have no or little clue about encryption and securing communications. And that’s totally fine as encryption is complex and even a small bug/error can render it unsafe. Worst is probably only your suggestion to “don’t bother” and communicate in plain text without any authentication
In case you want to explore new unknowns you could start with a read of the noise protocol which is used under the hood in ESPHome.
I have another question regarding my code. I have it running, but it definitely isn’t formatted correctly. I believe it is using 1 pixel per segment, but I need it to use 3 pixels per segment. I know there is code I can use to define segments, but I am not sure how to implement that (where in my code it should be placed) and how to get the code to use those segments.
I can upload my code if that will help, but I appreciated any help you can provide.