2022.9: Home Assistant Birthday Release!

bagelos · September 24, 2022, 10:31am

Hi All, I have had some success fixing my issue. I started with a fresh venv and following changes.

cd /srv
current_time=$(date “+%Y.%m.%d-%H.%M.%S”)
mv homeassistant homeassistant.$current_time
mkdir homeassistant
chown homeassistant:homeassistant homeassistant

su - homeassistant ; bash

cd /srv/homeassistant
python3.10 -m venv .

source bin/activate

python3.10 -m pip install --upgrade homeassistant
python3.10 -m pip install --upgrade home-assistant-frontend

FAILS - SO FIXING ERROR BY ERROR

python3.10 -m pip install --upgrade “sqlalchemy==1.4.40”

FAILS - ERROR WITH DENONAVR - MAYBE HTTPCORE

python3.10 -m pip install --upgrade “httpcore==0.14.7”
python3.10 -m pip install --upgrade “httpx==022.0”

SEEMS TO BE WORKING

nickrout · September 24, 2022, 11:35am

Post to github if you want dev attention.

krulbel · September 24, 2022, 1:46pm

Did you find a solution for the iOS app with the new Scheduler? I’d like to move all my input_datetime entities to the new Scheduler helper, but I must be able to change the start/stop timing from an iOS device.

Maverick · September 25, 2022, 7:49am

I now have an unsupported installation. I found this out by a random check of the System information page. It doesn’t show up anywhere else. This is why I’d like it to be back on a more prominent place.

darkly · September 25, 2022, 1:12pm

Can tell you how much I hate this Streamlining of automations.

Just leave it as it was.

nickrout · September 25, 2022, 8:54pm

Sigh. Hard to please everyone

solomos · September 26, 2022, 6:57pm

I have many Shelly’s.
Since the last update 2022.9.6, the unavailable nightmare has returned!

Has anybody got the same problem ???

kobyb1988 · September 26, 2022, 7:23pm

Hello. After automatically update my Home Assistant disappeared in my network and I did understand what happened. I have an error
[E] Sep 26 12:48:11 keenetic-0847 nginx: 2022/09/26 12:48:11 [error] 8584#0: *30341 connect() failed (148: Unknown error) while connecting to upstream, client: 49.12.208.55, server: ha.iotpalatkinburnhousesmart.keenetic.pro, request: “POST /auth/token HTTP/2.0”, upstream: “http://192.168.1.100:8123/auth/token”, host: “ha.iotpalatkinburnhousesmart.keenetic.pro”

Can anybody help me?Processing: self-test_KN-3010_stable_3.08.C.5.0-1_router_2022-09-26T21-06-08.408Z.txt…

bobofruit · September 27, 2022, 1:33am

Disable condition feature in automations should not be used, because it leads to wrong results.
This should be corrected as soon as possible.
Possible the wrong assumption was made in the code that a disabled condition could be considered as PASSED.
This is a very serious error.

The error has been confirmed now but has been around for a while.

Sparty117 · September 27, 2022, 4:23am

Does anyone know when the Broadlink integration updates will be included? This manufacturer is constantly changing their device IDs. The Github repo is updated but it is not included in any of these updates.

Robshot · September 27, 2022, 7:47am

Lets hope it get fixed soon as I also have like 30-40 shellies but I’m still on 2022.9.0.
That is the reason why I always wait a month to upgrade to not have these issues, not specially for me but to have the wife approval positive

nickrout · September 27, 2022, 9:37am

Please enlarge on this. What wrong results are you seeing?

Have you submitted a PR?

English please?

Confirmed by whom? Where?

bobofruit · September 27, 2022, 10:29am

@nicrout

Try to create this simple automation. Disable any condition and you will get always TRUE result in OR function. Even if it is not true in real.

github.com/home-assistant/core

Machine of states bug when condition disable feature in automations is used

opened 12:26AM - 26 Sep 22 UTC

bobofruit1970

### The problem Disable feature in conditions does not work as it should for …OR CONDITION. For example try create simple automation. It checks if any of two temperatures in my room is below threshold: " mode: single trigger: - platform: time_pattern seconds: /10 condition: - condition: or conditions: - condition: numeric_state entity_id: sensor.0x158d0003d4238f_temperature below: 0 - condition: numeric_state entity_id: sensor.0x158d0003d4238g_temperature below: 1 action: [] " Temperature in my room is 25 C degrees. So both conditions are false and actions are not executed. Such above automation works good. But when You try to disable one condition (for example second condition) like below it should still not be executed too: " mode: single trigger: - platform: time_pattern seconds: /10 condition: - condition: or conditions: - condition: numeric_state entity_id: sensor.0x158d0003d4238f_temperature below: 0 - condition: numeric_state entity_id: sensor.0x158d0003d4238f_temperature below: 1 enabled: false action: [] " When You use disable condition feature it executes actions. It performs actions even though the first enabled condition is still not met. If you use the disable feature in conditions then the machine of states automatically assumes that the OR function is TRUE. This is wrong. It should not work like this. Disabled by user condition should not be taken to analyze in any purpose!!!!!!. Only enabled conditions should be analyzed by machine of states. This is a BUG The same condition in my example shows different results: When I try to test enabled condition it say CONDITON DID NOT PASS When I try to test disabled condition it always say CONDITON PASSES It is incorrect to assume that a disabled condition is treated as a CONDITION PASSED. In the case of using the OR function, it leads to wrong decisions of the state machine because then it assumes the OR function is always passed. It shouldn't be like that. Only enabled conditions should be analyzed by machine of states!!!! Disable feature in conditions is very useful but it should be fixed for OR condition/function. ### What version of Home Assistant Core has the issue? Home Assistant 2022.9.6 ### What was the last working version of Home Assistant Core? Do not know ### What type of installation are you running? Home Assistant Supervised ### Integration causing the issue _No response_ ### Link to integration documentation on our website _No response_ ### Diagnostics information _No response_ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

viper80 · September 27, 2022, 11:28am

AleksandrBraun can you share your HA config ?

nickrout · September 27, 2022, 7:29pm

Ok, fix your code in your issue and you may get some attention.

ESe_ELe · October 9, 2022, 2:09pm

Hi Petro, I have the same problem as Gabriel.
I am using the last version HA 2022.10.1
How could intall it?

petro · October 9, 2022, 2:10pm

You’ve already installed it. Are you asking how to uninstall?

ESe_ELe · October 9, 2022, 2:17pm

No. Leds strips doesn’t work.

If I use the configuration.yaml configuration

light:

platform: flux_led
devices:
192.168.0.XX:
name: TiraLed

appear this error

Platform error light.flux_led - cannot import name ‘ATTR_WHITE_VALUE’ from ‘homeassistant.components.light’ (/usr/src/homeassistant/homeassistant/components/light/init.py)

And if I try to use the integration appears:

“This integration does not support configuration via the UI”

So I don´t know how to configure the flux_led platform.

Could you help me?

petro · October 9, 2022, 2:20pm

Don’t use the custom integration for flux_led. That error only appears if you have the custom integration for flux_led installed.

I.e. Uninstall the flux_led custom integration or write up an issue against the custom flux_led integration here

ESe_ELe · October 9, 2022, 2:44pm

Ok. I try to uninstall uninstall custom integration and use the HA integration

Thanks a lot for you help.