Announcement

Collapse
No announcement yet.

Force Back to Root - stopped working

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

  • Force Back to Root - stopped working

    Hi,

    I've recently updated Z Wave which may/may not have anything to do with this, however, over the same period of time SDJ-Health no longer fixes the bug with the separated Parent device against it's children. I've tried rebooting, stop/starting the plugin, tried turning off the setting and back on again, but everytime the devices are still shown as separated.

    In the log there are messages saying "Device xx forced back to parent_root_device" when the plugin starts but nothing actually happens.

    The interesting thing is if I use the Jon00Grouping utility script, this DOES work, however, it's a very labour intensive process as I've now got 20 devices separated from their parent.

    I appreciate that your (really brilliant) utility does this as a favour to the bug that Homeseer cannot seem to be bothered to fix, but if we could get this working once again, I'd be really appreciative.

    If you'd like any logs, please let me know which ones and which level.

    Thanks

    David

  • #2
    Code:
     
    Nov-20 21:51:11 SDJ-Health Activity Checking started.
    Nov-20 21:51:11 SDJ-Health Checking status...
    Nov-20 21:51:11 SDJ-Health Debug - Checking Poll Devices....
    Nov-20 21:51:11 SDJ-Health 3 devices in polling list
    Nov-20 21:51:11 SDJ-Health Debug - Starting Update Polling...
    Nov-20 21:51:11 SDJ-Health Polling devices started.
    Nov-20 21:51:11 SDJ-Health Debug - Checking Activity Devices....
    Nov-20 21:51:11 SDJ-Health Debug - Registering Enums.HSEvent.LOG
    Nov-20 21:51:11 SDJ-Health Debug - Finished registering callbacks.
    Nov-20 21:51:11 SDJ-Health Device #516 forced back to Parent_Root status!
    Nov-20 21:51:11 SDJ-Health Device #191 forced back to Parent_Root status!
    Nov-20 21:51:11 SDJ-Health Device #267 forced back to Parent_Root status!
    Nov-20 21:51:11 SDJ-Health Debug - ForceBackToRoot completed. 16 device(s) corrected.
    Nov-20 21:51:11 SDJ-Health Debug - Registering Enums.HSEvent.CONFIG_CHANGE
    Nov-20 21:51:10 SDJ-Health Device #26 forced back to Parent_Root status!
    Nov-20 21:51:10 SDJ-Health Device #160 forced back to Parent_Root status!
    Nov-20 21:51:10 SDJ-Health Device #95 forced back to Parent_Root status!
    Nov-20 21:51:10 SDJ-Health Device #33 forced back to Parent_Root status!
    Nov-20 21:51:10 SDJ-Health Device #348 forced back to Parent_Root status!
    Nov-20 21:51:10 SDJ-Health Device #152 forced back to Parent_Root status!
    Nov-20 21:51:10 SDJ-Health Device #487 forced back to Parent_Root status!
    Nov-20 21:51:10 SDJ-Health Device #19 forced back to Parent_Root status!
    Nov-20 21:51:10 SDJ-Health Device #355 forced back to Parent_Root status!
    Nov-20 21:51:10 SDJ-Health Device #68 forced back to Parent_Root status!
    Nov-20 21:51:10 SDJ-Health Device #136 forced back to Parent_Root status!
    Nov-20 21:51:10 SDJ-Health Device #341 forced back to Parent_Root status!
    Nov-20 21:51:10 SDJ-Health Device #76 forced back to Parent_Root status!
    Nov-20 21:51:10 SDJ-Health Debug - CheckAndCreateDevices completed
    Nov-20 21:51:10 SDJ-Health Debug - ForceBackToRoot started
    Debug log turned on ^^^

    and the results in the UI

    Click image for larger version

