search

openhab / openhab-addons

Add-ons for openHAB
https://www.openhab.org/
Eclipse Public License 2.0
1.9k stars 3.59k forks source link

[vesync] Levoit Vital 100s Air Purifier support #17798

Open m0rgano opened 9 hours ago

m0rgano commented 9 hours ago

I have a Levoit Vital 100s air purifier.

I'm currently running OH 4.2.2 on a Linux box (Ubuntu), Java 17.

When creating a Thing for this device using the VeSync Binding (4.2.2), I get the following error:

2024-11-23 14:03:34.031 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'vesync:airPurifier:fbcc735784' changed from INITIALIZING to UNKNOWN

2024-11-23 14:03:34.044 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'vesync:airPurifier:fbcc735784' changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): Device Model or Type not supported by this thing

The VeSync bridge appears to be working OK. I believe the issue is just regarding support for the 100s device.

lsiepel commented 9 hours ago

If I’m not mistaken this support is about to get added by this pr : https://github.com/openhab/openhab-addons/pull/15296

dag81 commented 1 hour ago

Thank you for raising @m0rgano, apologies for the misdirection by using the old repo as a file share. Also your really on it @lsiepel thank you for tagging up, and spotting so quickly :) m0rgano has been really helpful in testing with a real device, there is 1 bit we are trying to narrow down, as the simulations align on the core bits against the software stack that has historically been key and where this code is ported from generally, but fan speed is uncontrollable. Results currently from m0rgana are:

Summary of tests on the channels:

enabled: OK (reading & writing) display: OK (reading & writing) childLock: OK (reading & writing) filterLifePercentage: OK (reading, writing N/A) fanMode: OK (reading & writing) airQuality: OK (reading, writing N/A) airQualityPM25: OK (reading, writing N/A) manualFanSpeed: OK reading, but changes from OH not reflected on device

Hopefully we can narrow down quickly, otherwise would prefer to add a known limitations section to the readme if all else fail's on this, and raise a new bug for the specific manualFanSpeed issue - in the worst case, if we cant pin it down in time. Only as there's so many other key updates in that PR that should make it to 4.3 that will allow much better interoperability for other users of the currently tested devices, in other regions.