Just installed a new LDS01. Has anyone heard or contacted Brian to know if he plans on supporting it. I’m at V10.37S152 and the Chron GW1000 V7.2 does not report it. As a result I doubt if there are any tags neither which I need to complete the new wxlocalnn / wxnn webpage I put together?
Latest version of cron (7.6) does support LDS01. See also version history:
But I too doubt if there any tags yet. . . you’ll have to ask Brian.
EDIT: For those who need extratemp/extrahum, the latest crongw1000 includes HTTP support for up to 3 devices. The tags are already in tagslist.
Bear in mind that many new devices only appear when using the HTTP local API and not the old telnet (now known as binary) API as this binary API will eventually be deprecated!
Stuart
Just to be clear, Stuart, this is where you check the gw1000cron option “Wittboy/GW2000 in use (uses HTTP) - Use for snow depth”
I think you can use this option with a GW1000/GW1100/GW1200 too?
Not with the GW1000 but OK with all the others. GW1000 is unlikely to get support for any news stuff, it is not even sold now I think.
Stuart
1 Like
Can you give us the URL or is it private?
tx. I’ll reply to each. I haven’t made the new webpage live yet since it’s not complete but here is what’s kinda of going thru my mind. It’s basically the same as my thermostat page. https://lvpoa.net/lvweather/wx11.html but wx12.html I have visions of making the water level on the “measuring stick” correspond to the actual water level as taken off of a tag + a little creative scripting to recaculate to the actual water level which is presently 789’4". Unfortunatly I’m not an experienced coder though.
I’m also inexperienced with forums. Just had a forum suggestion that I respond to all feedback with a single so heres the next response to Stuart.
I wasn’t aware Brian was getting to that point of dropping support. And I just started registered and started using it. Goal was to get the heck off of VWS.
Back to Bits
Ok I found the version history. And I see where it says support has been added.
Could you enlighten me as to what this means as it pertains to updates. In other words the “product” that I’m under the impression that is most current is build 2025 10.37S Build 152. Does this mean that Brian will do updates but not change this build level designation? How does one know what build level is the latest if this is the case?
I haven’t crossed the road to the side that deals with API. I have been seeing / reading that it seems like everything is going that way. Just not there yet. I do everything local so I don’t have to depend on someone holding my data for me. Especially when the host disappears off of the map. If this makes sense to you. Of course we won’t get into Trump trying to dispose of NOAA data.
am I to interrupt from this that cron can be updated independently from the wd version itself. I’m new to wd and I was unaware of this possible capability. I’ve been on the wd download page and if it’s there I’m missing it. I only see the wd download itself. some insight would obviously be appreciated. The news on the right side indicates Version 10.37S Build 152. Which is what I’m at. My corresponding
We don’t know. . . Brian updates WD but doesn’t change the build number and doesn’t tell us why.
Just use the latest download from his site – who knows, there might be a later version of crongw1000 already 
lvpoa.net took too long to respond
Tx bits. It’s all too obvious that you know WD all too well from all of your previous responses I’ve read. I don’t know if you recall but I had some major issues with WD not doing what I thought it was suppose to do. I emailed Brian a couple of times but never received any assistance. So I ended up removing everything including doing manual registry updates and reinstalled on a different drive. Viola all of the issues went away and I was then getting the corresponding tags updated and brought across. That’s why my version (WX10) of the GW2000 webgui is now working.
So is there a way to tell when Brian does update WD if he doesn’t so indicate. I’ve yet to see a posting that it’s happened. Maybe your buddy buddy and as a result of all the help you give your just in the know? As long as I have you on the rope, I’ve been encountering an almost daily occurence of my GW000B going to lunch. I have to do a POPO to reset it and then it works fine for a day or two. I’ve seen this talked about on WXForum but haven’t seen any resolution. Bad unit? Bad Firmware(I’m uptodate)?
Tx.
NOTE:
Forget the question on updating of WD. I decided to download it and compare against my current copy. I discovered that he has a date - March 9, 2025. It’s downloading as we speak.
I do, I said it was like reading a dictionary because you lose the plot in the mass of detail 
No, just check the date/time on the download page (like you just did!) 
Which one? If you have a GW1000 you won’t get snow depth, as Stuart explained. You have to be able to check the “Wittboy/GW2000 in use” option in crongw1000.
I don’t think that’s what he meant. I assume he meant that as the GW1000 is now ‘old’ hardware it’s less likely that Ecowitt will add new features to it
1 Like
Hi
I have spoke to brian the other day and he has had family issue at the moment, so might not reply quickly.
He still updates WD but doesnt put the updates in place as to what he has updated.
Im waiting for him to update a tag for me, so i think he will update it when he can
Yes I that is exactly what I meant.
As for Ecowitt support it is widely believed that they are moving away from the binary (telnet) api and need people to start using the local HTTP API and this is why the GW1000 is now not recommended because it does not support that HTTP API.
Brian will need to fully support this HTTP API for all gateways in future not just the Wittboy/GW2000.
Stuart
1 Like
Hey guys, as a WD newbe I can’t stress enough how much I appreciate your time and knowledge. Here’s what I can tell you so far since yesterday.
Bits,
Sorry but I noticed a typo I have the GW2000B. I had to reset it again last night.
Nervous as I was about it, I did reinstall WD. Both instances, even thought I’ve yet to start using the 1st one. Chron 7.6 is now functional. image below,
You’ll notice there’s not data from Chron that pertains to the LDS01.
Based on my dealing with install/config of wd in the past, I kinda of knew that checking the “Wittboy/GW2000 in use (uses HTTP) - Use for snow depth” option was not going to work. But I tried it anyway. And I confirmed that when I do - that I lose nearly all of the temperature / humidty data for my 8 sensors. Alsothere was still nothing reported for the LDS01.
Broadstairs/Stuart/Chris, Tx for Clarifying that losing support only pertained to the GW1000. Comforting to know.
I’ve attached a couple of pics. One show my “temporary” siting for the LDS01. Basically a Sterling wallyworld plastic box. My LDS01 is down at the lake and I’m getting 4 bars signal strength. It’s about 100’ downhill from the house. My GW2000B is in the basement so I’m going thru 1@ 8" block wall. For anyone curious.
Yes you will not see the Laser sensor as the cron job is using the binary API. I think the options Brian (WD author) has called Wittboy/GW2000 is what uses the HTTP API so try that because if I’m correct and it uses the HTTP API that is the only way to see the Laser sensor will show up, hopefully with all the others.
I no longer use WD so am rapidly losing touch with it 
Stuart
Hey, you’re really pushing the envelope here. . .
As I said, Brian has only just got round to providing support for 3 extratemp/hum devices using the HTTP-get method, because I asked him to a few weeks ago.
Sorry I know nowt about support for the LDS01 beyond what Brian tells us, but as Stuart says you are not using the HTTP API yet. You may have to restart WD after checking the GW2000/snow box. . .
And then you will probably have a choice: to see all extratemp sensors with the old API; or only 3 plus the LDS01 with the new API 
The HTTP API has been around since the GW1100 so it should have been implemented in full a while ago. This API does show all sensors so WD should see them however if it will is unknown to me. You can see the output yourself by accessing your gateway by issuing
http://192.168.0.1/get_livedata_info? replacing the 192.168.0.1 with the IP address of your gateway.
As I said I have no idea how WD will process this. The output is in JSON format.
Stuart
The cron raw data (left column) will show all the sensors but WD data (right column) will not. . .