Name:	temp.jpg
Views:	10
Size:	157.3 KB
ID:	1260914

    Comment


    • #3
      Originally posted by Daveyboy View Post
      Hi,

      I've recently updated Z Wave which may/may not have anything to do with this, however, over the same period of time SDJ-Health no longer fixes the bug with the separated Parent device against it's children. I've tried rebooting, stop/starting the plugin, tried turning off the setting and back on again, but everytime the devices are still shown as separated.

      In the log there are messages saying "Device xx forced back to parent_root_device" when the plugin starts but nothing actually happens.

      The interesting thing is if I use the Jon00Grouping utility script, this DOES work, however, it's a very labour intensive process as I've now got 20 devices separated from their parent.

      I appreciate that your (really brilliant) utility does this as a favour to the bug that Homeseer cannot seem to be bothered to fix, but if we could get this working once again, I'd be really appreciative.

      If you'd like any logs, please let me know which ones and which level.

      Thanks

      David
      Can you post a screenshot of the Advanced tab of one of the orphaned root devices.

      Steve

      Comment


      • #4
        Hi Steve,

        Sure, the first one here is a device that SDJ-Health has tried to fix

        Click image for larger version

Name:	Capture.JPG
Views:	5
Size:	79.9 KB
ID:	1261003

        And this one is a device that I've just corrected using Jon00Grouping that SDJ-Health couldn't fix.

        Click image for larger version

Name:	Capture.JPG
Views:	5
Size:	95.9 KB
ID:	1261004

        Comment


        • #5
          Things have just got worse. Just rebooted the server and when MSJ-Health ran every device became orphaned again (about 20 of them), now an orphaned device root looks like this with no associated devices.

          Maybe SDJ_Health is setting the Parent Root on some devices but not the Association with the child ?? The logs even in debug mode do not show anything other than "Device xx forced back to Parent_Root status"..... Is the underscore _ relevant ?? Something changed in the latest Z-Wave module update perhaps, or a red herring ?

          Click image for larger version

Name:	Capture.JPG
Views:	5
Size:	84.4 KB
ID:	1261007

          Comment


          • #6
            and now the same device a minute later after manually resetting it using Jon00Grouping
            Click image for larger version

