Skip to content
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.

Integration broken after HA update. #156

Closed
hmjgriffon1 opened this issue Aug 3, 2023 · 13 comments
Closed

Integration broken after HA update. #156

hmjgriffon1 opened this issue Aug 3, 2023 · 13 comments

Comments

@hmjgriffon1
Copy link

hmjgriffon1 commented Aug 3, 2023

Upgraded to the following:
Home Assistant 2023.8.0
Supervisor 2023.07.1
Operating System 10.4
Frontend 20230802.0 - latest

Integration no longer works, I get these errors in the HA log.

Logger: homeassistant.components.switch
Source: helpers/entity_platform.py:624
Integration: Switch (documentation, issues)
First occurred: 7:54:20 AM (4 occurrences)
Last logged: 7:54:20 AM

Ignoring invalid device info: Invalid device info {'default_manufacturer': 'VeSync', 'identifiers': {('vesync', 'vsaqfbd52134d318cb56214b183a69aa')}, 'model': 'LAP-C601S-WUS', 'name': 'Master Bedroom Levoit Air Purifier', 'sw_version': None} for 'vesync' config entry: device info needs to either describe a device, link to existing device or provide extra information.
Ignoring invalid device info: Invalid device info {'default_manufacturer': 'VeSync', 'identifiers': {('vesync', 'vsaq3782ffc40cd8f5457a1fd7956d79')}, 'model': 'LAP-C601S-WUS', 'name': 'Living Room Levoit Air Purifier', 'sw_version': None} for 'vesync' config entry: device info needs to either describe a device, link to existing device or provide extra information.

@RobertD502
Copy link
Contributor

Are you sure this is for the VeSync integration? These look like entities for a Tempest weather station?

@modelstudent101
Copy link

They posted the wrong logs, but I was getting an error after the update that the device did not exist. After removing the device via the integration, I restarted, and re-added my account; the device was not created (300S Humidifer), but the entities were.

@NickM-27
Copy link

NickM-27 commented Aug 4, 2023

It is a problem, and #154 fixed it

@modelstudent101
Copy link

Awesome, thank you for the alert.

@hmjgriffon1 — if you want an easy way to add pull requests to a custom component, check out this repository:
Repo: /alandtse/pr_custom_component

Be extra careful when adding pull requests.

@hmjgriffon1
Copy link
Author

Sorry guys, I don't know how I grabbed the wrong logs. I will look at the link, I rebooted and mine is working again but only have entities.

@hmjgriffon1
Copy link
Author

so is that link an update that will come out?

@RobertD502
Copy link
Contributor

so is that link an update that will come out?

No, it is a pull requests that needs to be merged by the owner of this repo prior to creating a new release in order for it to be part of the next release.

@hmjgriffon1
Copy link
Author

so is that link an update that will come out?

No, it is a pull requests that needs to be merged by the owner of this repo prior to creating a new release in order for it to be part of the next release.

thought so, thank you sir, and I updated my post with the correct log entry lol.

@vlebourl
Copy link
Owner

vlebourl commented Aug 5, 2023

This will be out quickly!
Thanks for the report and the fix.

@vlebourl vlebourl closed this as completed Aug 5, 2023
@cagnulein
Copy link

is this on the latest HASS version? i just updated HASS but the error still here :(

@cagnulein
Copy link

@vlebourl this my error with the latest HASS

vesync: Not adding entity with invalid device info: Invalid device info {'default_manufacturer': 'VeSync', 'identifiers': {('vesync', 'vsaq73b8946141fd9fb15db29947e059')}, 'model': 'Core400S', 'name': 'Candeggiami', 'sw_version': None} for 'vesync' config entry: device info needs to either describe a device, link to existing device or provide extra information.

@vlebourl
Copy link
Owner

'default_manufacturer': 'VeSync'

I don't think you are using the latest version as this string isn't in the code anymore since version 1.0.2.

@cagnulein
Copy link

sorry @vlebourl all fixed now, you were right: my HACS didn't prompt me for an update of your component. I had to remove the folder and reinstall it. Thanks for your quick support!

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

No branches or pull requests

6 participants