It's clear that the log is in the cloud. And every couple of weeks there's some kind of server problem (at the start of each month, guaranteed) and the log disappears. Worse still, if you want to obtain the value of certain attributes of certain devices, it seems clear that the value comes from the log. So if the log is down, you can't send that value in an email to create your own log, either. One example is awnings that only operate in summer. Once summer is over, the awning position value stops changing and it drops out of the log, because the log only records changes and only stretches back a few weeks. Once the value isn't in the log, if you attempt to send the position of the awning in an HTTP request you just get garbage.
It's clear that the log is in the cloud. And every couple of weeks there's some kind of server problem (at the start of each month, guaranteed) and the log disappears. Worse still, if you want to obtain the value of certain attributes of certain devices, it seems clear that the value comes from the log. So if the log is down, you can't send that value in an email to create your own log, either. One example is awnings that only operate in summer. Once summer is over, the awning position value stops changing and it drops out of the log, because the log only records changes and only stretches back a few weeks. Once the value isn't in the log, if you attempt to send the position of the awning in an HTTP request you just get garbage.
Today's case is a bit weirder because if I click "latest" I get a list of recent events. But if I consult the log for a particular device, it stops at 4:15. So I'm guessing that that "latest" is stored locally, and the log is stored in the cloud.
Today's case is a bit weirder because if I click "latest" I get a list of recent events. But if I consult the log for a particular device, it stops at 4:15. So I'm guessing that that "latest" is stored locally, and the log is stored in the cloud.
The same problem 
Same problem.
Same problem.
Same problem here
Same problem here
It's clear that the log is in the cloud. And every couple of weeks there's some kind of server problem (at the start of each month, guaranteed) and the log disappears. Worse still, if you want to obtain the value of certain attributes of certain devices, it seems clear that the value comes from the log. So if the log is down, you can't send that value in an email to create your own log, either. One example is awnings that only operate in summer. Once summer is over, the awning position value stops changing and it drops out of the log, because the log only records changes and only stretches back a few weeks. Once the value isn't in the log, if you attempt to send the position of the awning in an HTTP request you just get garbage.
It's clear that the log is in the cloud. And every couple of weeks there's some kind of server problem (at the start of each month, guaranteed) and the log disappears. Worse still, if you want to obtain the value of certain attributes of certain devices, it seems clear that the value comes from the log. So if the log is down, you can't send that value in an email to create your own log, either. One example is awnings that only operate in summer. Once summer is over, the awning position value stops changing and it drops out of the log, because the log only records changes and only stretches back a few weeks. Once the value isn't in the log, if you attempt to send the position of the awning in an HTTP request you just get garbage.
Today's case is a bit weirder because if I click "latest" I get a list of recent events. But if I consult the log for a particular device, it stops at 4:15. So I'm guessing that that "latest" is stored locally, and the log is stored in the cloud.
Today's case is a bit weirder because if I click "latest" I get a list of recent events. But if I consult the log for a particular device, it stops at 4:15. So I'm guessing that that "latest" is stored locally, and the log is stored in the cloud.
Yep, the log is consistently lagging around 12 hours behind the current time.
How do you see events on the mobile? iPhone or Android? On Android I don't think they're available.
On the web interface the events are in the bottom section on the left, where the little notebook icon is.
Yep, the log is consistently lagging around 12 hours behind the current time.
How do you see events on the mobile? iPhone or Android? On Android I don't think they're available.
On the web interface the events are in the bottom section on the left, where the little notebook icon is.
Replies have been locked on this page!