Announcement

Collapse
No announcement yet.

BUG: Z-Wave Backup option doesn't always use the correct data and other issues

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • BUG: Z-Wave Backup option doesn't always use the correct data and other issues

    This has been around for a while but I always end-up forgetting about it. Well, this time I got burned a bit and it took a bit to recover.

    The Z-Wave plugin is not getting a new Date and Time whenever you do a "Backup this interface". The only time I ever see it change is the first time it's used once the HS3 has been started. After that it uses the same date over and over and over again. So what happens if that you think you're getting another backup when in reality you're just backing up over the same backup file.

    I got burned on this in that HS3 lost the devices in the Z-Wave tables The node number is in the device but when you do a backup it's missing from the backup. (BTW, this is another bug that needs to be looked at.) So when I backed-up the Z-Wave data it overwrote my good backup file so I had to go back a few files to find the good one.

    The simplest way to fix this is to always grab the current Date and Time whenever you enter the Z-Wave backup menu.

    I'd also like to see a Z-Wave backup done when a normal backup is done. I'll bet that most people think that a Z-Wave backup is done during a normal backup when in fact it's not. So you always need to remember to do a ZiWave backup before a regular backup. This should backup all active interfaces.

    This is also true when using BLBackup in that unless you manually run a Z-Wave backup you just get what was last backed-up which could have been months ago. What would help is a way to trigger a Z-Wave backup from an event so it could be done before calling BLBackup from the same event. The Z-Wave backup trigger should wait till it's done so the next function in that event will not run till the Z-Wave backup finishes. It should also backup all interfaces.

    I realize that other than the fixing the date the other requests might be harder to take care of since it requires interaction of the Z-Wave module and the Event structure. However the Date fix should be a very quick to take care of.
    HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
    Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
    IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

    Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
    mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

    Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

  • #2
    Sounds like it might be a linux only bug. On Windows, it seems to always have the current date/time for those.
    HS 3.0.0.548: 1965 Devices 1146 Events
    Z-Wave 3.0.1.262: 122 Nodes on one Z-Net

    Comment


    • #3
      Originally posted by Timon View Post
      The Z-Wave plugin is not getting a new Date and Time whenever you do a "Backup this interface". The only time I ever see it change is the first time it's used once the HS3 has been started. After that it uses the same date over and over and over again. So what happens if that you think you're getting another backup when in reality you're just backing up over the same backup file.
      Indeed if you do a manual backup not only does the Date and Time in the file name not update but the interface name doesn't change if you select a different interface. However, you can edit the automatically generated file name when you create new backups but there is no warning if you overwrite an existing file.

      Whilst it would be good to see the default file name update correctly I can't say I ever use the manual backups. As far as I am aware HS3 creates a backup every time you include or exclude a node from an interface and that is the only time the information changes. As far as I can tell these automatically generated backup files are named correctly and don't overwrite previous versions. Looking through my //Data/Z-Wave folder there are a whole series of backup files related to each of my interfaces which appear to be from each time I have included or excluded nodes. I will keep an eye on this next time I add or exclude a node to make sure this works as I think it does.

      Steve

      Comment


      • #4
        Didn't know HS3 made it's own backup files during includes or excludes and in fact have no proof either way that it does. I'll check my Z-Wave backup files the next time before I do any includes or excludes just to be sure.

        As far as being a Linux only I have no idea although I can't see why the platform would make any difference. I posted the issue and hopefully Rich will take a look at it.

        The other issue I posted were related but would be more of a feature request and not a bug.
        HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
        Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
        IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

        Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
        mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

        Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

        Comment


        • #5
          Originally posted by Timon View Post
          Didn't know HS3 made it's own backup files during includes or excludes and in fact have no proof either way that it does.
          Have you looked in your //Data/Z-Wave folder. I have a whole series of backup files going back years that I'm sure were created automatically. I'm on Windows though.

          Steve

          Comment


          • #6
            Don't have that many and the ones I do seem to be about how often I create one. Still I will only be able to tell when I create or remove some devices. That will likely happen next month when I buy some more devices I need.
            HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
            Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
            IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

            Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
            mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

            Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

            Comment


            • #7
              On Windows, my observation has been that the filename is properly initialized only the first time after the plugin is started.Cycling just the plugin (not HS3 entirely) should get it to initialize.

              I added three locks back in February, and I see three backups that would correspond to those activities.

              I run an automatic backup weekly using a script I developed before automatic backup was instituted: https://forums.homeseer.com/forum/li...-backup-script

              Comment


              • #8
                Thanks for that input Dave. If it's picking up the date when the plugin is started it seems it would be easy to do it again whenever the backup interfaces command was selected.

                BTW, Has anyone ever figured out what the data on the lines in the backup file mean? Always noticed that a large number of the lines are identical and was just curious what they mean.
                HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
                Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
                IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

                Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
                mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

                Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

                Comment

                Working...
                X