This object is in archive!
Zipato: HTTP UUID format in new firmware
Need Answer
Will the current method of setting meter values via HTTP POST continue to be supported in future, i.e.:
?
Some are saying that now each meter attribute will have its own UUID. That means that each attribute would need to be updated by a HTTP call individually.
I have Google App Scripts that make frequent updates to many meters during the day. That amounts to maybe a couple of thousand HTTP calls in total. If I have to multiply that number by sixteen, I'm going to rapidly blow past the 20,000 daily URL fetch limit. Not to mention the enormous increase in the running time of the scripts, which is liable to break yet another GaS limit.
The same question
No connection
Real-time notifications may not work
Replies have been locked on this page!