mickgiles / homebridge-vesync Goto Github PK

Here is the configuration file segment
{
"platform": "VesyncPlug",
"name": "VesyncPlug",
"username": "[email protected]",
"password": "PASSWORD",
"debug": "True"
}

Here are the logs:
11/27/2020, 10:01:19 AM [VesyncPlug] DeviceDiscovery invoked
11/27/2020, 10:01:19 AM (node:29459) UnhandledPromiseRejectionWarning: TypeError [ERR_HTTP_INVALID_HEADER_VALUE]: Invalid value "undefined" for header "tk"
11/27/2020, 10:01:19 AM at ClientRequest.setHeader (_http_outgoing.js:529:3)
11/27/2020, 10:01:19 AM at new ClientRequest (_http_client.js:243:14)
11/27/2020, 10:01:19 AM at Object.request (https.js:316:10)
11/27/2020, 10:01:19 AM at /home/hoobs/.hoobs/node_modules/hyper-request/hrequest.js:391:79
11/27/2020, 10:01:19 AM at new Promise ()
11/27/2020, 10:01:19 AM at Object.makeRequest (/home/hoobs/.hoobs/node_modules/hyper-request/hrequest.js:270:29)
11/27/2020, 10:01:19 AM at Object.doPost [as post] (/home/hoobs/.hoobs/node_modules/hyper-request/hrequest.js:163:25)
11/27/2020, 10:01:19 AM at EtekCityClient.getDevices (/home/hoobs/.hoobs/node_modules/homebridge-vesync-v2/lib/client.js:48:28)
11/27/2020, 10:01:19 AM at /home/hoobs/.hoobs/node_modules/homebridge-vesync-v2/index.js:65:28
11/27/2020, 10:01:19 AM (node:29459) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)
11/27/2020, 10:01:40 AM [LevitonDecoraSmart] onGetPower Front Lights
11/27/2020, 10:01:40 AM [LevitonDecoraSmart] onGetPower Ilene’s Lamp

11/27/2020, 10:02:19 AM [VesyncPlug] DeviceDiscovery invoked
11/27/2020, 10:02:19 AM (node:29459) UnhandledPromiseRejectionWarning: TypeError [ERR_HTTP_INVALID_HEADER_VALUE]: Invalid value "undefined" for header "tk"
11/27/2020, 10:02:19 AM at ClientRequest.setHeader (_http_outgoing.js:529:3)
11/27/2020, 10:02:19 AM at new ClientRequest (_http_client.js:243:14)
11/27/2020, 10:02:19 AM at Object.request (https.js:316:10)
11/27/2020, 10:02:19 AM at /home/hoobs/.hoobs/node_modules/hyper-request/hrequest.js:391:79
11/27/2020, 10:02:19 AM at new Promise ()
11/27/2020, 10:02:19 AM at Object.makeRequest (/home/hoobs/.hoobs/node_modules/hyper-request/hrequest.js:270:29)
11/27/2020, 10:02:19 AM at Object.doPost [as post] (/home/hoobs/.hoobs/node_modules/hyper-request/hrequest.js:163:25)
11/27/2020, 10:02:19 AM at EtekCityClient.getDevices (/home/hoobs/.hoobs/node_modules/homebridge-vesync-v2/lib/client.js:48:28)
11/27/2020, 10:02:19 AM at /home/hoobs/.hoobs/node_modules/homebridge-vesync-v2/index.js:65:28
11/27/2020, 10:02:19 AM (node:29459) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 9)
11/27/2020, 10:03:19 AM [VesyncPlug] DeviceDiscovery invoked
11/27/2020, 10:03:19 AM (node:29459) UnhandledPromiseRejectionWarning: TypeError [ERR_HTTP_INVALID_HEADER_VALUE]: Invalid value "undefined" for header "tk"
11/27/2020, 10:03:19 AM at ClientRequest.setHeader (_http_outgoing.js:529:3)
11/27/2020, 10:03:19 AM at new ClientRequest (_http_client.js:243:14)
11/27/2020, 10:03:19 AM at Object.request (https.js:316:10)
11/27/2020, 10:03:19 AM at /home/hoobs/.hoobs/node_modules/hyper-request/hrequest.js:391:79
11/27/2020, 10:03:19 AM at new Promise ()
11/27/2020, 10:03:19 AM at Object.makeRequest (/home/hoobs/.hoobs/node_modules/hyper-request/hrequest.js:270:29)
11/27/2020, 10:03:19 AM at Object.doPost [as post] (/home/hoobs/.hoobs/node_modules/hyper-request/hrequest.js:163:25)
11/27/2020, 10:03:19 AM at EtekCityClient.getDevices (/home/hoobs/.hoobs/node_modules/homebridge-vesync-v2/lib/client.js:48:28)
11/27/2020, 10:03:19 AM at /home/hoobs/.hoobs/node_modules/homebridge-vesync-v2/index.js:65:28
11/27/2020, 10:03:19 AM (node:29459) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 12)

