kpine

The `zwave.node_event` (AKA Basic Set) event is no longer supported. See #90 and OpenZWave/qt-openzwave/issues/60. (Plus it isn't implemented here)

That looks like the [behavior for the current zwave integration](https://github.com/home-assistant/core/blob/dd91b51435463ca06847d6290cdd8db091bbce78/homeassistant/components/zwave/node_entity.py#L324), so it was probably just missed here.

How does HA know that the switch is not functional?

I don't have these devices, but I've looked at the manuals before. It provides switches S1 and S2, so I always thought those are the two switches provided.  S2...

Make sure you're using the latest version of the add-on, then attach [driver **Debug** logs](https://www.home-assistant.io/integrations/zwave_js/#how-to-access-the-z-wave-logs) of the firmware upgrade process in a comment here.

What about the controller's region and power levels? Are they set correctly? 

I don't know if it matters, or what the impact is, but those power levels are nowhere close to the recommended ones for a 700-series stick. What affect does that...

`zw_programmer` is a command line tool for doing OTW updates of the 700-series controllers and NVM backups and restores. It won't work for flashing the Zniffer firmware on a UZB3....

FWIW, I updated this device manually (before the OTA service existed) with the file from GitHub, and have had no issues at all. I wonder what the difference could be....

These parameters seem to be dependent on firmware version?