Announcement

Collapse
No announcement yet.

No Bridges in Maintenance after 4.1.7

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

    #16
    gaf@bluerivernet.com and gjelsvik
    This is definitely an issue with the PluginSDK... if possible, can you revert back to 4.1.6.0 through a backup?

    ​​​​​​​Wim
    -- Wim

    Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

    1210 devices/features ---- 392 events ----- 40 scripts

    Comment


      #17
      Tested the upgrade here to 4.1.7.0 and for me it worked fine so far, no error. the more interesting is it to find the device that is causing the error in PluginSDK. Some special device?

      Wim
      -- Wim

      Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

      1210 devices/features ---- 392 events ----- 40 scripts

      Comment


        #18
        gaf@bluerivernet.com

        We have tested a solution for this. It is some issue with the pluginSDK, we have not been able to really put the finger on the issue that pluginSDK is having other then that it is confusing features. But if you delete the device with the reference 1398 the problem is solved. The plugin will recreate the device and run normally after that.

        Wim
        -- Wim

        Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

        1210 devices/features ---- 392 events ----- 40 scripts

        Comment

        Working...
        X