I saw that, and considered it. But, in addition to my WS-1401-IP, I also want the data from my WS-8482, which I use to measure conditions in my garden (hoping soil moisture sensor will be available soon).
The easiest way to get timely data from both devices is to use the API to get the real-time event stream from ambientweather.net.
I reported this further up in this thread. The binding currently does not update the thing config when a parameter value is changed. You could manually change it in the jsondb. You need to stop OH before making the change or your edit will be lost.
True. The binding also could implement UoM, which let’s the framework take care of the unit conversion based on the locale.
I found and fixed a bug that stops the channels updating, due to the thing being offline when it updates the channels for the first time and hence you had to wait for a value to change to finally get shown. With rain not occurring every day this was a big issue as channels had zero values after a restart… Bug is now fixed and few other changes have been made, works great.
I have now been scraping for 24 hours scraping at 60 second intervals, and then a further 36 hours scraping at 20 seconds apart. No stability issues seen and it takes 380ms to fetch the livedata even after days I have not seen the value rise. Going to look at adding the ability to restart the hardware via the binding and then I can share the JAR with anyone wanting to help test the new changes.
Weather stations that should work are:
WS-0900
WS-1400
WS-1550-IP
WS-2902A (if you add on the ip Observer)
WH-2950 (if you add on the ip Observer)
Plus any others that come with the IP Observer
You can add an IP Observers onto your setup if your outdoor unit is compatible and still keep your normal screen working at the same time.
To upgrade you need to remove the old Jar and place this one into the addons folder (after unzipping). Then remove any old ‘things’ and re-add the weatherstation ‘thing’ using PaperUI or the textual config at bottom of this post.
Quick list of changes are:
UV index channel fix.
Now waits until unit is ONLINE before trying to update channels which was causing missing info.
Can reboot the unit manually via a switch, or using an openhab rule, or also it is possible to auto reboot.
Displays the web delay when fetching the livedata.
Refresh time is now easily changed.
Should be easier to run ‘mvn clean install’ with less errors and warnings.
Removed unit labels as these can be added easily by user by adding labels in sitemap or item definitions.
Timestamp of last update scraped from livedata.
@captndelta
Please contact me so I can provide the changes to the code I have made. A big thank you for making this binding.
@mhilbush Thanks for helping with the url for doing a reboot.
@shorty707
Since you have the original binding working it would be great if you could test these changes.
Number WeatherOutdoorTemp "Outdoor Temp (°C)" {channel="ambientweather1400ip:weatherstation:Weather1:outdoor_temp"}
Number WeatherOutdoorHumidity "Outdoor Humidity" {channel="ambientweather1400ip:weatherstation:Weather1:outdoor_humidity"}
Number WeatherWindDir "Wind Direction" {channel="ambientweather1400ip:weatherstation:Weather1:wind_direction"}
Number WeatherWindSpeed "Wind Speed" {channel="ambientweather1400ip:weatherstation:Weather1:wind_speed"}
Number WeatherWindGust "Wind Gust" {channel="ambientweather1400ip:weatherstation:Weather1:wind_gust"}
Number WeatherSolarRad "Solar Radiation" {channel="ambientweather1400ip:weatherstation:Weather1:solar_radiation"}
Number WeatherUV "UV" {channel="ambientweather1400ip:weatherstation:Weather1:uv"}
Number WeatherUVIndex "UV Index" {channel="ambientweather1400ip:weatherstation:Weather1:uvi"}
Number WeatherRainHourly "Rain Hourly (mm)" {channel="ambientweather1400ip:weatherstation:Weather1:hourly_rain"}
Number WeatherRainDaily "Rain Last 24 hours (mm)" {channel="ambientweather1400ip:weatherstation:Weather1:daily_rain"}
Number WeatherRainWeekly "Rain this week (mm)" {channel="ambientweather1400ip:weatherstation:Weather1:weekly_rain"}
Number WeatherRainMonthly "Rain this month (mm)" {channel="ambientweather1400ip:weatherstation:Weather1:monthly_rain"}
Number WeatherRainYearly "Rain this year (mm)" {channel="ambientweather1400ip:weatherstation:Weather1:yearly_rain"}
String WeatherBatteryOut "Battery Status" {channel="ambientweather1400ip:weatherstation:Weather1:battery_out"}
Number WeatherResponse "Response (ms)" {channel="ambientweather1400ip:weatherstation:Weather1:web_response"}
Switch WeatherReboot "Reboot Station" {channel="ambientweather1400ip:weatherstation:Weather1:reboot"}
String WeatherTime "Time of last update" {channel="ambientweather1400ip:weatherstation:Weather1:receiver_time"}
@mhilbush
Just a note in case you are interested. I did see the response of my ip observer go very high say 6000ms once but it has not done it in over a week. For now I suspect it was caused by two openhab instances running, one set to update every second whilst I was doing testing and developing. Since only doing an update every 20 seconds it has been great.
Thanks. It sounds like the firmware you’re using is much more stable than the version I’m using. Are there any features missing in the version you’re running compared with the version you were running from Ambient Weather? I might switch.
@mhilbush
I have not changed firmware. Ambient weather do not make the weather stations, nor do they sell or ship outside the USA. People in other countries need to buy under different brands. I purchased an IP observer separately as a spare part with the brand Misol on it for $50 shipped to my door. So I have this weather station which sends the data to a colour screen at the same time as to the Ip Observer unit. Be sure to check the freq matches before buying as they are made in 433, 868, 915 mhz models.
Ambient weather are 915mhz
Aercus (sold in the UK), Pantech and Misol are all 433mhz
The outdoor units only send RF blindly so you can have unlimited indoor units listening to the 1 outdoor unit. If you suspect your hardware has bad flash or ram possibly causing unstability then buying another Ip Observer as a spare part is pretty cheap and would allow you to keep the firmware stock on one whilst playing with a second.
My firmware version has a custom upload feature which does not appear to work. I cannot enter in the URL to the ambient weather website as it appears to have a character limit and I cannot enter the full url. It cuts the URL short. So I tried to enter in a local IP address which fits, but my router logs show that the weather station does not attempt to send packets to the IP I gave it. This would mean you would need to capture and re-direct the packets headed to WU to resend them to your desired URL.
I do not know who writes the firmware and which version Ambient possibly split off from the version I have. It is possible that Ambients is split from an older version and since they made so many customisations they are vastly different to what other brands use. The weewx forum is the best place to ask what version is best.
Hi Guys. I have this weather station. Will this work with openhab.
And can you please summarize the topic above. What exactly I have to do with this JAR file? I am not an expert just use Paper UI and some text config file.
Yes it will if you purchase as a spare part the ip observer unit which goes for $50 as a spare part. Be aware that they make them in three frequencies so get the same brand so it works. I run a screen like yours with the same outdoor unit and use an up observer at the same time. Works great and have had no issues since I moved to the ip observer as my screen would stop uploading to the cloud all the time.
What is the reason of this module? I can reach the inside screen through the local network with a desktop app so I think it has some web server capability. but I am not an network expert
The screens usually do not work for this address which the binding uses to scrape the data locally before it leaves your network.
http://192.168.1.4/livedata.htm
The advantage is this will work if your internet connection goes down which is highly likely during a storm, if you want reliable weather data in a storm then I would purchase the extra box and do this method. As mentioned the screen will still fully work at the same time as the IP box, they can work in parallel.
Sorry to be picky but this is NOT MY BINDING. 99% at least is the hard work of
Thomas Hentschel, I have just made some tiny changes.
NAN means Not a Number, have a look at the livedata page directly and see if the field has text or perhaps is null… Wait and if the value changes the binding should update it.
Also it confuses me why yours has degrees C next to the outdoor temp value, the mods I made should have removed all unit labelling, perhaps you need to do a clean of your tmp and cache folders if you have tried multiple jar files?
My mistake about the degrees C, I forgot I had played with the ability for the binding to follow the regional settings of Openhab, this is only done for the temperature and nothing else. I had not done it for the other settings as some of them have 4 different units they can be set to like wind. KM/hr, m/sec, Knotts, miles/hr, fps…
It would be possible to automate this by scraping the settings page just like what is done for the livedata and then setting up the %units% but that is a LOT of work which I am not keen on doing until I hear back from @captndelta so I can upload the changes to his github page in a way that wont effect the other bindings all in the same project.
