wishy

Python 3.12 for Home Assistant Core
Admittedly there are only 10,000 of us, but it seems a little oversight not to include details on Python for Home Assistant Core (advanced install) users.
Presumably 3.11 is deprecated and we have 6 months to move?

2 replies

balloob Founder of Home Assistant

As a user of Home Assistant Core installation you are yourself responsible for the Python installation. We don’t know how Python is installed so cannot include details for that.

1 reply

wishy

Of course. But the release notes don’t make it clear when 3.11 is deprecated

3 replies

mateuszdrab

I don’t want to sound like I’m ranting, however I’m not sure I’m happy with the automatic token expiration enforcement.

I appreciate all the amazing stuff that are implemented in HA but certain decisions irritate me.

For example:

• my dad doesn’t use the app much if at all but it is needed to have the sensors update - with this, it sounds like it will soon stop working.
• I have Home Assistant logged into some devices that I don’t use as I have 2 homes, it’s nice to have my session working when I return which currently is the case even if I’m away for a year.

I understand the security concerns, which is why I think 90 days is a good default, but should be customizable.

At least if oauth was supported, AAD would take care of the re-authentication. Unfortunately, all the requests to add oauth/SAML support which actually would be a workaround to the issue below have been ignored.

I would appreciate customizability of the expiration feature.

9 replies

balloob Founder of Home Assistant

Ah check. It is 3 months and 2023.4 will require the new Python version.

GSzabados

Which Tapo devices are supported now? The Tapo range is quite wide, cameras, sockets, bulbs, vacuum cleaners, Hub with sensors and cameras, etc. Probably around 100 different devices split between regions.

Is there any plans to add cameras?

@JurajNyiri, do you have any plans to merge in?

2 replies

balloob Founder of Home Assistant

See the documentation for a list of supported devices.

2 replies

GSzabados

Thanks! I realised that at the end, but first I clicked on the Tapo link, which is quite empty regarding devices.

2 replies

DancingTable52

I agree. Or let us select a device and exclude it from being logged out. My wife only uses the app for notifications and location data. Never opens it.

4 replies

finity Regular

I agree. We should have a customizable option for certain devices to stay logged in as long as we want.

Exactly my situation too.

1 reply

Duke_box

Ditto - I have the same scenario

spr0k3t

Lots of great stuff in this release. Testing it out now. Cheers to all involved with this one.

inverse.chi

For more context on the answer you already have of 2023.4. It’s documented in their ADR process.

See: https://github.com/home-assistant/architecture/blob/8631a749058299f2b309226e1afd508ae5c12cc2/adr/0020-minimum-supported-python-version.md

lboue

Thanks for Python Matter server 5.5.0.

sesame26

will the proximity integration also still have a proximity.home entity where you can add tracker entities of several family members?

2 replies

nwithan8

That Google Generative AI example seems like a real privacy violation. Personally, I would advise against sending unscreened photos from any of your cameras up to a cloud LLM…

1 reply

allard77

I second that. Is there a way to ‘fake’ activity and put that in an automation for selected clients? The beta testing period was only a week, otherwise I might have picked up on this

1 reply

nwithan8

Wouldn’t the mobile app on the phone pinging home with GPS data count as “activity” to keep the session valid?

2 replies

daywalker03

I think a lot of people don’t have it running in the background on their phones, so it wouldn’t automatically.

DancingTable52

What about mobile apps on the iPad? They don’t leave the house so don’t update location. But I still need the sensor data AND notifications to work to them? I guess what counts as activity. Is background sensor update like updating battery level count as activity? If so - great. If not - less great.

1 reply

dshokouhi Amazing contributor

if your companion app is sending sensor data then the token is being used and considered active, you don’t have to open the app for it to be active. If you dont have any sensors enabled then yes you may be considered inactive.

Edwin_D Regular

Same thoughts. I hate the Tado app for not keeping the session alive. No one opens it, but geofencing is on. Users are constantly loggged out keeping them cold. For now it was Home Assistant to the rescue, but I fear that ends too.

Home assistant is intended to work in the background, automating stuff. As nice as the companion app is, I’m the only one opening it regularly.

bric

