Announcement

Collapse
No announcement yet.

Device Changed, but not handled by plugin: Relationship,Relationship

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

    Device Changed, but not handled by plugin: Relationship,Relationship

    I've been chasing the HS3 logging stopping issue, one of the suggestions is to turn on debug logging in HS3 (from Control Panel: &hs.DebugMode=32). When I did this I noticed a Debug Logs folder was created, and a couple of HS debug logs started. As I was looking at these I saw the creation of MySOmfy.log in this debug log folder. Now when I open it I see I'm being flooded with the messages below. What is causing this? These are not showing in the HS3 log, but I am wondering if they are part of the log freezing issue.

    3/5/2019 9:46:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:46:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:46:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:46:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:46:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:46:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:46:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:46:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:46:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:46:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:46:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:46:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:46:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:48:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:48:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:48:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:48:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:48:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:48:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:48:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:48:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:48:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:48:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:48:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:48:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:48:32 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:51:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:51:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:51:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:51:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:51:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:51:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:51:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:51:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:51:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:51:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:51:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:51:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:51:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:52:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:52:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:52:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:52:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:52:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:52:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:52:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:52:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:52:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:52:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:52:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:52:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:52:48 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:54:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:54:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:54:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:54:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:54:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:54:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:54:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:54:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:54:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:54:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:54:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:54:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:54:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:56:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:56:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:56:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:56:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:56:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:56:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:56:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:56:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:56:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:56:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:56:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:56:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:56:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:58:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:58:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:58:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:58:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:58:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:58:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:58:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:58:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:58:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:58:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:58:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:58:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 9:58:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 10:00:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 10:00:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 10:00:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 10:00:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 10:00:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 10:00:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 10:00:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 10:00:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 10:00:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 10:00:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 10:00:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 10:00:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship
    3/5/2019 10:00:49 AM ~ Device Changed, but not handled by plugin: Relationship,Relationship

    As there is not much to configuring this plugin, I'm at a loss on how to address other than ask for help.

    Click image for larger version

Name:	MyS0mfy.jpg
Views:	62
Size:	75.3 KB
ID:	1290151

    Mike

    #2
    Hi,

    You can ignore this log post as it only reflects changes to a device that is pushed in the HS3 api towards all plugins and as it was a change on a device the plugin does not own it just ignores it (but prints this line in the debug log).

    To disable debug you should go to the Config filder in the HS3 root folder. Here you should find a MyS0mfy.ini file


    in dis file you can remove the debug line or set it to false:
    [General]
    Debug=False
    LogToFile=False

    Comment


      #3
      Originally posted by Toby View Post
      Hi,

      You can ignore this log post as it only reflects changes to a device that is pushed in the HS3 api towards all plugins and as it was a change on a device the plugin does not own it just ignores it (but prints this line in the debug log).

      To disable debug you should go to the Config filder in the HS3 root folder. Here you should find a MyS0mfy.ini file


      in dis file you can remove the debug line or set it to false:
      [General]
      Debug=False
      LogToFile=False
      Thanks for the quick reply. I added both entries to the ini file, and restarted the plugin. However the MyS0mfy.log file continues to grow (16 to 20 entries per second).
      Mike

      Comment


        #4
        what version are you running? it looks like the 1.0.2.0 version has some missing code in the logging part.as it looks like this version logs some events even if debug flag is set to false...
        I'm running a newer version as I have been working on some addons, but this is not released. This version does not have this logging issue and if you set debug to false it stops logging. I will try to get one out fast.

        In any case - I don't belive this to be the root cause of your problem as it only displays the fact that some other devices are being constantly updated/changed.
        HS3 would announce any update to all plugins that subscribe to updates and this is what is shown in the log.

        a device was updated, but it was not one of the devices belonging to the plugin so the plugin ignores the update.
        What this plugin has subscribed to is to be notified about config changes to devices. This is used to update the plugin if name or devices are changed outside the plugin GUI. As a consequence all config changes triggers an event. And if the device is not for the plugin it ignores the change and prints this line with the remaining parameters.

        W
        hat you need to figure out is why you have config changes so often - and from the looks of things it looks like its the device relationships that is changing.

        Comment


          #5
          Yeah it's version 1.0.2.0. Not a big deal as it's only logging when debug mode logging is enabled. Thanks for the clarification on the device relationship issue, I'll look into that elsewhere.
          Mike

          Comment


            #6
            to be clear, the 1.0.2.0 version is logging some of the lines because the "Debug Log" folder exists. It has nothing to do with the activation of debug mode for HS3.
            the version i have here in beta logs only if Debug flag is set to true AND debug log folder exists.

            if you cant figure out what device is being changed, i could quickly send you a version that prints out the reference number for the device that is changed.

            Comment


              #7
              Originally posted by Toby View Post
              to be clear, the 1.0.2.0 version is logging some of the lines because the "Debug Log" folder exists. It has nothing to do with the activation of debug mode for HS3.
              the version i have here in beta logs only if Debug flag is set to true AND debug log folder exists.

              if you cant figure out what device is being changed, i could quickly send you a version that prints out the reference number for the device that is changed.
              Thanks for the offer Toby. It's not a big deal at the moment, I'm keeping an eye on the size of the log file. Hopefully I won't have to keep the debug log folder around for too long.
              Mike

              Comment


                #8
                Toby, I wrote a small script to duplicate the reporting of device changes to a log file with information on what is changing. I was trying to figure out why so many changes per second (around 50-60) were logging in your debug log. I discovered that all counters and timers are included by default in the device change notification. Once I removed those from reporting what I see is expected - number of device changes per second varies but they are all valid device changes. I see my weather station and several z-wave power devices are updating quite frequently, but nothing excessive.

                At least now I know my system is not chasing itself. Thanks for helping me figure this out.
                Mike

                Comment

                Working...
                X