The "java.lang.NullPointerException: Cannot invoke method size() on null object on line 435 (GetWeather)" increased in frequency and number over last 24 hours. Just updated to your Version 98 and will let you know how it goes. Thanks again for your hard work and responsiveness!
Let me know how it goes. I just checked my logs and did not have any hits at all last night. But that just means Ambient was working properly.
Not that the new version will make it get data. It will display an error that no data was received from Ambient.
I received one error around 8:46 AM since I installed the new driver (.98) around 6 AM EST:
Like the new description - unfortunately, the Ambient Weather API server has had a lot of issues the past couple of weeks.
Well, at least it is catching it now. You are getting a lot more of those than I was, but even from your log there it does not look like there is much consistency to it. Not like their server is having a fault for X hours, or some sort of repeating error.
@snell, I purchased an Ecowitt GW1000B with 2x temperature/humidity sensors and 3x soil moisture sensors. Thanks to your driver, so far, it's all working well.
What would be the easiest way in Hubitat to create discrete tiles for each and every sensor?
I do not think there is a perfect tile match for those sensors, but even then the normal tiles will not see the reported values properly because they are not named "normally" (since you can only provide one "temperature" per device for example). You could make tiles with the Attribute template. That will show one attribute on each though.
The other, more convoluted but maybe more what you want, way is to Connect a Global Variable to your Dashboard. I tried that just now to answer your question and I did come up with something. Basically I created 3 global variables (Temperature, Humidity, and WeatherString). I then created a rule that triggered whenever the two device attributes (temp & humidity, but could be anything) from my AmbientData device changed. It set the Temperature and Humidity variables based on the selected device attributes. Then I had it set the WeatherString based on those. There might be an easier way to do it, but I managed to get it working quickly as a sample.
Here is what it looks like:
And here is what I had as the Rule:
The errors with the Ambient Weather Net API have continued so I posted an inquiry to them about the issues we're having. Turns out their cloud vendor has been having problems with one of the physical servers and is attempting repairs. Following is their response to Ed Edelman at Ambient Net:
We have identified an issue on the physical machine hosting one or more of your Droplets, which are listed below. In order to minimize disruption, we will be migrating the Droplets to a healthier physical machine. Throughout the migration, Control Panel and API events - including: power offs, resizes, and attempts to destroy the Droplet - will not succeed for the affected Droplet(s).
In order to minimize downtime, we will attempt to perform live migrations in all possible cases. A live migration would result in no downtime, but minor performance decreases in disk I/O and a second or less of packet loss as the network is switched over to the new physical host.
In the event that we are not able to perform a live migration of a Droplet, we will perform an offline migration during which the Droplet will be powered off and migrated offline during the window.
We apologize for any inconvenience and will be happy to answer any questions or concerns - simply reply to this email or open a support ticket on your account.
DigitalOcean Cloud Operations
Not a surprise then. I really wish they had a mechanism for me to be able to know about server-side issues so I could provide a better status. I sent them an email about it previously... but never got a response.
Don't want to jinx the matter, but I haven't gotten an error on the Ambient Weather Net API poll since 2:46 PM yesterday ( dev:3532020-04-21 02:46:24.910 pm [error] Country Ln PWS - No data returned by Ambient). Just left a message at Ambient Weather Net thanking Ed Edelman and their cloud vendor for fixing the problem on the API servers.
- Imported @snell's latest custom driver into HE.
- Setup a new virtual device of type AmbientWeather
- Set a fake random string for API key
- Set a fake mac address of aa:aa:aa:aa:aa:aa
- Set Ecowitt Local and then Debug level logging
- Saved the device
- Set my GW1000 customized server to the IP address of my HE
- Set the GW1000 customized server path to "/aaa" (also tried other things)
- Set the GW1000 customized server to port 39501 with an upload interval of 30 seconds.
But I do not seem to be getting any data in HE.
I've tested changing the IP to one of my linux boxes listening on port 39501 and then changed the GW1000 to point to that box, and it received calls from the GW1000, so I know that is working.
I've telnetted to the HE on port 39501 and can see that the port is open.
After all this, there was nothing in the Events for the new AmbientWeather device I added...
Am I missing something?
Thanks for the help!
@OpenDave, the "trick" is to set the Ecowitt virtual device "Device Network ID" to the Ecowitt gateway "MAC address". The MAC address has to be formatted all uppercase with no colons (for example: fe:dc:ba:98:76:54 → FEDCBA987654).
@snell's driver doesn't have the GUI to do that, so you have to do it manually.
@snell I’m about to pull the trigger on an Ecowitt HP3501. Does your driver support this model? Also, what mounting pole are folks using to mount the Anemometer on their house? How high should it be off a roofline? Thanks!
Try @mircolino suggestion first, the hub needs to know that what is coming from the GW1000 MAC address needs to go to the correct driver. When that doesn't happen, the GW1000 message appears as an error in the log.
Thank you all!
As I understand it Ambient and Ecowitt are both just branded versions of Fine Offset devices which is why they have a lot of compatibility in terms of frequencies and protocol. In fact, I have the GW1000 a bunch of sensors and the Ambient WS2902 array and they work almost seamlessly together. (Almost because the "outdoor temp/humidity" from the WS2902 overrides the measurements from the WH32 so I cannot use that independently). Anyway, looking briefly at the description of the HP3501 it looks like it supports a "user customized website" likely in the same way the GW1000 does, and I suspect is speaks the same protocol. So, my guess is it will very likely work with @snell's driver as is. You might poke around on some of the WeeWx forums or similar and see if you can find anyone who has one who can tell you what the payload looks like and compare it to that of the GW1000. I suspect they are the same and I suspect the driver will work.
I hope this helps. Report back if you get one.
Thanks but I decided to go with a Weatherflow Tempest. Hopefully they start shipping in a few weeks.
If it sounds like it will have pretty much the same method as a GW1000, it should work. If some slight tweaks are needed in the driver, that should be possible also.
I will make some changes in the next rev of my driver to help with the Ecowitt... Try to avoid requiring a Fake API Key and such things going forward.
@snell you're awesome. If you need any help, let me know.
Main thing is if you spot anything that is not working as well as it could, or features you would like, let me know. Worst case, I would say no.
Otherwise, my drivers are basically a hobby now. They pretty much all do everything I need them to but I am always working on them a bit to make them better or as I learn new things while working on entirely new drivers.
Version 0.99 is now posted. Only Ecowitt users should see any difference as you will no longer need a fake MAC or API Key (they are hidden). For new users, the process is to add the virtual device, select the driver, then select the method you want (Ambient API or Ecowitt Local) and save preferences. If Ambient, it will then display the preferences for the MAC and API Key. Both get to select about the temperature, humidity, etc...