Announcement

Collapse
No announcement yet.

(updatesensors):start: the given key was not present in the dictionary

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

    (updatesensors):start: the given key was not present in the dictionary


    #2
    Xian,

    Could you send me a trace of what is going on?
    • Set detailed trace and logging to file in the configuration page/trace options
    • Restart the plugin and let it run for say 15 minutes
    • Disable the detailed trace and logging to file in the configuration page
    • Send me the \logs\JowiHue.log file?


    Send the log to w dot vuyk at upcmail dot nl?

    Thanks,

    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


      #3
      Thanks, I have just sent you an email

      Comment


        #4
        Thanks to the trace Xian send me I found that the action Xian did, updating the NWK id, causes sensors (maybe also lights) to change their ID as well. The plugin does not expect the sensor to change its id internal on a gateway.

        So this caused an issue here that I have to find. I am on it, but the solution takes time. In the mean time.. do not change the NWK id in deCONZ or know this can happen.

        Wim

        *edit* still working on this, it might be different then I expected...
        Last edited by w.vuyk; March 19, 2018, 05:30 AM. Reason: extra info
        -- 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