Levoit Binding

dagoodyear · February 24, 2023, 2:44am

Hi @phui, Over the weekend I’ll try to get a build against 3.4.1 and upload a separate jar for it. Please snapshot your system / back it up if its a live system before installing! As I would if testing on our primary system. In this case I will before posting to ensure the 3.4.X upgrade path is checked prior to pushing the jar out.I’ll send a message once I’ve build and confirmed the 3.4.X version.

phui · February 24, 2023, 3:13am

@dagoodyear Thank you very much !!!

dagoodyear · February 24, 2023, 12:46pm

HI @phui, I managed to get it done while on lunch and tested here - had to download 3.4.1 to mirror your one. First I installed the normal one to setup the devices. Then download this one and added it to my addin’s directory and remove the installed binding form openhab official binding installs. Reboot and when it boots backup you should see a new device family under the device properties if it’s using the new version.

If you need to roll back I’d suggest restore the backup, otherwise what I did on this install was install the new binding. Shutdown openhab - delete from the addin’s folder and cleared the tmp and cache directories. On restarting it ran with the original binding (although you’ll still have that extra prop left against the devices).

P.S if pos could you confirm the current 200 one you have as well please.

phui · February 24, 2023, 5:40pm

@dagoodyear
Tried your new binding.
Remove the system binding, install and restart your new one via console.
The L450S was discovered immediately.

Thanks again for your great effort !!!

Patrick

dagoodyear · February 24, 2023, 6:29pm

Hi @phui, Great thanks for the confirmation Could you do me favor and confirm what that device reports under its things Properties for Device Name and Device Family. Additionally if at all pos could you confirm the same for the 200S, and that everything is working as expected for both that would be great evidence for the PR of the changes. Hopefully you don’t mind helping. Thanks in advance.

phui · February 24, 2023, 6:33pm

@dagoodyear
Here you go:

450S

Device Type: LUH-O451S-WUS
Device Family: Oasis Mist

200S

Device Type: Dual200S
Device Family: Dual 200S

dagoodyear · February 24, 2023, 8:03pm

Thank you @phui!

sid3windr · June 10, 2023, 3:47pm

I was assuming based on the above posts that the Oasis Mist would be supported, but it doesn’t look like mine works, likely because the device type is slightly different because of my location: LUH-O451S-WEU

So I’m getting “Device Model or Type not supported by this thing” unfortunately.

I also have a Cosori Air Fryer which is supported by pyvesync but not by the OpenHAB binding, any chance of getting that one supported as well?

Thanks!

dagoodyear · June 10, 2023, 11:10pm

Hi @sid3windr,

Regarding the Oasis Mist, I did some additions to add support for that. However I could only get the PR added to the 4.X builds, as only bug fixes go in older releases. In theory the 4.X snapshots or maybe even more now should support it based on the additions here:

github.com

openhab/openhab-addons/blob/4eec1a7f47384dac88359f5a4d7c82e4327589e4/bundles/org.openhab.binding.vesync/src/main/java/org/openhab/binding/vesync/internal/handlers/VeSyncDeviceAirHumidifierHandler.java#L74


      
          
          public static final VeSyncDeviceMetadata CLASSIC300S = new VeSyncDeviceMetadata(DEV_FAMILY_CLASSIC_300S,
                  Arrays.asList("A601S"), List.of("Classic300S"));
          
          public static final VeSyncDeviceMetadata DUAL200S = new VeSyncDeviceMetadata(DEV_FAMILY_DUAL_200S,
                  Arrays.asList("D301S"), List.of("Dual200S"));
          
          public static final VeSyncDeviceMetadata LV600S = new VeSyncDeviceMetadata(DEV_FAMILY_600S, Arrays.asList("A602S"),
                  Collections.emptyList());
          
          public static final VeSyncDeviceMetadata OASIS_MIST = new VeSyncDeviceMetadata(DEV_FAMILY_OASIS_MIST,
                  Arrays.asList("O451S"), Collections.emptyList());
          
          public static final List<VeSyncDeviceMetadata> SUPPORTED_MODEL_FAMILIES = Arrays.asList(LV600S, CLASSIC300S,
                  CLASSIC200S, DUAL200S, OASIS_MIST);
          
          private static final List<String> CLASSIC_300S_600S_MODES = Arrays.asList(MODE_AUTO, MODE_MANUAL, MODE_SLEEP);
          private static final List<String> CLASSIC_300S_NIGHT_LIGHT_MODES = Arrays.asList(MODE_ON, MODE_DIM, MODE_OFF);
          
          private final Logger logger = LoggerFactory.getLogger(VeSyncDeviceAirHumidifierHandler.class);

The matching at the same point was updated to ensure that region code’s shouldn’t cause an issue. So in theory if you have a 4.X build the Mist should work. That being said I also did do a build for the older 3.4x releases as I have not migrated myself from 3.4 so figured others may also still be on it. Details are in this thread, and somewhere a link to the 3.4X build in my repo that should include the mist support:

Please let me know if the 4.X build works for you or the custom build linked to on my github for the Mist - in theory it should. You may need to clear caches, and other-bits likely mentioned in this thread for it to pick up the custom module.

In theory it could support the other devices types, but I don’t have any of those to test with and am short of time currently. I will keep it in mind once I know I have a reasonable window of time to extend it, if no one else does first in the public repos.

Hopefully that helps - fingers crossed either the 4.X build kicks in with the mist, or the re-build of the same code against 3.4 I think it was linked to on my repo.

sid3windr · June 11, 2023, 12:33am

Hi David, thank you for the fast response! I must have assumed your fixes were also in latest 3.x (based on release dates), sorry for that. I have just downloaded the 3.4.3 jar from your github repo and put it in my 3.4.4 installation, and indeed it does now recognize the Mist and can control it!

Levoit should thank you, because I bought this one based on your support for OpenHAB

One thing, which I noted in the source code already earlier (but I have just received the Mist today and I wanted to double check), is that there is no control for the “night light” (on/off + color) in the binding, but the device does have it (and the VeSync app can control it).

dagoodyear · June 11, 2023, 12:41pm

Hi @sid3windr, I had a look at pyvesync codebase in regards to the Mist and nightlight’s. At the moment it doesn’t look like they mapped over the cal’s for the night light functionality. It may be worth opening a issue with pyvesync - Issues · webdjoe/pyvesync · GitHub, once they map it I add the relevant bit into this binding.

sid3windr · June 11, 2023, 3:40pm

Issue opened at Add support for Nightlight functionality on OasisMist · Issue #190 · webdjoe/pyvesync · GitHub .

The binding and humidifier support seems to be working well, so thanks again!