Sending pictures to Google’s AI is only as much of a privacy violation as buying a nest cam and paying for their AI recognition features. Most Doorbells do something like that these days, as unfortunate as it is we just need to have an expectation that anytime you’re at anyone else’s house and see a camera, it just isn’t going to be private.

Duke_box

According to the info in breaking changes we should use a long lived token (10yrs).

I would like someone, a dev or an expert, to explain how I use this to keep my phone browser logged in and my HA companion app logged in.
Maybe I am being dumb but I have a few of these tokens for vscode and Alexa etc. But a guide to how to use these for the companion app and a browser session would be good.

And I can see the temporary ones for the relevant mobile devices.
So will the temporary ones self destruct after 90 days?

mib1185 Great contributor

this should answer your question at all: 2024.2: More voice, more icons, more integrations, more... everything! - Home Assistant

1 reply

davidmtml

I can’t reconfigure my Tuya Integration after this update. I get to the first page and enter my User Code. Then I click on ‘Submit’ on the next screen where it’s then supposed to pop up the QR code to scan, but instead I just get an error that says unable to login. I double-checked my User Code and tried it again with the same error.

5 replies

mib1185 Great contributor

about the refresh token expiration

as long as any (authenticated and valid) communication with HA is done, the refresh token is considered as used. Some examples are updating sensors or receiving notifications in the companion app or keep a browser open showing the HA UI (as long as the browser did not freeze )

3 replies

TheFes

The proximity.home entity will be imported, but it’s depreciated. Sensor entities are created with the same information as the proximity entity has, but also sensors for each tracked device are created.

1 reply

Nick4 Regular

Just installed this release; went smooth, as usually.
Thanks guys!

I’m watching the live stream (delayed) and only noticed now that it’s possible to rename the headers of actions, conditions and actions…
Nice feature though to be able to move things around right away!

About renaming: sometimes it can be useful (in my opinion) to keep the current text of the header + add some comment.
Would it be possible to, instead of showing the current header text faded out, to keep it available and if needed just delete/cut and add additional text?

@synesthesiam (voice Mike): well done to make the assist feedback more meaningful!

Duke_box

Good to know.

How do you use the long lived token though?

alex21

same here - QR code does not display. Instead error is

5 replies

naijaping

There is problem with the new Tuya app re authentication. the last part after inputing the user security code did not show QR-Code instead it shows Invalid hex color: rgba(43,55,78,1).

2 replies

tom_l

Should the time and date integration have been imported?

It has not for me. No repairs generated either. Still using YAML.

1 reply

sesame26

I did read that first actually but maybe is my shortcoming but i not find the answer on my question there, maybe the format is wrong, i am wondering if you still will be able to create a proximity sensor using the proximity (distance) to home from device trackers of several different persons.

Similar as I have now a proximity.home entity that uses trackers of my phone and aswell of my wife and kids phones

1 reply

poudenes

Will the 90days expiring for tokens have some impact for the Alexa Integration? Or does Alexa connect every day so the token will stay alive?

2 replies

samtygier

Now that there is myUplink in core, should elupus/hass_nibe users switch? Will everything still work? Is there a way to migrate the history across?

1 reply

sesame26

Ok, thank you!

Ernst

Although not mentioned in the release notes, we also added several Xiaomi BLE buttons and wall switches in this release (More specifically, the following devices: RTCGQ02LM, JTYJGD03MI, SJWS01LM, K9BB-1BTN, XMWXKG01LM, K9BB-1BTN, K9B-1BTN, K9B-2BTN, K9B-3BTN, MS1BB(MI), XMWXKG01YL, YLAI003). Button clicks are recorded as events.

Jtmoore81

I had to go through the integration site on the home assistant website and add to my instance for the qr to show.

Although this is the first time using the tuya app the fan entity is greyed out. The light entity and countdown entity are active and work as expected.

davidmtml

Interesting. That’s a different error than I got.

I rolled back to 2023.6 without issue.

DancingTable52

The matter updates, although theoretically good, seem to not be working properly for me. Not the biggest deal, didn’t have access before anyway, but I cannot ping matter devices, it fails every time even if I can control the device no problem, and I also cannot share the device. It either fails, or loads indefinitely. Rest of the update from what I’ve tried seems pretty great though.

