Closed IrgendSoEtwas closed 2 years ago
Also experiencing this and the above fix works. Thanks @IrgendSoEtwas
Interesting, I wonder if the EU and US models use different naming conventions. We should probably check for both device types and put them in an array, or just use device name.
I'm on vacation until 1/2. I can fix it after that unless someone else gets to it before then. Thanks for reporting!
@joshryandavis @IrgendSoEtwas So I wound up just adding a new device called Dual200S_EU that looks for LUH-D301S-WEU
as the deviceType. I also found that there is a LUH-D301S-WUK
model as well, so that's been added too.
Just to make sure...there are only 2 mist levels and an auto mode on this model, right? If so, 1.3.1-beta3 should work for you. Please test it if you can. Thanks!
Thanks @pschroeder89 for looking into it!
Just to make sure...there are only 2 mist levels and an auto mode on this model, right? If so, 1.3.1-beta3 should work for you. Please test it if you can. Thanks!
Correct, it still has a low, high and an auto mode on the model. I will try to test the beta3 version when I got time and let you know!
Just downloaded the 1.3.1-beta3 and works for me as intended @pschroeder89!
Pushed version 1.3.1 to npm. Thanks for reporting and testing!
Describe The Bug:
After installing the plugin, no devices were added to the accessories section of HomeBridge. I am using correct VeSync account credentials and the Dual 200s is registered and linked with the account. With enabled debug mode, I can see that the API call can find the device but it won't get added.
Expected behavior:
As the Dual 200s should be supported by the plugin, the device should be added by HomeBridge.
Logs:
Environment:
Suggestion:
I already fixed it locally for myself as I noticed that the deviceType of my Dual 200s got reported as
"deviceType": "LUH-D301S-WEU"
and I simply changed the correspondingenum DeviceName
in thedeviceTypes.ts
file. However I do know that this is not a general purpose solution and thus is not feasible for a PR. I just wanted to inform about this. Maybe the device type check can also consider the"deviceName": "levoit Dual 200s",
property or something.