The 'myTile' is an attribute that is defined in the driver. I believe my 'myTile' may be unique, but I started from a myTile I originally saw in @arnb's driver and I have enhanced it. Adding any attribute to the dashboard is a built in function of the dashboards.
I made several minor adjustments/corrections throughout the day, but nothing big enough to create a new version number (yeah, I'm am a spare-time coder). If you pulled the driver code before 7:00 PM EST Sunday night, I suggest you refresh it again now.
We are hoping that the gateway for obtaining keys on the new API will open on February 15, 2019. In order to provide PWS uploaders with time to transition their API calls, all current WU API keys that are linked to a PWS will stay open through Friday, March 1, 2019. That gives you two full weeks to sign up for a new key and change your calls.
I am not sure how many people many be using this driver, but I don't think it is broadly used. My thoughts are to remove the Weatherunderground forecast option completely since it will be even more limited in who can use that option after March 1st. The Dark Sky forecast data has completely replaced my personal forecast usage and I have not relied on WU for a while now and I have not missed WU. So I would be interested to know your opinions:
I use the driver and would like to keep WU as a forecast option.
I use the driver and will use a forecast option other than WU. (APIXU or Dark Sky)
I use the driver without an external forecast option.
Maybe just a coincidence but I updated to the new driver (worked fine) but my hub slowed to a crawl
had not made any other changes today
restored to an earlier version and back working fine again
dev:31022019-02-16 10:15:33.330 pm errorgroovy.lang.MissingMethodException: No signature of method: dev1550380295524173664243.updateLux() is applicable for argument types: () values: []
The errors indicate that the Dark Sky API pull failed .... that probably cascaded the other errors. Make sure you load the new code and save it, then check all your preferences and save those.
I didn't have the "Station Data File Location:" filled in correctly which cause the cascade
But I still see a temporary slow down when selecting the new driver or saving preferences or polling or even just selecting the weather device itself seems to take a long time but after completed the rest of the hub appears to return to running fine again.
created a new api key just in case but same results
Glad it is working. I have not seen the slowdown on startup. Hopefully that was a one-time thing.
I'm interested in knowing if you see any more slowdown after it it is up and running.
Thanks for the feedback. Let me know if you see anything else that needs my attention.
thanks for the driver
still works fine
I just never saw the slow down with the old ApiXU driver vs the delay with darksky driver if you try to open another tab or do something else.
Not a big deal