Announcement

Collapse
No announcement yet.

Parent Child relationship errors

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

    Parent Child relationship errors

    I and others are getting errors on startup related to child/parent relationship errors. These errors persist even after going to Setup-->Labs-->Fix Relationships on 3.0.0.51.

    Here are my errors on startup: I have Solar Radiation, UV Index, Temperature Indoor and Humidity Indoor unchecked in settings. Luminance is device 4340 and has never updated since the start and has a null value. I have no devices numbered 3004, 3002, 2993
    Apr-27 12:13:52 PM Warning Device (4340) AmbientWeather AmbientWeather Luminance does not reference a parent, it should reference one parent
    Apr-27 12:13:52 PM Warning Issue checking child device (4340) AmbientWeather AmbientWeather Luminance
    Apr-27 12:13:52 PM Warning Device (4340) AmbientWeather AmbientWeather Luminance is marked as child, but does not reference any parent
    Apr-27 12:13:52 PM Warning Issue checking parent device (2989) AmbientWeather AmbientWeather Ambient Weather Station
    Apr-27 12:13:52 PM Warning Device (2989) AmbientWeather AmbientWeather Ambient Weather Station references a child device with a device ref of 3004 but the device does not exist
    Apr-27 12:13:52 PM Warning Issue checking parent device (2989) AmbientWeather AmbientWeather Ambient Weather Station
    Apr-27 12:13:52 PM Warning Device (2989) AmbientWeather AmbientWeather Ambient Weather Station references a child device with a device ref of 3002 but the device does not exist
    Apr-27 12:13:52 PM Warning Issue checking parent device (2989) AmbientWeather AmbientWeather Ambient Weather Station
    Apr-27 12:13:52 PM Warning Device (2989) AmbientWeather AmbientWeather Ambient Weather Station references a child device with a device ref of 2993 but the device does not exist
    Apr-27 12:13:52 PM Warning Issue checking parent device (2989) AmbientWeather AmbientWeather Ambient Weather Station

    #2
    Thanks for reporting. This is a known item with AmbientWeather and Life360 plugins from the HS3 updates for HS Mobile support. There are plans to update the plugins to remove the errors. In the meantime this does not effect functionality at this time.

    Comment


      #3
      Ultrajones
      macromark

      The Tools>Setup>Labs>Fix Relationships button fixed the vast majority of my broken Parent/Child issues, but...

      I've found another issue to report, in addition to those listed above :
      May-27 10:10:07 AM Warning Device (658) Monitored Device UltraMon3 Plugin UltraMon3 Gateway Monitoring references a child device with a device ref of 663 but the device does not exist
      May-27 10:10:07 AM Warning Issue checking parent device (658) Monitored Device UltraMon3 Plugin UltraMon3 Gateway Monitoring
      May-27 10:10:07 AM Warning Device (658) Monitored Device UltraMon3 Plugin UltraMon3 Gateway Monitoring references a child device with a device ref of 662 but the device does not exist
      May-27 10:10:07 AM Warning Issue checking parent device (658) Monitored Device UltraMon3 Plugin UltraMon3 Gateway Monitoring
      May-27 10:10:07 AM Warning Device (658) Monitored Device UltraMon3 Plugin UltraMon3 Gateway Monitoring references a child device with a device ref of 657 but the device does not exist
      May-27 10:10:07 AM Warning Issue checking parent device (658) Monitored Device UltraMon3 Plugin UltraMon3 Gateway Monitoring
      HomeSeer Version: HS3 Pro Edition 3.0.0.500
      Operating System: Microsoft Windows 10 Pro - Work Station

      Enabled Plug-Ins:
      2.1.0.119: AmbientWeather | 3.0.21.0: BLLock | 2.0.24.0: BLUPS | 1.3.6.0: Device History | 3.0.0.56: EasyTrigger | 3.1.0.7: MeiHarmonyHub | 3.0.6681.34300: UltraCID3 | 3.0.6644.26753: UltraLog3 | 3.0.6554.33094: UltraMon3 | 3.0.0.91: weatherXML | 3.0.1.245: Z-Wave | 3.0.51: HS Touch Designer | 3.0.0.40 Z-Seer+

      Comment


        #4
        Those are Warnings about UltraMon3....

        Comment


          #5
          Originally posted by Simplex Technology View Post
          Those are Warnings about UltraMon3....
          Yes, I know. I just offered that I was receiving those warnings in addition to AmbientWeather, which is already being dealt with. I don't know that anyone is aware of the UltraMon P/C issues...
          HomeSeer Version: HS3 Pro Edition 3.0.0.500
          Operating System: Microsoft Windows 10 Pro - Work Station

          Enabled Plug-Ins:
          2.1.0.119: AmbientWeather | 3.0.21.0: BLLock | 2.0.24.0: BLUPS | 1.3.6.0: Device History | 3.0.0.56: EasyTrigger | 3.1.0.7: MeiHarmonyHub | 3.0.6681.34300: UltraCID3 | 3.0.6644.26753: UltraLog3 | 3.0.6554.33094: UltraMon3 | 3.0.0.91: weatherXML | 3.0.1.245: Z-Wave | 3.0.51: HS Touch Designer | 3.0.0.40 Z-Seer+

          Comment


            #6
            Originally posted by ewkearns View Post

            Yes, I know. I just offered that I was receiving those warnings in addition to AmbientWeather, which is already being dealt with. I don't know that anyone is aware of the UltraMon P/C issues...
            Ok.

            There were a couple of recent conflicts/items that came up around UltraMon3 and they were reported in his forum. Unfortunately I don't have any means to contact UltraJones as I had major issues with the UltraLighting3 plugin and after posts and a PM and absolutely no responses I resorted to replacing my LIFX lamps with Hue.

            The last I heard he was having a family emergency of some sort. I hope things go well or he hands his plugins over to another developer to continue with and maintain.

            Comment


              #7
              Originally posted by ewkearns View Post
              Ultrajones
              macromark

              The Tools>Setup>Labs>Fix Relationships button fixed the vast majority of my broken Parent/Child issues, but...

              I've found another issue to report, in addition to those listed above :
              May-27 10:10:07 AM Warning Device (658) Monitored Device UltraMon3 Plugin UltraMon3 Gateway Monitoring references a child device with a device ref of 663 but the device does not exist
              May-27 10:10:07 AM Warning Issue checking parent device (658) Monitored Device UltraMon3 Plugin UltraMon3 Gateway Monitoring
              May-27 10:10:07 AM Warning Device (658) Monitored Device UltraMon3 Plugin UltraMon3 Gateway Monitoring references a child device with a device ref of 662 but the device does not exist
              May-27 10:10:07 AM Warning Issue checking parent device (658) Monitored Device UltraMon3 Plugin UltraMon3 Gateway Monitoring
              May-27 10:10:07 AM Warning Device (658) Monitored Device UltraMon3 Plugin UltraMon3 Gateway Monitoring references a child device with a device ref of 657 but the device does not exist
              May-27 10:10:07 AM Warning Issue checking parent device (658) Monitored Device UltraMon3 Plugin UltraMon3 Gateway Monitoring
              I installed Ultramon in early April and I'm not seeing these warnings. It's likely Ultrajones had already dealt with the problem for new devices; which would indicate that deleting your monitored network devices and letting the plugin recreate them should eliminate the problem provided your plugin is up to date. That's a guess.
              Failing that, you can wait for Ultra to return. Meantime in any case, the Warnings are only that... warnings, and have absolutely no functional effect other than being present in the log at startup. They were added to HS3 in later versions evidently to accommodate something to do with Alexa.


              https://forums.homeseer.com/forum/3r...s-availabllity
              Real courage is not securing your Wi-Fi network.

              Comment

              Working...
              X