- Code: Select all
(604, u'2014-12-21 16:24:39', u'True')
(605, u'2014-12-22 07:13:19', u'False')
(606, u'2014-12-22 16:25:09', u'True')
(607, u'2014-12-23 07:13:49', u'False')
(608, u'2014-12-23 16:25:42', u'True')
(609, u'2014-12-24 07:14:14', u'False')
(610, u'2014-12-24 16:26:16', u'True')
(611, u'2014-12-25 07:14:39', u'False')
(612, u'2014-12-25 10:58:57', u'False')
(613, u'2014-12-25 16:26:52', u'True')
(614, u'2014-12-26 06:45:46', u'True')
(615, u'2014-12-26 07:15:01', u'False')
(616, u'2014-12-26 16:27:31', u'True')
(617, u'2014-12-27 07:15:21', u'False')
(618, u'2014-12-27 11:06:45', u'False')
(619, u'2014-12-27 16:28:12', u'True')
(620, u'2014-12-28 07:16:11', u'False')
(621, u'2014-12-28 08:06:13', u'False')
(622, u'2014-12-28 16:28:55', u'True')
(623, u'2014-12-29 05:29:20', u'True')
2014-12-28 16:28:55 | True
2014-12-29 05:29:20 | True
It's true that the light is switched on at 16:28 and is still on at 05:29, but it's not clear to me why SQLogger is writing that second row. Shouldn't the plugin be waiting for the next state change?
Dave