#VeSync device suddenly result “unavailable”

1 messages · Page 1 of 1 (latest)

jade rock
#

Hello everyone.

I’m an absolute beginner with Home Assistant — I only discovered it yesterday.

Let me briefly describe my problem.

Yesterday, I installed HA on my small Linux server using Docker Compose.

My only goal was to manage a VeSync switch, model BSD60+.

First, I downloaded the app from the Play Store on my Android smartphone, created an account, and successfully added and tested the device.

Then, I added the same VeSync account in HA, which immediately recognized the device as well.

I tested the switch, and the lamp connected to it turned on and off successfully.

Today, I decided to continue setting up other devices, but when I went to test the VeSync switch again, it showed as “unavailable.”

I verified that it still worked in the Android app, that the Wi-Fi signal was fine, restarted the router, unplugged and plugged the switch, restarted HA, restarted the server, removed and re-added the VeSync account in HA — none of these actions changed anything.

Now, in fact, whenever I re-add the VeSync account, the device immediately appears as “unavailable.”

What could have happened?

tidal frost
#

switch is connected to a 2.4ghz only network? Most IoT devices dont like 5ghz..

jade rock
#

yes, 2.4ghz

#

my router has both

tidal frost
#

make sure device is not switching between 2.4 and 5..

#

and check network signal/channel

#

2.4

jade rock
#

The companion app, during the setup process on the smartphone, explicitly required that type of connection.

tidal frost
#

for companion app yes, not for switch though

jade rock
#

I don’t think I can interface directly with the switch without the companion app that configured it the first time.

tidal frost
#

check router settings, most routers allow you to define the way a device gets the right band. Something like device X only connects to 2.4ghz

jade rock
#

Ok, I'm checking.

#

It appears active and connected to 2.4ghz wifi.