Just kidding. Matter server update fixed that (sorta. Some devices don’t give me the option to share devices anymore, but the ones that do have that option work)

iSteve-O

I was hoping February was raspberry pi 5 month. Oh well.

2 replies

mib1185 Great contributor

tl;dr yes

the proximity entity itself (proximity.*) is now deprecated, but superseded by sensor entities. Further the configuration is now available via the UI, no YAML configuration needed anymore.

1 reply

Blueman2

Thanks @balloob for adding the ability to export history data to CSV!!! I have been wanting that for years. HUGE new feature.

Hedda

Do you think Nabu Casa can convince many more Zigbee device manufacturers to provide their Zigbee device OTA firmware images publicly to third-party Zigbee gateway applications like Home Assistent?

If not then users need to manually upload firmware images collected by unofficial means:

Hoping for a larger open-letter type campaign about making both Zigbee and Z-Wave OTA device firmware available to all!

1 reply

dougiteixeira

That’s a problem with what you’re using. Change to the Home Assistant theme and repeat the authentication steps and the integration will work.

2 replies

asbachb

Anyone has problems with the update? I can trigger the install. It seems to be installed. But the ui resets and ask me if it should install the update…

neliss

Loving the added icons for all services and service parameters! Must have been quite some work, but it’s a great result.

dougiteixeira

mattbrad2

Dear God, please this! Between my wife and father-in-law, I really need them signed in indefinitely.

1 reply

domramsey

Same issue with Tuya as others have reported, setup produces an “Invalid Hex Color” error that can’t be dismissed. Only fix for me was to restore HA entirely from a backup.

1 reply

Piggyback

Thank you for the tip!! That worked!

daywalker03

It’s been said that if the app is running in the background, the access token won’t expire.

1 reply

Duke_box

Don’t you use a long lived access token for AMP. I thought that was part of the setup for this custom integration. If so, I believe you won’t have a problem. Or am I misunderstanding your question?

1 reply

petro Great contributor

refresh the page or open a new window… no need to restart. Also, according to another user, it’s because of your theme. Revert to the default HA theme and you should be good to go

petro Great contributor

Any communication between HA and Alexa will reauth. Even if you restart HA.

tom_l

If it is sending location data it is using the token. So they won’t be logged out.

Kedryn

Tuya integration not display qrcode

AND
i created 1 prox sensor with 4 personas and it made 5 different prox sensors with same name

boheme61

I can inform you that even P115 , with Current-Power/Todays-Total-kWh/ and Total-kWh , is supported.
( I had 7 Plugs and 3 light-strips popping up)( PS: Sorry, i had to Ignore all, after all i was only “testing” )

However , i’ve still havent found support anywhere for ( local-polling ) with Tapo (hub) H200, + T100( motion-sensor) +T310(temp-sensor), outstanding devices which communicate over 866MHz.

It’s very high on my wish-list

3 replies

tonicb

I do not have the matter diagnostics and actions, even the “share device” is not there, only “download diagnostics” and the three dots only shows “remove”, same as before the update

1 reply

DancingTable52

Share device doesn’t work as far as I can tell anyway.

Edit: just kidding. Matter server update fixed it

1 reply

SamJongenelen

Yeah but Google actively tries to kill apps that havent been opened in a while. Sounds like a good idea to let tokens be indefinate or a year

Mariusthvdb

Raised that same question in beta. It’s not causing a repair because yaml is not deprecated.

For the same reason they are not imported.

You can delete yaml and add them in Ui in a snap though

boheme61

Never thought of such a feature, and i have noone to share with anyway

JurajNyiri

No, I plan to keep it as a custom integration.

mib1185 Great contributor

this is on purpose to differentiate between proximity configuration with same monitored zone. you can easily rename the created service to your needs.
btw why did you create 4 proximity configuration for the same zone? do you want to track different groups of persons or use different “ignored zone” settings?

mateuszdrab

Alrighty, so scenario of my dad’s phone is handled and should not be a concern.

This would just leave me with the odd ‘laptop I’ve not used in a while’ case. I guess I can live with it but I’d love to be able to customize the token expiration.

Personally, I’d set it to a year - I know, quite long.

