openambitproject / openambit

openambit
280 stars 82 forks source link

log don't srynchronise to movescount #66

Closed LanglaisMickael closed 9 years ago

LanglaisMickael commented 9 years ago

Hello,

I am trying to upload my logs using openambit. I have the following error in the console : Failed to upload log, movescount.com replied with " ""Device creation not allowed. Suunto devices must be created by POSTing a new UserDevice."" " After configuring my email adress linked to my movescount, a link in the gui openambit appears to connect to the movescount.com and validate the authorization for the connection. After that the link disappear in the gui, the error message appear in the console and my logs do not synchronise. Maybe there is a time latency for movescount to be updated with this new connexion...

Does anyone already encountered such issue ?

Thanks in advance best regards Mickael.

benedetto commented 9 years ago

Is this the first time ever that you sync your watch?

Without having seen this error yet, it sounds like the watch was not registered to movescount yet and I guess that openambit isn't able to do this step (yet). Therefore, you will quite surely need a moveslink installation for the initial configuration of your watch (and at the moment also every now and then if you want to change watch parameters that are not accessible through the watch's menu, as openambit cannot do those settings yet).

If you do this initial configuration, it would be great if you could record the communication that happens between the watch and movescount at this process, maybe it is of use somehow. You find a tutorial how to record this communication here: http://openambit.org/wireshark-dissector/

marguslt commented 9 years ago

To capture RESTful https chatter going on between ml <-> mc, debugging proxies are safer bet -http://www.telerik.com/fiddler/web-traffic-recording (tested, works like a charm, I'm just not too eager to remove watch from mc)

svenstorp commented 9 years ago

I am assuming this is an issue as described by @benedetto. I have created an issue (#73) describing the "register new device" feature