First of all, this is an incredibly useful plugin! The approach for scenes and them profiles within scenes is wonderful; especially for implementing different dim and device combinations throughout the day as lighting and family patterns change, timed overrides for occupancy or "door open" events. All very nice. And the "<No Change>" action is a great addition.
I have the 1.3.2.0 beta up and it mainly seems to be doing fine, but I'm getting a few logged errors I can't track down. Examples below.
This is new system and so I've moved around a few devices here and there. But I can't find the correlation as to what the cause it. These seem to come while some other actions are underway but not particularly related to anything being demanded of SceneMaster.
The second issue, for the SceneMaster designer at any case, seems to get confused on it's database (perhaps from the caching changes?). The issues I've had were:
a) when trying to select a specific profile, the wrong one came up for editing.
b) the entire scene database seemed to go missing.
Restarting the plugin correct both issues for a while.
Cheers,
Don R
I have the 1.3.2.0 beta up and it mainly seems to be doing fine, but I'm getting a few logged errors I can't track down. Examples below.
Aug-02 2:45:58 PM | SceneMaster | Device 733902746 added but could not be accessed by plugin |
Aug-02 2:29:34 PM | SceneMaster | Device 521560557 added but could not be accessed by plugin |
Aug-02 2:05:39 PM | SceneMaster | Device 2062616413 added but could not be accessed by plugin |
The second issue, for the SceneMaster designer at any case, seems to get confused on it's database (perhaps from the caching changes?). The issues I've had were:
a) when trying to select a specific profile, the wrong one came up for editing.
b) the entire scene database seemed to go missing.
Restarting the plugin correct both issues for a while.
Cheers,
Don R
Comment