forum

The approach you've describer will mostly work, but it's not ideal for the following reasons: 1. The controller switch approach will cause the new controller to have a node ID that is not 1. While a controller with a ID node that's different than 1 should work, it will introduce some subtle problems...

The results from the 2 curl commands look normal. The first command returns the Z-Way's data dictionary for the battery command class. It shows the battery value is in the data tag "last", as expected. The second command returns Z-Way's internal representation for the Virtual Device (JavaS...

It looks like the virtual device is working based on the event history. I don't know why the UI is showing 0%. Perhaps the semicolon in the JavaScript expression should be removed. On a tangent, the virtual device isn't querying the door lock (i.e., impacting the battery life) - it's simply querying...

The virtual device is set up to update its value once per hour. I'm guessing you did not wait for the value to update itself. You can trigger an update by clicking on the clock icon/timestamp on the main UI for the virtual object or you can wait an hour and the updated battery level should appear. P...

Yes, definitely possible. Assuming your lock has a Z-Wave node ID of 18, run this command to confirm the battery level value is returned: curl -s -u admin:[YOUR ZWAY ADMIN PASSWORD] --globoff "http://127.0.0.1:8083/ZWave.zway/Run/devices[18].instances[0].commandClasses[128].data.last.valueOf()&...

Adding/reinforcing what @lanbrown wrote... Secondary controllers have been deprecated in the Z-Wave standard as they are incompatible with S2 security. They were part of the original Z-Wave specification that envisioned users having a portable/battery-operated controller and a line-powered stationar...

Based on your troubleshooting, it looks like communication to your RazBerry card (over the serial port) is not working correctly and the expert UI is not showing you accurate information. As a result, you may be chasing a red herring. The /var/log/z-way-server.log file will show if there's a problem...

Please try to restore the .zbk file from your old master Pi onto your newly rebuilt Pi.

If the restore fails, move the Z-Wave controller from your dead master Pi into your newly rebuilt Pi (safely, with the power off).

I think the best solution is to fix the problem that's preventing restore of the .zbk (expert UI backup). Try power-cycling your PI (do a graceful shutdown, don't just yank the power out) and trying the restore again. If that fails, do you haze a .zab backup (from the normal/smarthome UI)? If so, tr...

From what I can tell, a shutdown of Z-Wave.me servers would break the following: 1. Mobile app remote access (LAN access should still work if the local IP address/hostname is configured in the app). It's entirely possible the app has a built-in kill switch where the app needs to successfully check i...