Well that’s down to Brian to resolve it. This is the only way now with new devices to gather all data.
Stuart
1 Like
Tx again Guys.
Bits - your right on. The left side does contain the lds01 data when the wittboy option is there. I just never could see it because it extends beyond the 1st and only line of output It takes a bit of finagaling but when i check the wittboy option on the left side of the chron output and cut / paste that into a txt file I can see the data But like you said it does not show on the right side.
Stuart,
I have been using the livedata option to display the “actual output” of the GW2000. For give my ignorance - but is this what you call the HTTP API?
Feedback wise - I originally tested the wittboy option with the checkmark and without restarting wd. So I did a restart but doesn’t change the results. For what it’s worth - checking or unchecking wittboy changes the output immediately without a restart of wd is the results I’m seeing.
.
So is the data (left side) that’s displayed in Brians cron job reflected in any of the txt files like clientraw.txt. Of course trying to extropolate that would not be fun. So is a 3rd instance of wd my only solution to get my 8 wh31’s along with lds01 data in order to populate my two webpages the only way to pull this off. And of course I’m still at Brians mercy to actually create tags that have it?
Good to know 
The cron left side is the raw data in json format. AFAIK only the right-side data from the cron job have been parsed by WD. . . so extratemp/hum1-3 will end up in clientraw.txt, for instance. I have no idea how LDS01 data is used by WD: is it shown on the main screen? I just checked a tagslist from 18 February download and I can’t see any snow/laser tags, either. . . Data certainly won’t be in clientraw*.txt as they are set in stone.
Here’s my cron data:
(BTW I don’t have piezo rain. . . 
)
Thanks for this, explains a lot. I just wish he would post any problems on the Forum so we would all know when not to bother him.
Indeed, some communication would be nice. I got a test version the other day with a note he was at a funeral, but try this… The test was not successful.
I switched over to the http pull on my GW1100 and the data looked fine in the right window, but in WD i had a rain rate of 455 inch/hr. That’s a lot of rain! The rest of the rain values remained correct. Reading the raw http directly in a browser showed: " { “id”: “0x0E”, “val”: “0.00 in/Hr” }" so how WD came up with 455 in/hr is a bit puzzling. We live in a mysterious world…
Jim
The standard cron job without the Wittboy being ticked uses what is now called the binary API and really is almost legacy in that it is not updated with the data from things like the Laser sensor or much of the IOT (Internet Of Things) stuff like the programmable switches and water taps etc.
The HTTP API is the way forwards, the binary API is fine if you only have basic weather sensors but even that may change in the future. Although the binary API does currently work on all gateways including the latest GW3000 it is unlikely to get updates except for bug fixes and only displays the weather sensors.
To be honest if you use any Ecowitt equipment whatever software you use I’d suggest registering on the WXForum and in particular follow the board on there called Ambient Weather and Ecowitt and other Fine Offset clones where you will find a whole slew of information about Ecowitt and their kit including a very informative Wiki linked from that board and is well worth a browse.
Stuart