Indigo Domotics

On my sense I had dryer and dryer1 (or Dryer2 - I can't remember). On the sense control panel I merged those two dryers since I only have one. Then in indigo I deleted the extra dryer. Started to see this in the log every few seconds. Help

PS. Restarting Sense plug-in does not fix..

Code: Select all

   Sense Debug                     Active: 1220.26394893w
   Sense Debug                     Daily: 3.8793838kw
   Sense Debug                     CSV Output: 2019-06-02 06:33:18.983720,1220
   Sense Debug                     CREATED: Dryer
   Sense Error                     NameNotUniqueError
   Disabling plugin "Sense 1.0.4"
   Stopping plugin "Sense 1.0.4" (pid 68002)
   Sense Debug                     shutdown called
   Stopped plugin "Sense 1.0.4"

Tossing out the sense csv file and having the plug-in restart and make a new csv did not help...

I disabled the plug-in and then deleted the sense plug-in dryer device. Restarted the plug-in and it created a new dryer device - that seems to have fixed it!

Spoke too soon - error is back and the newly created dryer drive is missing the power symbol ....

Code: Select all

   Sense                           Debug logging enabled
   Sense Debug                     Rate limit is: 30
   Sense Debug                     Active: 2849.70836728w
   Sense Debug                     Daily: 5.697364kw
   Sense Debug                     CSV Output: 2019-06-02 07:39:48.065153,2849
   Sense Debug                     CREATED: Dryer
   Sense Error                     NameNotUniqueError

Reloading the plug-in seems to have corrected the device and the error has stopped?

Did you delete (online) the dryer, and rename dryer2 to dryer?

NameNotUnique is trying to create the device because plugin doesn’t know about it - which means the Sense device id isn’t known to the plugin.

If you delete a device in Indigo (dryer2) it removes the id from its own list, so if you’d renamed dryer2 to dryer that would explain the situation.

(Renaming a device in Sense is handled ok in the plugin, I tested that, so this is only way I can think of causing this problem)


Sent from my iPhone using Tapatalk Pro

It is working great now and to be honest I would not bet my life on exactly what I did (it was yesterday late) - but good info from you on how to handle it next time and how the plug-in works - Thanks