In terms of using long lived tokens, I guess that would also be an option but I’m not aware of how to achieve authentication in the app/web UI with an already existing token.

1 reply

phidauex

Just wanted to say I’m loving the update! Drag and drop, CSV export from history, and many other long-term wishlist items coming all at once. Thanks!

boheme61

You can have more than 1 long lived token ! , Maybe you can create 1 for this purpose

alex21

Awesome - changing the theme resolved the problem.

Thank you.

aigarius

For me the time integration stopped working on upgrade without any repair options. Had to read the changelog and put 2+2 together that time&date are now configurable via UI. Only after I added the time integration via the UI did my automations with a time trigger started working again. Not great. Also no error message anywhere in the automations that my time-based automation does not have an integration active for it to trigger from.

bkr1969

Still can’t authenticate Tuya even after changing theme. Where is the fracking QR code I’m supposed to scan?

sesame26

Thanks for your explanation, all clear now!

PapaLanc

There is no code for tuya integration in Smart Life app

circa1665

I’m getting this repair warning since upgrading:

The `beat` Time & Date sensor is being removed

This stops working in version 2024.7.0. Please address before upgrading.

Please remove the `beat` key from the `display_options` for the time_date entry in your configuration.yaml file and restart Home Assistant to fix this issue.

I can see that this is due to this change: Deprecate 'beat' display option in Time & Date by emontnemery · Pull Request #106871 · home-assistant/core · GitHub

I don’t what ‘beat’ is, I’m not seeing a ‘time_date’ entry in my configuration.yaml and I don’t know what is being referred to by ‘display_options’

2 replies

bkr1969

The only way I could get the Tuya QR was to delete the integration and re-install.

ValMarDav

Hi, Look in your sensors.yaml file.

2 replies

circa1665

Thank you!

spdustin

After you try to add the updated Tuya integration and get an empty screen where the QR code should be, restart Home Assistant and try to add the integration again. It should work then.

(This is assuming you’re not using a custom theme. If you are, reset back to the default Home Assistant theme, restart, and re-add the integration)

1 reply

Lexorius

Hi, i was shocked to read that message, because i use the swatch beats on my awtrix light and on some display projects.

what are the cause to remove the (swatch internet) beats option ?

i would also love to have a (star trek) star Time option. currently i use a helper template with {{ ((as_timestamp(states(‘sensor.date_time_iso’)) - as_timestamp(“2318-07-15 00:12:00.0-05:00”)) / 34367.0564 ) | round(1,‘floor’) | string }}

greetings from germany
Thomas

2 replies

jonathanp

Now Tuya says the QR Code has expired and to refresh it. How does one do that?

1 reply

PapaLanc

I restored from backup now I get access denied in file editor for confi…yaml

frenck

Hit submit, the authentication will fail, and HA will request a new one immediately.

1 reply

Kedryn

No i added 1 prox sensor, with 4 people
and it created 4 (or 5, dont remember) different prox sensors

i delete all, made 1 with 1 person, then added other 3
and it worked

avd706

Any month is raspberry pi month… If you can get one.

MariuszBit

Hi guys! May I ask what happened to mqtt.publish in 2024.2? All of the sudden bunch of my automations gone all mad, didn’t see that coming from the version announcement blog post

Thanks!

1 reply

teprrr

I have a H100 and a T315 working outside homeassistant and I would guess that they likely work very similarly to H200&T310, so support for those is coming in the future. Adding support for other hub-connected sensor devices like those motion sensors should also be doable with the caveat that they do not push updates but need polling and will thus not instant when it comes to automations…

Cameras and other devices like vacuums will require some more time & effort, so any help to extend the support is very welcome

1 reply

teprrr

The list of devices that are known to work are listed on the linked tplink integration page: TP-Link Smart Home - Home Assistant - The list is not exhaustive, but basic controls for any device from the listed categories (plugs, wall switches, bulbs, …) should work right now.

michaelwacey

I just installed 2024.2.0 and found this issue in my logs. How do I report it?

Logger: pychromecast.dial
Source: components/cast/helpers.py:68
First occurred: 7:58:40 PM (1 occurrences)
Last logged: 7:58:40 PM

