The reason I choose to parse only the data from the web page was because it provided more information about the device itself including the response status (HTTP Code) received from uRADMonitor server. Keeping the labels somewhat consistent would be nice.

P.S. Many thanks for the samples from A3 unit.

Hi, @radhoo.

I found that some city names have bad encoding in the JSON data published here:
“id”:”1100000E”, “city”:”Timi?oara” (this also occurs for other ids)
“id”:”12000045″,”city”:”KC4%97dainiai”.

• This reply was modified 8 years, 10 months ago by cristianst85 (nox).

Howdy everyone!

I’ve just released a new version (1.1.0) of the application.

Two new features were added: Check for Updates and Data logging. Also, starting with version 1.x .NET 4.0 is required.

Mads Barnkob, probably the culprit is an older firmware. My application works only if your device exposes the readings via an web page (see: requirements for uRADMonitorX)

The solution is (if possible) to upgrade your firmware to version 110 at least (also check the Firmware Upgrade Guide).

• This reply was modified 9 years, 4 months ago by cristianst85 (nox).

I’ve released a new version (0.40.0) that should work better with Wine/Mono.
My test environment is openSUSE 13.2 (x86_64)/KDE4/Mono 3.8.0.