Nintendo is famously litigious even with legitimate fangames. Including purchases in this is asking for legal trouble.
Are you kiwi perchance? I've only heard kiwis refer to the country itself as Aussie, and I'm curious if there are other places that do the same
There are precisely two meaningfully dangerous spiders. Redbacks and Sydney Funnelwebs. The former keep to themselves, and the latter have an attitude problem because they have to live in Sydney
Both are covered by antivenin that all paramedics and emergency rooms keep.
Nobody has died from a spider bite in Australia since 1979. The Sydney funnelweb antivenin was developed in 1980.
If you're putting in street numbers and only getting back streets, chances are that street number does not exist in openstreetmap yet and you'll need to add it
Concrete doesn't dry, it cures. It is quite possible to fill 3D prints with it, and it has been done.
There's always OpenHAB
I've not heard of this before and the website didn't help with "what" and "why". What is this? Did anyone here use this, and what was your experience?
TL;DR the python code converts the yaml into a (pure) C++ program.
ESPHome is by-and-large a build system to build bespoke C++ programs. The python files you're seeing describe how that yaml file maps to the C++ files.
The core idea is that end users (including people managing custom sensors) as much as possible only have to interact with the yaml file. The yaml file lists what components you want to run and their configurations. A component is in general a subdirectory of esphome/esphome and is intended to be independent of other components.
Those github references in the yaml pull in external components from the community. It's roughly equivalent to dropping another folder into the source tree (noting again that you shouldn't usually need to have the source tree at all).
Running esphome copies all used components into a separate source tree, with substitutions and variables set according to the yaml configuration (defined by the component's python files) and builds a bespoke binary for you that will run on your device.
If you want to include code that's not already an ESPHome component, you will need to make it into one. You can do this in place in the source tree or by creating an external component yourself. You will want to use an existing component as a template for this. Have a look for if ESPHome itself or a community component already exists first because it will make your life so much easier.
I had a similar failure rate then changed my charger and haven't had a battery fail since. My original charger was Energiser branded, which is the most common battery where I live so I thought it had to be fine. I replaced it with an eneloop BQ-CC55. I don't love it - it's a fast charger and it makes batteries uncomfortably hot, but it was able to charge batteries to full health that both my energiser and trickle charger thought were dead dead. That includes energiser batteries!
Low self discharge is the standard now, Eneloop is no longer unique.
Given our history of government security I'm honestly expecting this to come out as Services Australia hosting private information over an unprotected, undocumented API
