Trusted networks only work while logging in. They do not allow those IP addresses to access the URLs because they came from that IP. This was a deprecated feature that was removed in this release.
In 102 we’re adding a scene.create service and a scene editor.
In your automations you’ll be able to create a snapshot of a couple of states by creating a scene of them, then do some magic like flashing lights etc, then restore the state by activating the just created scene.
Scene editor is also a lot easier to build than a script editor. The UI for it is just the UI to control the devices, then at the end we take a snapshot and store in your scene.
I have never used Scenes in HA, but do have Scripts. Google see Scripts as Scenes in the Google Home app - treats them as you would expect a Script. Where you will find the Scripts (called Scenes in GH app) is where you create / change Routines. If you ask a Google Home device to run a Script, it works well in my experience.
I just updated Hass.io to 0.101.2 (that’s the latest version that was shown, even if 0.101.3 is out), and apcupsd throws this error:
Unable to prepare setup for platform apcupsd.sensor: Unable to set up component.
14:15 setup.py (ERROR)
Setup failed for apcupsd: Integration failed to initialize.
14:14 setup.py (ERROR)
Failure while testing APCUPSd status retrieval.
14:14 components/apcupsd/__init__.py (ERROR)
From the changelog:
Move imports in apcupsd component ([@Bouni](https://github.com/Bouni) - [#27803](https://github.com/home-assistant/home-assistant/pull/27803))
To provide perspective to the discussion about scenes, here is how they are handled in Premise. I’ve converted Premise’s terminology to Home Assistant’s (as best as a I can). There’s a lot of similarity with Home Assistant but with some important differences (like all of an entity’s options are available for use in a scene and a scene can have two behavior modes).
A scene is a collection of entities whose state and options are set to a desired value when the scene is turned on.
A scene can be turned on/off.
Any entity can be added to a scene and all of it options are available for use in the scene.
A scene’s behavior can be either set-restore or set.
If it is set-restore, when the scene is turned off, it restores everything to its previous value(s).
If it is set, when the scene is turned off, it leaves everything in its current state and does not restore to previous values.
Starting and stopping a scene are events that can be used to trigger an automation.
Scenes can be created in the UI by dragging entities from a palette, dropping them into a scene, then manually setting their state/options to the desired values.
As an alternative to manually setting an entity’s desired state, you can choose ‘record’ and it will use the selected entity’s current state (and options).
You can also choose ‘record’ for the entire scene (all entities listed in the scene will be set to their current state).
wow, that is a rich environment… Premise seems to be a great home automation system, every time you write about it, it seems to be very adequate in offering solutions for HA challenges.
It was a rich environment; it was discontinued many years ago and only a handful of people still use it. That’s why I have no qualms about describing its features, to inspire Home Assistant’s developers to freely copy them, because Premise is not a competing product (it’s more of a ‘historical artifact’ given that it was created almost 20 years ago).
Do you need a separate feature request for this, or would this discussion suffice…