On android the app ID is used for password matching, does apple really not do the same thing? That would be maddening!

You have a typo: platform: esphome.

Thanks for posting, good catch!

At 8tb, I can’t find any, but here is a 5tb disk:

https://www.amazon.com.au/Seagate-Barracuda-Internal-Drive-Factor/dp/B01LXO31IZ/ref=mp_s_a_1_13

Check the thickness though, your device may not accept 15mm disks.

The OPs device can take a nvme SSD and an internal HDD. Unclear if the current SSD is nvme or not though, but I assumed it was nvme.

The USB connection will likely be quite slow, and some external harddisks will power save aggressively.

You could get a largish 2.5" HDD and hook it up internally, might be a middle ground cost-wise?

I cant test this, but should it be something like:

# Example button configuration
button:
  - platform: template
    name: Livingroom Lazy Mood 1
    id: my_button

    # Optional variables:
    icon: "mdi:emoticon-outline"
    on_press:
      - logger.log: "Button 1 pressed"
  - platform: template
    name: Livingroom Lazy Mood 2
    id: my_button2

    # Optional variables:
    icon: "mdi:emoticon-outline"
    on_press:
      - logger.log: "Button 2 pressed"

As for the other thing, that might be something you need to write your own driver for? if you need some inspiration, this repo has a driver for mitsubishi heatpumps, which does something similar (read/write to a uart): https://github.com/echavet/MitsubishiCN105ESPHome

Out of curiousity, whats your success rate?

I dont think there is anything wrong with that, as long as you are setting the expectations right. In some ways, it takes the load off the maintainer, because they dont necessarily have to “fix” your code, they can just rewrite from scratch using your code as inspiration.

Different devs accept different things, and we are all burnt out to some degree.

I think you probably want to start small, i.e, normalise the colors first, and then do your dark mode change, but it really depends.

Did the dev not say why they rejected it? Seems very rude of them not to give a reason.

Depends on the project (and the maintainers), but have you reached out to the developers for assistance?

Touching a foreign codebase is always difficult, even for professional coders. I have found that it usually is a very hard slog for a few weeks or so, and then it will start to click in place. I think the only real shortcut is to ask for help and see if an existing dev can guide you through it.

That happens to my filament as well, i assumed it was drying out to much. Your humidity is way lower then mine, i’m typically around 50%. Not sure that this is the reason though

Same, im not normally one to worry about aesthetics, but the thin wedge is a really nice shape

This concept has existed for years in third party apps. All the major manufacturers are late to the game…

Won’t solve their problem, but they won’t be your friend anymore :)

The esphome config is more like a build script, it builds an esphome binary with the config built in. They are fairly simple yaml files, and there is plenty of doco and examples about. Esphome will generate a basic config for you, and you can modify it to suit.

So, to start with, you just need to install the esphome addon in HA. From there, you can plug the esphome dev board into the PC you use to access HA (ideally, youll want to use chrome, as it supports flashing the esp device directly), and in the esphome interface click the “New device” button. You choose a name for the device, and then click connect. Esphome UI will then connect to your board, and try to determine what it is, and will setup a basic “failsafe but does nothing” config, and it will flash it to the board.

From there, you can unplug the board, and subsequent flashes can happen over wifi. Adjust the config and reflash until it works. Home assistant should detect the board when it next boots up and you can add it as a device.

If you get dev boards, no additional hardware is required, its built into the usb interface. Software wise, you will need to use Chrome for the first setup, as firefox doesnt support WebSerial which is needed gor the first flash.

If you have any other questions shout out.

If you want something more “flash, then configure”, tasmota is another option. You flash the device from a webbrowser (https://tasmota.github.io/install), and then next time it boots it starts a wifi network you can connect to, and then you can connect to a web interface and use a gui to configure it and connect it to your HA. Esphome is a little more work upfront, but your configs can be backed up more easily.

I use esp32 dev boards, they are very cheap for this kind of thing. You dont need to make a circuit board, other than the voltage divider which youll need anyway. Then its just a bit of esphome code and you are done. They dont use much power either.

An “ADC that HA can read” sounds exactly like a job for a microcontroller to me?

I second the early return suggestions, but the other thing you should be aware of is that isalpha() is being evaluated twice unnecessarily. If its cheap and not call frequently, not a real big problem, but it is a waste of cycles. If you want to document the else, you could try:

...
}
else  // isAlpha() == false
{
...

Also, if isAlpha was something that could change between evaluation, such as isTuesday, you are at risk of the first call returning false, and then the second call returning true, which would skip both cases.

Thats probably the best way to look at it, otherwise it gets very difficult very fast.

If markup languages are locked out, then rust has other problems, because you then can’t change your cargo.toml file anymore.

And then there is the build script problem :/

As a thought excercise this has been interesting, there certainly are a lot of inter-dependencies between languages the deeper you look.

Sorry, I meant in the context of OPs question (so i guess up to them to set the rules). As in, you pick Python for the rest of your life, does that lock you out of C libraries? Its a bit of a rabbithole though, as many language runtimes would get excluded as well. There arent many languages that actually stand alone.

If you pick Python, do you still get libraries written in C or Rust?

C, can build any other language from that :D

And if i am gonna be miserable, may as well inflict as many vulnerabities on everyone else while I am at it.