12-15-2019, 08:20 AM
It's complaining that the driver is not connected to the device, so the attempt to write the value fails. Is the Caseta driver cycling by any chance? If that happens, sometimes you'll happen to catch it while it's up and sometimes while it's down.
Bring up a driver monitor tab for the Caseta and see if it is clearly cycling (i.e. on some fairly short time frame.) Also, right click on and it look at the stats, and see if the lost connections and such are running up. In a perfect world, there would be zero lost connections. If it's a fairly high number, then the driver is cycling though maybe just not often enough for you to notice it while watching.
It may also be that something else happening just before that particular scheduled event causes it to cycle so that it's always unavailable at that time. If you put the driver into low verbosity and clear the logs, let it run for a bit and you should see msgs about it losing and regaining the connection.
Bring up a driver monitor tab for the Caseta and see if it is clearly cycling (i.e. on some fairly short time frame.) Also, right click on and it look at the stats, and see if the lost connections and such are running up. In a perfect world, there would be zero lost connections. If it's a fairly high number, then the driver is cycling though maybe just not often enough for you to notice it while watching.
It may also be that something else happening just before that particular scheduled event causes it to cycle so that it's always unavailable at that time. If you put the driver into low verbosity and clear the logs, let it run for a bit and you should see msgs about it losing and regaining the connection.
Dean Roddey
Explorans limites defectum
Explorans limites defectum