I've got 3 hours trying to get this config'd, and find that I'm stuck in a loop using diff internet help without resolution:
I'm trying to install the Ambient WS-2000 onto my C-8 Pro. I've D/L and installed the package manager and created a new virtual device, using driver "AmbientEcowittWeather".
No matter what parameter I enter choose, I cannot get "Weather Method" to stop being red. Changing that to Live Data Scrape, IP Address/HN of ObserverIP will not clear from being red. (I don't know what the observerIP is, even after repeated internet searches)
WS-2000 appears to be config'd correctly with Hubitat IP, port, path. IP from my wireless router is known.
I hit a brick wall, so any help would be appreciated.
EDIT: refusing to give up: using the WSView Plus just complicated things for several more hours, as the app just refused to show the wifi, or any wifi, even after selecting diff consoles. This led me to read reports about issues with the wifi chip of the WS-2000. I gave up, and created an AMBWeather account, and was able to see (cloud data) displayed on a dashboard.
I want to use LOCAL, so I deleted everything, and started over without using the WS-2000 wifi or WSView app. I now have a LOCAL config with a dashboard showing my weather, albeit limited fields using EZ or Hubitat dashboards.
I don’t recall that it does, but it is what I use with my WS-2000 unit, which of course uses the Internet if you want to monitor your unit via cell phone.
I just successfully installed a virtual device with driver "AmbientEcowittWeather" for my Ambient WAS-2000.
I downloaded the WS View app for iPhone and went through the config instructions from the AmbientEcowittWeather driver (lines 17-27 in the driver, substituting "Ambient" for "Ecowitt").
On the Hubitat side, I selected "Ambient Local" as the Weather Method (the title never changes to a different color from red).
The "tricky" part for me was realizing that the network ID was editable. Once I figured that out, I inserted the all-caps, no colons, MAC number for my WAS-2000, saved, hit the Refresh command, and refreshed the browser: data appeared!
The AWS driver shows air pressure in hPa*, which I prefer, with all other units being standard American "English" units. The AWS driver also generates many more Current State values. But, it's not local. One nice thing about the AEW driver is that it creates child devices for remote sensors rather than separate parent devices.
[Tthere is a mistake in the associated AWS documentation, which says the pressure units are inHg]
EDIT: Actually, the AWS driver may just be reporting the value received from the WS-2000 in default units of inHg; the WS-2000 app allows fine grained selection of units, and I chose hPa which the AWS driver reports in its barometric pressure fields. <-- that's ALL wrong: the AWS app associated with the AWS driver allows granular selection of units and when picking hPa, simply does not change the field name or field definition from inHg.
thanks for your help. I've exhausted what is a reasonable amount of time to get this work:
I had to install 'WS View "PLUS"" on my android tablet to even see what resembles the ws2000, therefore the config instructions you mentioned are non existent. The app is locked into "IP configuration" and I cannot find how to change that to wireless even after performing a factory reset, and the ws-2000 is connected to my wireless router; the app does not recognize the SSID.
Thanks again, and don't worry about replying, 6 hours trying to do this is enough.
Is the device still broadcasting the setup SSID? I seem to recall that there was an option to disable that once connected. However, if it is till broadcasting the setup IP, you may need to connect to that one again to unlock WSView plus.
If you go into the device list, and click more -> Device Setting, check and see if the disable AP button is on.
If so, you can always post questions (if it does not get answered here) to that main thread.
Red labeled fields in the Preferences for the driver are just one of the things I do to help identify required fields. It does not indicate a problem with that field. But, it sounds like you are getting caught on the "custom" reporting you need to set the weather station to do, so it can send the data to the Hubitat locally. @stephen_nutt just posted about that as I was editing this...
Try just going to device's IP address in a browser. You should be able to turn WLAN on/off. Mine is using ethernet. It's not same PW as the app; I think it starts w/out a pw for admin user.
Mine is currently integrated to HA so this isn't exactly the same to connect to Hubitat but close. I know the path is different for Hubitat and I believe the port is different also.
Per @stephen_nutt's post... The settings for Hubitat are:
Server IP/Hostname = Your Hubitat's IP/Hostname (IP is generally best)
Path = data/report/ (This should be the default value)
Port = 39501
I updated the EcoWitt driver to o forward the data on to another destination, which allowed me to forward it to HA. I would expect you could do the same with this driver.
You know, in all this time nobody has ever asked me to forward the data from my driver... Obviously if @sburke781 did, then it is possible. That could solve @stephen_nutt's wish also (although I think that would still be better done from the weather station).
@stephen_nutt: Well, I am adding in a forwarding capability. Testing it now by forwarding from one Hubitat to another... If you are willing to try it out, I can shoot you a link to a sample version once I have it at least working between Hubitats.
Ok, my AmbientEcowittWeather has been updated to include the ability to forward the data from any of the methods it supports, Ambient API, Ambient Local, Ecowitt Local, and Live Data Scrape (should work, but I lack the Observer IP to test it but the rest are tested). It forwards all of them as if the data was coming from an Ecowitt Local.
Sorry to hijack your thread @mike_shields2010. Did you get your weather station working in the end?