Name:	Capture.JPG
Views:	5
Size:	103.4 KB
ID:	1261009

            Comment


            • #7
              Originally posted by Daveyboy View Post
              Things have just got worse. Just rebooted the server and when MSJ-Health ran every device became orphaned again (about 20 of them), now an orphaned device root looks like this with no associated devices.]
              The bug that used to be the issue was the root device getting set to Standalone but leaving the Associated devices. This meant that all that was required to restore the group was to reset the roots parent status to Parent Root. I can see from your screenshot that the root devices have lost their associated devices. The pi doesn't know which child devices should be associated to the root devices so it can't correct that. You can of course correct it using Jon00's pi because you select all the child devices manually. I would turn off ForceBackToRoot in the SDJ-Health pi as it isn't going to do any good in your situation.

              Submit a bug to HS about how your devices are losing their grouping and see if you can get any response. I did read something about changes to grouping requirements made whilst developing the latest HS Mobile App so maybe that is the cause. I submitted a bug over a year ago on this but HS said there was nothing in the ZWave pi that would change the root status and that my database must be corrupted.

              Steve

              Comment


              • #8
                Yeah, thanks Steve - am going to call them when they wake up in a few hours. I've since discovered some more interesting info.

                1) Your tool is missing some devices that are set to Standalone - see post #4 above - not vitally important atm and probably related to:
                2) After a restart every device is re-ophaned again (even after using Jon00Grouping). It's only TRV devices, but there's 23 configured in the system and it's getting high visability because it's cold outside and no setpoints can be set until the parent know's it's child
                3) Each orphaned child still knows it's parent - it's just the parent that forget's it's association. If there was a way of scanning a child and re-assigning it's parentage that would fix this
                4) The problems are not in the fix/workarounds, but the reason why this is suddenly happening after a reboot - it's like there's a read only flag against the relationship status/association that isn't permanent
                5) This has just started happening in the last few days, after the Z-Wave module update

                Comment


                • #9
                  Originally posted by Daveyboy View Post
                  Yeah, thanks Steve - am going to call them when they wake up in a few hours. I've since discovered some more interesting info.

                  1) Your tool is missing some devices that are set to Standalone - see post #4 above - not vitally important atm and probably related to:
                  2) After a restart every device is re-ophaned again (even after using Jon00Grouping). It's only TRV devices, but there's 23 configured in the system and it's getting high visability because it's cold outside and no setpoints can be set until the parent know's it's child
                  3) Each orphaned child still knows it's parent - it's just the parent that forget's it's association. If there was a way of scanning a child and re-assigning it's parentage that would fix this
                  4) The problems are not in the fix/workarounds, but the reason why this is suddenly happening after a reboot - it's like there's a read only flag against the relationship status/association that isn't permanent
                  5) This has just started happening in the last few days, after the Z-Wave module update
                  Which versions of hs and ZWave are you running?

                  Comment


                  • #10
                    HomeSeer Version: HS3 Standard Edition 3.0.0.478
                    3.0.6.5: SDJ-Health
                    3.0.1.248: Z-Wave

                    Comment


                    • #11
                      Originally posted by SteveMSJ View Post

                      Which versions of hs and ZWave are you running?
                      Looks like you've been here before yourself Steve after Z wave updates and then losing associations, thanks for your help !

                      https://forums.homeseer.com/forum/ho...ations-problem

                      Comment


                      • #12
                        Originally posted by Daveyboy View Post

                        Looks like you've been here before yourself Steve after Z wave updates and then losing associations, thanks for your help !

                        https://forums.homeseer.com/forum/ho...ations-problem
                        That was a long time ago! Different type of problem. Associations rather than Relationships. That was all sorted in later ZWave versions but a drag at the time🙁

                        Comment


                        • #13
                          Originally posted by SteveMSJ View Post
                          Submit a bug to HS about how your devices are losing their grouping and see if you can get any response. I did read something about changes to grouping requirements made whilst developing the latest HS Mobile App so maybe that is the cause. I submitted a bug over a year ago on this but HS said there was nothing in the ZWave pi that would change the root status and that my database must be corrupted.
                          Daveyboy,

                          I found the post from rjh that mentioned HS altering the Parent Child relationships in a group to try and 'fix' things in HS build 470. This might have been the start of your latest problems rather than the ZWave pi.

                          https://forums.homeseer.com/forum/ho...43#post1245643

                          If you manage to get through to support you could mention this.

                          Steve

                          Comment


                          • #14
                            Originally posted by SteveMSJ View Post

                            The bug that used to be the issue was the root device getting set to Standalone but leaving the Associated devices. This meant that all that was required to restore the group was to reset the roots parent status to Parent Root. I can see from your screenshot that the root devices have lost their associated devices. The pi doesn't know which child devices should be associated to the root devices so it can't correct that. You can of course correct it using Jon00's pi because you select all the child devices manually. I would turn off ForceBackToRoot in the SDJ-Health pi as it isn't going to do any good in your situation.

                            Submit a bug to HS about how your devices are losing their grouping and see if you can get any response. I did read something about changes to grouping requirements made whilst developing the latest HS Mobile App so maybe that is the cause. I submitted a bug over a year ago on this but HS said there was nothing in the ZWave pi that would change the root status and that my database must be corrupted.

                            Steve
                            Daveboy

                            I have found the same problem as you that as well as erroneously setting some root device relationship statuses to StandAlone (the previous issue) it is also wiping the list of associated child devices. I have now updated the way the plug-in can repair these groupings to be more aggressive so that it searches for child devices that are related to the parent and rebuilds the list in the root device. I will leave it running on my system for a few days before publishing the new version to check that there aren't any adverse effects. Of course it would be better if HS were to correct the issue.

                            Did you have any luck with support? I will submit another bug and see if I can get it addressed.

                            Steve

                            Comment


                            • #15
                              Originally posted by SteveMSJ View Post

                              Daveboy

                              I have found the same problem as you that as well as erroneously setting some root device relationship statuses to StandAlone (the previous issue) it is also wiping the list of associated child devices. I have now updated the way the plug-in can repair these groupings to be more aggressive so that it searches for child devices that are related to the parent and rebuilds the list in the root device. I will leave it running on my system for a few days before publishing the new version to check that there aren't any adverse effects. Of course it would be better if HS were to correct the issue.

                              Did you have any luck with support? I will submit another bug and see if I can get it addressed.

                              Steve
                              Good news to report here. Rich has now tracked down the cause of this bug and it is corrected in ZWave 3.0.1.253 just released.
                              No more lost groupings!

                              Steve

                              Comment

                              Working...
                              X