Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HA 2024.2.x :The 'schema' option is deprecated, please remove it from your configuration #517

Open
memphi2 opened this issue Feb 15, 2024 · 14 comments

Comments

@memphi2
Copy link

memphi2 commented Feb 15, 2024

v0.10.10 causes the following warning when starting HA > 2024.1:

Logger: homeassistant.components.mqtt.vacuum
Source: helpers/config_validation.py:917
Integration: MQTT (documentation, issues)
First occurred: 20:39:34 (1 occurrences)
Last logged: 20:39:34
The 'schema' option is deprecated, please remove it from your configuration

@Krispkiwi
Copy link

Krispkiwi commented Feb 27, 2024

I'm also getting this @rand256

@goodlucknow
Copy link

receiving also. changes on homeassistant end which is unfortunate as Valetudo RE functionally working perfectly.
link to changes from the release notes, hopefully helpful.
it looks like 6 months until the actual breaking change, this is early warning.

@damousys
Copy link

damousys commented Apr 3, 2024

Any update on this ?

@rand256
Copy link
Owner

rand256 commented Jun 9, 2024

Well, as far as I understand from the links provided, the actual breaking change is they're dropping the support of legacy schema which we don't use, while by some reason they start spamming the logs when schema is set to state which is not going to be unsupported and actually is a default value, right? Then it's a very "useful" warning if you ask me... So all we need to do is to remove the schema altogether and that's it?

I'm attaching the binary which should be completely the same with the latest version, just without the schema field in mqtt autoconf payload. Could someone confirm this is enough to fix this terrifying issue?

valetudo240609.tar.gz

@Krispkiwi
Copy link

Apologies Rand, I've been away. Has no one tested this?

@rand256
Copy link
Owner

rand256 commented Jul 8, 2024

I have no idea. Even if someone's did test it, they didn't bother to write about it.

@sca075
Copy link

sca075 commented Aug 6, 2024

@rand256 I would test it but I would need the pkg file, can I use the the old one and just replace the binary in it?

@pidator
Copy link
Contributor

pidator commented Aug 6, 2024

You don't need to completely flash the whole firmware new (.pkg) just download the provided binary, stop the valetudo service on your robot and replace the binary. Then restart the valetudo service again (or do a system reboot, both way works and will start the new binary)

@sca075
Copy link

sca075 commented Aug 6, 2024

@pidator Thanks, I honestly taught (as the vacuum can load the pkg with the md5) well would be more easy. No plan then to beta release this patch for example?

@pidator
Copy link
Contributor

pidator commented Aug 6, 2024

Oh, there's even a wiki entry for the updating process Link. Perhaps this helps :)

@sca075
Copy link

sca075 commented Aug 6, 2024

Will need to setup the SHH but this isn't a problem thanks for the link :)

@memphi2
Copy link
Author

memphi2 commented Aug 8, 2024

I have just tested it. The message in HA has disappeared with the new package. Thank you very much!

@sca075
Copy link

sca075 commented Aug 26, 2024

Confirmed also from my side, installed just some minute ago, the procedure that @pidator provided is really easy thanks for that that @rand256.

@goodlucknow
Copy link

@rand256 have this running on my V1 now(had lost SSH access for a time) and errors in homeassistant appear to be resolved. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants