Adri,

Just to confirm that I've tried this from a remote Python script and it is broken there as well!!! (So it isn't just the Swagger page that has a problem...)

As we can get the data for an individual device by digging it out of the "all devices" stuff, it's a [low prioirity?] nuisance rather than a show-stopper, but hopefully it'll get fixed at some point.

Cheers - Al.

It took me a total of 2 weeks to rewrite all the scripts(*) and then 1 week to fine-tune them after the website was changed.

(*) Actually, only 2 scripts needed rewriting ('wcgformat' and 'wcgstats') and it was fun to add some functionality to 1 script ('wcgresults').

Calling writing computer programs (which is my job) 'creating kludges' is an insult in my eyes. I can deal with that, although it's not fair.

Two things.
The programs and websites that people are offering have been produced because people wanted to create something, based on the available data and on their view how data should be represented.
The helpful hints that people are offering have been given because they want to help others.

When technology behind a website changes, things can't always remain the same. The choice can't always be 'keep everything working like the way it used to'. Like evolution, we have to adapt to 'survive'. If you don't, your website or program stops working or will fail in some way.

As for me, I have been writing programs - using the available data - to be able to look at things in a certain way. I have been offering programs to others. In certain circumstances they are useful. So, to me, calling them 'kludges', well, it is disappointing, because, for me it is creativity, trying to solve the puzzle, battling the changes. And when I finally, at last, succeed in that, victory! And with a victorious feeling I sometimes fail to see the big frustration, when I want to help. But that's me.


And hey, if they don't want the help that I'm offering, maybe they should try to find a solution for their problem somewhere else. That's not my problem, I don't get paid for it, you see. Besides, they make their own choice how they solve their problem. It's up to them.

Not only that, I also mentioned at least two other solutions (with links).

In my first post in this thread I wrote:
The outcome then was that the amounts of runtime, points and results didn't match, in fact they were represented as being zero at that time in the '{id}' case.

I've just checked it again and the values are now showing the correct values in the device-api with the {id} at the end.

Bravo and thanks, techs!

Adri

Yes, you did.


Wikipedia describes it as: "A kludge or kluge is a workaround or quick-and-dirty solution that is clumsy, inelegant, inefficient, difficult to extend and hard to maintain."
I've always known the Wikipedia meaning of the word since I learnt English.

Oxford ODE: "/klʌdʒ, kluːdʒ/ informal ▶noun · an ill-assorted collection of parts assembled to fulfil a particular purpose. ■Computing a machine, system, or program that has been badly put together, especially a clumsy but temporarily effective solution to a particular fault or problem. ▶verb [with obj.] · improvise or put together from an ill-assorted collection of parts. Hugh had to kludge something together. – origin 1960s: invented word, perhaps influenced by bodge and fudge."


Glad that you look at it that way, too, Bobby.


I believe that's not the way how I work. If something doesn't work and I don't get it to work, I will search for a solution, and then when I get it to work, I want to understand what was wrong about it, because I want to learn from my mistake and hope to remember it.


Adri