Nice, @Khalos, appreciate the (duh) clarification. I’m a recent "Smart"Things convert (2ish months) - started on OZW but quickly moved to ZWaveJS before I got in too deep. Imo, JS is ‘ready’ - super fast, stable, and now covers my bases (simple environment = mostly switches, a few outlets, and a Linear garage door). Main gap for me is the lack of config UI - pending (this team is moving crazy-fast), and the JS2MQTT add-on solves that gap in the interim if you’re so inclined.
I’m betting @kylerw’s OZW->JS blueprint provides a nice head start - seems the primary difference is mapping text identifiers (e.g. “KeyPressed”) instead of scene_data identifiers (e.g. 7680). Add the long-press identifier and you’re there. That and aligning the switch-name ZwaveJS identifier. These blueprints are still ‘foreign territory’ for me, but as with all things HASS I’m sure it just takes a few cycles to get familiar / proficient. Will see if I can burn a weekend cycle or two in the near future.