You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to use this timestamp (unixtime?) to give as info to homekit. I'm not sure where/how to send it to homekit...
{"id":"9044149","name":"Garage inne","lastUpdated":1478118807,"ignored":0,"client":"130828","clientName":"Torodd1","online":"1","editable":1,"battery":254,"keepHistory":0,"protocol":"fineoffset","model":"temperaturehumidity","sensorId":"231"}
The text was updated successfully, but these errors were encountered:
Hmm, I was assuming it existed, but it may be only as internally registered time from receiving an update. The CurrentTime I believe is for setting the internal real time clock of accessories, for their own timestamp when logging time-series of data.
In this case maybe it could use the timestamp to save and check if the data is newer than the last sent, and don't resend it if it was the same, and then the homekit app on iOS will mark it as not updated.
Is it possible to use this timestamp (unixtime?) to give as info to homekit. I'm not sure where/how to send it to homekit...
{"id":"9044149","name":"Garage inne","lastUpdated":1478118807,"ignored":0,"client":"130828","clientName":"Torodd1","online":"1","editable":1,"battery":254,"keepHistory":0,"protocol":"fineoffset","model":"temperaturehumidity","sensorId":"231"}
The text was updated successfully, but these errors were encountered: