- Thu Dec 25, 2014 5:22 pm
#5703
Well, no guarantees as I've only done a short amount of testing... but running the version on the 0.9.4 binaries - not only does the NTP work.. but it looks like other functions work just fine as I have this running with my Android APP..
We really DO need a consistent interface for the new commands - i.e. OK for good and something like ERROR for bad at the end of the messages put out when you send commands - that would allow us to use similar checking logic for most commands....
As you are obviously in full command of the source code - is it worth a few minutes to change the somewhat chinese responses such as "no is fun" to ERROR or again something consistent... also "busy s..." means nothing... possible to make that just "busy"... and do you know what that even means as I don't... if you get busy are you supposed to wait or try the command again?
Any information would be great - I KNOW I am not the only one struggling with this...
Excellent work so far. Incidentally, the NTP servers are great but they don't give another useful function... light up and dawn times. I ended up writing my own PHP page which I access to get this along with time and date... also.... it would be GREAT when you return the time and date if you could also return the one LONG Linux timestamp that the likes of ARDUINO use to set up the clock - because I can imagine the main use for your NTP stuff will be to do just that - set up an Arduino or other clock which takes in the LONG time (seconds since Jan 1974 I think).
Tomer wrote:I updated the original message with link to binaries compiled with SDK 0.9.4.