In homebridge, getting the following:

SyntaxError: Unexpected token < in JSON at position 0
at JSON.parse ()

it keeps reloading each time.

Full log:

at Transform.<anonymous> (C:\Users\username\AppData\Roaming\npm\node_modules\homebridge-vesync-v2\node_modules\hyper-request\hrequest.js:304:43)
at Transform.emit (events.js:327:22)
at finish (internal/streams/writable.js:657:10)
at finishMaybe (internal/streams/writable.js:644:9)
at afterWrite (internal/streams/writable.js:473:3)
at afterWriteTick (internal/streams/writable.js:453:10)
at processTicksAndRejections (internal/process/task_queues.js:79:21)

SyntaxError: Unexpected token < in JSON at position 0
at JSON.parse ()
at parserFunction (C:\Users\username\AppData\Roaming\npm\node_modules\homebridge-vesync-v2\lib\client.js:13:29)
at Transform. (C:\Users\username\AppData\Roaming\npm\node_modules\homebridge-vesync-v2\node_modules\hyper-request\hrequest.js:304:43)
at Transform.emit (events.js:327:22)
at finish (internal/streams/writable.js:657:10)
at finishMaybe (internal/streams/writable.js:644:9)
at afterWrite (internal/streams/writable.js:473:3)
at afterWriteTick (internal/streams/writable.js:453:10)
at processTicksAndRejections (internal/process/task_queues.js:79:21)
[4/7/2021, 12:48:07 PM] [HB Supervisor] Homebridge Process Ended. Code: 1, Signal: null
[4/7/2021, 12:48:12 PM] [HB Supervisor] Restarting Homebridge...

I was hoping to be able to use this with my air purifier but i have no idea if this is available with this. The vesync2 homebridge plugin has no syntax guide for the purifier. Any help would be appreciated. Thanks.

I have several VeSync devices but use this plugin only for simple smart plugs. There is a purifier and a humidifier in my account that have their own plugins that better support the functions but I can't remove those two from being added as basic on/off accessories even when using the Exclude feature. The air purifier is a ESW01-USA (Core 200S) and the Humidifier is the Classic 300S (Ultrasonic Smart Humidifier).

I've added the following to the Exclude list but they both still show: ESW01-USA,ESW01,CORE200S,200S,CLASSIC300S,300S

I have recently started getting an error in the log. Says to contact the developer.

[09/12/2023, 14:18:45] [homebridge-vesync-v2] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://homebridge.io/w/JtMGR for more info.

[09/12/2023, 14:18:51] [homebridge-vesync-v2] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.

The bridge discovers my devices; all 6 of them; and their unique identifiers. However when selecting a device to turn on the wrong device is triggered.

any chance of supporting these humidifiers through HomeKit? Got a plug icon in HomeKit but doesn't control humidifier from HomeKit.

https://www.amazon.com/gp/product/B09C24TYGQ

The ESW10-USA plugs show up in homebridge but can’t be turned on or off.

Latest homebridge and this plugin, seeing this message (a lot) in console:

[homebridge-vesync-v2] ERROR: TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received null

I have two distinct Etekcity outlets in my Vesync app that are both working completely correct in the app (tapping each outlet listed turns on/off that outlet). However in Homebridge both outlets show up but clicking on either one activates the exact same outlet every time. The other outlet never turns on or off.

I have tried uninstalling and cleaning up the plugin, rebooting Homebridge and reinstalling the plugin but get the same result. The homebridge logs for the plugin show it detects both outlets separately ( I see two different serial numbers) but both items on Homebridge only seem to trigger one of the two outlets.

I bought 4 Aubess smart plugs since the etekcity ones are not available any more. I connected them to the Vesync App and they show up on Homebridge, but they do not respond to any commands. Any ideas?

Homebridge v1.3.8
homebridge-vesync-v2 v2.3.8
Node.js Version v14.15.1
Npm Version v6.14.9

[homebridge-vesync-v2] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://git.io/JtMGR for more info.

In the startup log for Homebeidge, I see:

[homebridge-vesync-v2] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://git.io/JtMGR for more info.
[homebridge-vesync-v2] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.

Just wondering if a Humidifier added to VeSync app will show up as an on/off switch when using this plugin.

My Etekcity lightbulb (https://www.amazon.com/Etekcity-Dimmable-Equivalent-2700K-6500K-Required/dp/B07NR514SD/ref=sr_1_3?dchild=1&keywords=etekcity+light+bulb&qid=1606044189&sr=8-3) shows up here but it shouldn't. Its probably appearing as part of the API pull which just lists all devices. The home app also shows the device but as an outlet and toggling it doesn't work. Is it possible to create an exclusionary list (possibly as part of the config file) to prevent these devices from appearing in the home app?

When i enter the correct information, no devices are retrieved in homebridge?

Latest v2.2.0 of the code removed the light switches. Rolled code back to v2.1.0 and they are back. Can you confirm light switches are no longer supported?