Failed to determine cast type for host () (services:{ServiceInfo(type=‘mdns’, data=‘C4A-fb1cf26082eb8232401f205015226256._googlecast._tcp.local.’)})

1 reply

contagon

It seems there are a few new options for the proximity sensor that I can’t seem to find in the documentation.

Could anyone explain to me what the “ignored zones” and “tolerance” settings do? Or perhaps link me to whatever site I’m missing here?

EDIT: Nvm, it appears to be in the old documentation, so I got the info from there. Not sure why it’s been removed though?

magixnetworks

My HP iLO integration no longer works since installing this version

2 replies

phidauex

Same here, I’m getting this error:

AttributeError: module 'ssl' has no attribute 'wrap_socket'

It appears that this is a python deprecation in 3.12, the URL below gives an explanation and suggests a fix. I’ll submit an issue to the maintainer if someone hasn’t beaten me to it. EDIT: someone beat me to it, but I added some detail. Shouldn’t be too hard of a fix.

Remove the ssl.wrap_socket() function, deprecated in Python 3.7: instead, create a ssl.SSLContext object and call its ssl.SSLContext.wrap_socket method. Any package that still uses ssl.wrap_socket() is broken and insecure. The function neither sends a SNI TLS extension nor validates server hostname. Code is subject to CWE-295: Improper Certificate Validation. (Contributed by Victor Stinner in gh-94199.)

malikai3k

I have the adguard addon i had to disable protection in it. then it showed the code for the tuya auth not sure if it was just a coincidence but the code didn’t show after multiple refreshes until i disabled it

Krispkiwi

Really hoping the ability to use custom shapes for zones comes soon, the circles can result in false positives.

2 replies

Chris8837

For the ECOVACS update I was using this and it worked fine just clunky as it’s older.

Is this merged as my Deebot is recognized if I use the integration and login, but I can’t control my Deebot 901. It shows unknown.

Any thoughts here?

matthewcbyington

Most likely not. A lot of OSes use point and radius for GPS. I think it’s unlikely custom shapes will happen.

Matt

2 replies

Krispkiwi

I’ve asked in the HA discord before, people said someone is working on it after the feature request got a few votes. Not sure about others but i sure have my HA ping as in a zone when I’m just driving past it because I can’t get the whole thing in the circle without going out onto the street a bit. It’s a small thing but frustrating for location based automations.

3 replies

Steve61

I’ve just tried to update to 2024.2 from 2024.1.5 and it won’t update. I had skipped 2024.1.6 because of the Omada issue.

I have now tried four times. I always see the Z2MQTT warnings so that does not seem to be the issue. I have restarted twice - nothin"

Log:

