search

romedtino / simple-wyze-vac

Home Assistant Custom Component for Wyze Vacuum
49 stars 8 forks source link

Configuration validation won't let me restart #5

Closed codypet closed 2 years ago

codypet commented 2 years ago

Configuration validation just spools and I can't restart after installing application and setting up the config file.

I'm running core-2021.9.6

When I tried a hard restart of HA my google devices disconnected. They reappeared after I deleted the integration. The vacuum entities never showed up.

This is the error I get in my for my nest and when I restart. https://hastebin.com/efasulezeq

romedtino commented 2 years ago

The process should be: install it through HACS then in your Home Assistant configuration.yaml you add an entry like

simple_wyze_vac:
  username: myEmail4Wyze@email.com
  password: myWyzePassword

Make sure to hit that check configuration button image

and a vacuum entity should show up on reboot.

I don't believe this integration interferes or connects to anything google nest related so I'm not sure what to make of your log

codypet commented 2 years ago

It appears to have something to do with the libraries. It happens with the other Wyze Vac integration as well. https://github.com/alanjames1987/Wyze-HA/issues/11

romedtino commented 2 years ago

Oh I see. Interesting bug. Did you try installing the Wyze-HA update with a newere protobuf version declared to see if that fixes it?

codypet commented 2 years ago

So I'm running this on VirtualBox and for some reason when I run it, it doesn't change anything. I'm not sure if I'm installing the latest protobuf wrong or what? When I try to ping it before updating, it says there's no version at all.

romedtino commented 2 years ago

Hmm, is it virtual box with a docker container of HA? If I check my copy of home assistant on docker, it shows protobuf at 3.10.0 image

Before wyze-sdk updated to fix the login issue, I had recommended people to manually remote into their HA instance and change a line of code in the wyze-sdk instance. Perhaps you can do something similar to update protobuf?

Remote into your HA docker VM/instance and do a pip install protobuf==3.13.0 ?

Note: If that works, you'd have to make sure to update protobuf every time Home Assistant roles out an update. Whenever an update comes in, it repulls the dependencies

codypet commented 2 years ago

Yea for some reason my VM doesn't recognize those commands. Its like its speaking a whole different language in VM. I don't know why I can't get that info.

romedtino commented 2 years ago

I've added the dependency to protobuf as stated in the issue mentioned above. Please let me know if you're still having issues, if not I'll probably close this issue in a few days :)