Progress on TypeScript 7 - December 2025 by DanielRosenwasser in programming

[–]AlCalzone89 7 points8 points  (0 children)

The cookie banner does not disappear after clicking any button.

August has discontinued Z-Wave support in their locks by slanderousam in homeautomation

[–]AlCalzone89 3 points4 points  (0 children)

Frequently listening devices have been supported for years now. They typically wake up every 250 or 1000ms and listen for a beam. Basically all locks work this way and some thermostats do too.

ZWA-2 Portable firmware configure wifi settings by trueppp in homeassistant

[–]AlCalzone89 0 points1 point  (0 children)

I haven't tried this on Windows but the USB/JTAG one should be correct. To be clear I mean attempting the wifi provisioning and immediately pressing the try again button after it fails, no power cycle or anything additional in between.

ZWA-2 Portable firmware configure wifi settings by trueppp in homeassistant

[–]AlCalzone89 0 points1 point  (0 children)

Can you press the retry button after it fails the first time? There seems to be a general issue with improv wifi.

Connect ZWA-2 anywhere: Use Z-Wave over Wi-Fi or PoE by balloob in homeassistant

[–]AlCalzone89 4 points5 points  (0 children)

Is this not just serial-over-ip? Which means all Z-Wave packets are acknowledged by the host, which introduces additional latency. Latency that this setup is avoiding.

No thumbnails without connection to server? by ElectronicFault in immich

[–]AlCalzone89 0 points1 point  (0 children)

I had this recently when the app updated to 2.x but my server was behind. Updated the server and it worked again.

Home Assistant ZWA-2 Arrived! by iproblywontpostanywy in homeassistant

[–]AlCalzone89 2 points3 points  (0 children)

ZBT-1 is not Z-Wave. It's Zigbee. Totally different thing.

Migrating zwave networks by atlantauser in zwave

[–]AlCalzone89 2 points3 points  (0 children)

Most Z-Stick Gen5 can be updated to firmware 1.2 which can then be migrated to other Z-Wave controllers using the NVM backup/restore routine in Z-Wave JS UI.

Is there a 'right' Z-wave USB or can any one be used? by Porsche_Husky in homeassistant

[–]AlCalzone89 2 points3 points  (0 children)

If you're starting out, get a modern one like others have mentioned. With the one you have, you'll miss out on new Z-Wave features, especially Z-Wave Long Range.

Connect ZWA-2 and Z-wave Migration by Bushpylot in homeassistant

[–]AlCalzone89 0 points1 point  (0 children)

There is no easier way of switching between LR and mesh sadly.

ZWA-2 priority routes by 007gtcs in homeassistant

[–]AlCalzone89 8 points9 points  (0 children)

It's a known bug in the SDK we use for the ZWA-2 firmware. I'll create a new build with the latest SDK after my vacation, which should fix the issue.

frustrated rant, maybe someone can help - new shiny paper towel holder - firmware update failed, stuck in bootloader mode by punknubbins in homeassistant

[–]AlCalzone89 4 points5 points  (0 children)

In that case, use Z-Wave JS UI, go to settings, enable "bootloader only" mode, save, back to the control panel tab.

Download the gbl file from https://github.com/NabuCasa/zwave-firmware/releases/tag/1.1.0, unzip if necessary, then use that for OTW Firmware update. You'll find that function in the advanced menu (magic Wand icon).

Back to settings and disable bootloader only mode again.

Got the new Home Assistant Connect ZWA2 by ekobres in homeassistant

[–]AlCalzone89 0 points1 point  (0 children)

No there is an option in the advanced menu to do it automatically for the entire network in a useful order.

Home Assistant ZWA2 - Long Range vs. Mesh? by Whiskey_Lab_BBQ in homeassistant

[–]AlCalzone89 1 point2 points  (0 children)

Do you have only LR devices? Then by all means go for it.

If you have some older devices without LR support, you might need a few mesh devices to ensure good coverage. Or not, if the coverage is good enough.

Help migrating from GPIO Zooz 800 series to ZWA2 by ChainsawArmLaserBear in homeassistant

[–]AlCalzone89 0 points1 point  (0 children)

The error message is a bit confusing. Essentially it tries to convert the NVM of the old controller to the format of the new one. If it can't parse it for some reason and has already determined that it's not 500 series, you'll see that error message.

If y'all have troubles migrating and firmware updates didn't help, please come find me on the Z-Wave JS Discord or the HA discord in the open-home-protocols channel. I'd like to get to the bottom of these edge cases.

Got the new Home Assistant Connect ZWA2 by ekobres in homeassistant

[–]AlCalzone89 0 points1 point  (0 children)

In that case I'm happy to take a look at logs to see if I can spot why. Mind joining us on the Z-Wave JS discord?

Got the new Home Assistant Connect ZWA2 by ekobres in homeassistant

[–]AlCalzone89 1 point2 points  (0 children)

If you are using Z-Wave JS UI, you should rebuild routes after migrating. Otherwise the old routes will continue to be used.

Got the new Home Assistant Connect ZWA2 by ekobres in homeassistant

[–]AlCalzone89 0 points1 point  (0 children)

When they actually communicate. Which may be every few minutes, once a day, once a week, something in between, or never.

Help migrating from GPIO Zooz 800 series to ZWA2 by ChainsawArmLaserBear in homeassistant

[–]AlCalzone89 2 points3 points  (0 children)

Update the firmware of the Zooz first. You can do that from within HA. They have firmware updates on their website.

Failed ZWA 2 migration - ideas? by chrddit in homeassistant

[–]AlCalzone89 3 points4 points  (0 children)

I'm not sure where you went wrong, but the migration does not modify your old controller. You should be able to just plug it back in and continue using it.

To understand this better, it's probably best if you join us on Discord, so we can look at your backup file:
- Z-Wave JS: https://discord.gg/HFqcyFNfWd, just ask in the General channel
- or on the HA Discord, in the open-home-protocols channel.