24-02-08 13:53:51 INFO (MainThread) [supervisor.backups.manager] Creating partial backup with slug b1713763 completed
24-02-08 13:53:51 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2024.2.0
24-02-08 13:53:51 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2024.1.5 to ghcr.io/home-assistant/qemux86-64-homeassistant:2024.2.0
24-02-08 13:53:51 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2024.2.0.
24-02-08 13:54:34 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:54:34 WARNING (MainThread) [supervisor.addons.options] Option 'external_converters' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:54:34 WARNING (MainThread) [supervisor.addons.options] Option 'devices' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:54:34 WARNING (MainThread) [supervisor.addons.options] Option 'groups' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:54:34 WARNING (MainThread) [supervisor.addons.options] Option 'homeassistant' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:54:34 WARNING (MainThread) [supervisor.addons.options] Option 'permit_join' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:54:34 WARNING (MainThread) [supervisor.addons.options] Option 'advanced' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:54:34 WARNING (MainThread) [supervisor.addons.options] Option 'device_options' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:54:34 WARNING (MainThread) [supervisor.addons.options] Option 'blocklist' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:54:34 WARNING (MainThread) [supervisor.addons.options] Option 'passlist' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:54:34 WARNING (MainThread) [supervisor.addons.options] Option 'queue' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:54:34 WARNING (MainThread) [supervisor.addons.options] Option 'frontend' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:54:34 WARNING (MainThread) [supervisor.addons.options] Option 'experimental' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:54:34 WARNING (MainThread) [supervisor.addons.options] Option 'availability' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:56:31 INFO (SyncWorker_4) [supervisor.docker.manager] Stopping homeassistant application
24-02-08 13:56:41 INFO (SyncWorker_4) [supervisor.docker.manager] Cleaning homeassistant application
24-02-08 13:56:41 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
24-02-08 13:56:41 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2024.2.0
24-02-08 13:56:41 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
24-02-08 13:56:46 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!
24-02-08 13:56:46 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!
24-02-08 13:56:46 INFO (MainThread) [supervisor.homeassistant.core] A backup of the logfile is stored in /config/home-assistant-rollback.log
24-02-08 13:56:46 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2024.1.5
24-02-08 13:56:46 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2024.2.0 to ghcr.io/home-assistant/qemux86-64-homeassistant:2024.1.5
24-02-08 13:56:46 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2024.1.5.
24-02-08 13:56:47 INFO (SyncWorker_6) [supervisor.docker.manager] Cleaning homeassistant application
24-02-08 13:56:47 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
24-02-08 13:56:47 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2024.1.5
24-02-08 13:56:47 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
24-02-08 13:56:50 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
24-02-08 13:56:50 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
24-02-08 13:56:52 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
24-02-08 13:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/thomasmauerer/hassio-addons repository
24-02-08 13:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/vk2him/Enphase-Envoy-mqtt-json repository
24-02-08 13:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/zigbee2mqtt/hassio-zigbee2mqtt repository
24-02-08 13:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/daemongloom/rtl_433-hass-addons repository
24-02-08 13:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/adamoutler/mqtt-explorer repository
24-02-08 13:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repository
24-02-08 13:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/sabeechen/hassio-google-drive-backup repository
24-02-08 13:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
24-02-08 13:56:52 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
24-02-08 13:56:53 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to NOT_RUNNING
24-02-08 13:56:55 INFO (MainThread) [supervisor.store] Loading add-ons from store: 87 all - 0 new - 0 remove
24-02-08 13:56:55 INFO (MainThread) [supervisor.store] Loading add-ons from store: 87 all - 0 new - 0 remove
24-02-08 13:56:55 WARNING (MainThread) [supervisor.addons.options] Unknown option 'base_topic' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:56:55 WARNING (MainThread) [supervisor.addons.options] Option 'external_converters' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:56:55 WARNING (MainThread) [supervisor.addons.options] Option 'devices' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:56:55 WARNING (MainThread) [supervisor.addons.options] Option 'groups' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:56:55 WARNING (MainThread) [supervisor.addons.options] Option 'homeassistant' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:56:55 WARNING (MainThread) [supervisor.addons.options] Option 'permit_join' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:56:55 WARNING (MainThread) [supervisor.addons.options] Option 'advanced' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:56:55 WARNING (MainThread) [supervisor.addons.options] Option 'device_options' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:56:55 WARNING (MainThread) [supervisor.addons.options] Option 'blocklist' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:56:55 WARNING (MainThread) [supervisor.addons.options] Option 'passlist' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:56:55 WARNING (MainThread) [supervisor.addons.options] Option 'queue' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:56:55 WARNING (MainThread) [supervisor.addons.options] Option 'frontend' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:56:55 WARNING (MainThread) [supervisor.addons.options] Option 'experimental' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:56:55 WARNING (MainThread) [supervisor.addons.options] Option 'availability' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-08 13:57:20 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqtt-user'
24-02-08 13:57:20 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache
24-02-08 13:57:34 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to RUNNING
24-02-08 13:57:34 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
24-02-08 13:57:34 INFO (MainThread) [supervisor.homeassistant.core] Successfully started Home Assistant 2024.1.5
24-02-08 13:57:34 INFO (SyncWorker_5) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/qemux86-64-homeassistant:2024.2.0']

3 replies

don-reba

Really stoked to hear about the new Matter diagnostic tools and data export! I am just starting using Home Assistant, and these were the two areas that most stood out to me as needing improvement.

matthewcbyington

One idea would be to use a short “for” in the automation so that you have to be in the zone for say 30 seconds or 1 minute or something before it’ll trigger the automation.

Obviously if you want immediate notification (such as when arriving home) this might not be tenable.

Matt

1 reply