EDIT:
I apologize--your driver is working as expected with my Levitate Nowa! Google Home, however, does not pass along Open/Close/Set Position/Partial Open commands to Hubitat--it's doing its own interpretation and its own interpretation is that "Open" means both rails go to 100, "Close" means both rails go to zero, and "partial open" means both rails go to 25. What?! LOL. Useless.
I think there are different desired behaviors based on whether we're using this driver with a Levitate Nowa versus a Day/Night Nowa:
- With Levitate, any Close command should send the top rail up, not down. (This was driving me crazy until I realized the driver was actually for the Day/Night shade. A 'Top Rail Close Direction' parameter would solve the Levitate problem and also might be awesome just for the Day/Night all by itself--it'd let the user decide whether "closed" means light-filtered or blackout.)
- With both, it'd be amazing if the parent device's Partial Open command could use pre-defined custom top/bottom rail position values.
I'm not sure what's possible, or how difficult any of that is, so feel free to tell me I'm on crack. LOL.
In Google Home specifically, neither parent nor child devices' commands are accessible in Google Home's "Automations" (routines), so setting both top and bottom rail to a "favorite" position currently requires two separate set position voice commands--not ideal. I think the two things I mentioned above would solve that entire issue though!
(I did get "one Google Home voice command for two rail positions" working using a Virtual Shade and Rule Machine. But the 15-30s delay with that was yucky.)
