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
Why would something like this have a threshold?
Has anyone checked in with Oprah?
This is jobseeker. If there are people on it who can't work that's still a failing of the welfare system, albeit a different one.
Since the author was unable to find it, here are the bits relevant to recommendation algorithms:
25F Design features
(1) A design feature of an online service includes the following:
(a) a recommender feature;
(b) a logged-in feature;
(c) an endless-feed feature;
(d) a feedback feature;
(e) a time-limited feature.
Recommender feature
(2) An online service has a recommender feature if the service can:
(a) select material by reference to any information that the
service has associated with an end-user’s account; and
(b) display that material to the end-user while the end-user is
using the service.
25G Negative behavioural impacts
(1) The following design features of online services are taken to have
negative behavioural impacts:
(a) a recommender feature;
(b) a logged-in feature;
(c) an endless-feed feature;
(d) a feedback feed feature;
(e) a time limited feature;
(f) a design feature determined by the Minister under
subsection (2).
(2) The Minister may, by legislative instrument, determine that a
design feature of an online service is taken to have negative
behavioural impacts.
Division 3—The digital duty of care
26 The digital duty of care
Digital duty of care
(1) A person responsible for an online service must ensure, so far as is
reasonably practicable, a safe online environment.
Note: For safe online environment, see section 25B.
(2) This requirement is the person’s digital duty of care.
Mandatory requirements
(3) To comply with the digital duty of care, the person must also do
the following:
(a) manage design features of the service appropriately,
including by providing user empowerment tools as required;
(b) conduct risk assessments in accordance with section 26A;
(c) take effective measures as necessary to address those
assessments.
Note: Failure to comply with this subsection will constitute a breach of the
digital duty of care.
User empowerment tools
(4) The Minister may, by legislative instrument, require specified
online services to provide specified user empowerment tools.
Note: For specification by class, see subsection 13(3) of the Legislation Act
(5) The online services or user empowerment tools may (without
limitation) be specified by reference to any matter.
Note: The user empowerment tool may, for example, be specified by
reference to the amount or kind of control the tool gives a user of an
online service over the operation of particular design features.
(6) A user empowerment tool allows a user of an online service to
manage the way design features of the service operate for the user,
including, for example, by providing control over the kind of
content that is recommended for the user.
