Getting "Connecting to Vesync failed!" after upgrade to homebridge 1.8.3

[dakovacic]

After upgrading to home bridge 1.8.3 this morning I am seeing the plugin reporting "Connecting to Vesync failed!" and discovery of my devices, a number of etekcity smartplugs, is failing.

Here is my homebridge information:
Hardware: Raspberry Pi 3 Model B Plus Rev 1.3
Os: "Debian GNU/Linux 12 (bookworm)"
HB version: 1.8.3
NodeJS Version: v20.14.0

From the logs:
[20/06/2024, 10:07:53] Loaded plugin: homebridge-vesync-v2@2.3.9
[20/06/2024, 10:07:53] Registering platform 'homebridge-vesync-v2.VesyncPlug'

[20/06/2024, 10:07:54] [VesyncPlug] Initializing VesyncPlug platform...

[20/06/2024, 10:07:55] [VesyncPlug] DeviceDiscovery invoked

[20/06/2024, 10:07:57] [VesyncPlug] Connecting to Vesync failed!
[20/06/2024, 10:07:57] [VesyncPlug] Adding discovered devices
[20/06/2024, 10:07:57] [VesyncPlug] Discovery complete

With about once a minute a repeat of:
[20/06/2024, 10:34:06] [VesyncPlug] DeviceDiscovery invoked
[20/06/2024, 10:34:06] [VesyncPlug] Connecting to Vesync failed!
[20/06/2024, 10:34:06] [VesyncPlug] Adding discovered devices
[20/06/2024, 10:34:06] [VesyncPlug] Discovery complete

I've tried:

• Disabling the plugin, waiting 5 minutes and reenabling the plugin
• Uninstalling and reinstalling the plugin
• upgrading nodes from 20.12.1 to 20.14.0

All my devices are still available via the VeSync app on my iPhone. At this point I have the plugin disabled so that I do not fill up my logs.

[paulg1981]

Same exact problem for me.

[fkick]

Also seeing this issue.

[jimcrammond]

I've hit this too. It seems the response to the query in getDevices returns an error response with the reason: 'the token has expired'. Don't know why that is though.

[mickgiles]

version 2.3.10 published fixing this issue.
apparently vesync changed their API and it was unrelated to the homebridge upgrade

[jimcrammond]

Thanks for the quick turnaround. I realized when reviewing homebridge logs again that the issue started a bit before I upgraded.