I’m not through with researching this yet, but after installing the latest update (.9) I’ve lost my openweathermap forecast and sensor.
I didn’t find anything on the release-notes, concerning this. Did I miss something?
Hello. Have you fixed your problem?
I am working with the same problem!
BR
Oescafandrista
Had the same issue with lost openweathermap entity, but since I am actually working on deCONZ issues, i wasn’t sure, if this was related to the upgrade 108.9 or deCONZ.
So, most likely the update caused this.
Regards
Jörg
Protokolldetails ( ERROR )
Logger: homeassistant.components.weather
Source: components/openweathermap/weather.py:272
Integration: weather (documentation, issues)
First occurred: 25. April 2020, 18:41:48 (1 occurrences)
Last logged: 25. April 2020, 18:41:48
openweathermap: Error on device update!
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 324, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 476, in async_device_update
await self.hass.async_add_executor_job(self.update)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/openweathermap/weather.py", line 231, in update
self._owm.update_forecast()
File "/usr/src/homeassistant/homeassistant/util/__init__.py", line 240, in wrapper
result = method(*args, **kwargs)
File "/usr/src/homeassistant/homeassistant/components/openweathermap/weather.py", line 272, in update_forecast
self.latitude, self.longitude
File "/usr/local/lib/python3.7/site-packages/pyowm/weatherapi25/owm25.py", line 602, in three_hours_forecast_at_coords
forecast = self._parsers['forecast'].parse_JSON(json_data)
File "/usr/local/lib/python3.7/site-packages/pyowm/weatherapi25/parsers/forecastparser.py", line 66, in parse_JSON
for item in d['list']]
File "/usr/local/lib/python3.7/site-packages/pyowm/weatherapi25/parsers/forecastparser.py", line 66, in <listcomp>
for item in d['list']]
File "/usr/local/lib/python3.7/site-packages/pyowm/weatherapi25/weather.py", line 583, in weather_from_dictionary
visibility_distance, dewpoint, humidex, heat_index)
File "/usr/local/lib/python3.7/site-packages/pyowm/weatherapi25/weather.py", line 74, in __init__
raise ValueError("'clouds' must be greater than 0")
ValueError: 'clouds' must be greater than 0```Does anyone know if the printer entity states will be translated in a future release (idle, printing etc.) ? I checked on lokalise, but only the integration configuration UI seems to be translated.
Yes. Z-wave was fine in 0.106.x and I upgraded to 0.108.8 and everything appears fine in the ui but nothing switches on or off properly. It looks like something gets turned on, but then the sliding switch turns itself right back off again.
home-assistant.log shows and a lot of warning errors about decimal numbers…
Any fix to this before I give up on HA’s current native z-wave integration and use z-wave to mqtt on a separate box altogether? Or buy a Fibraro box if I can’t afford The free hours required to fix this?
1 Like
Not sure at which version it started, but I just noticed, that logic of displaying popup showing details of pointed to state of entity in history graph is changed. Instead of showing it just below the cursor horizontally it is displayed in the center of current state bar (very unintuitive). Also vertically it seems to be shifted ~3 bars below pointer. I found it very annoying, especially that is is causing popup to display at, or below bottom edge of the screen for graphs that are very low on the screen. In screenshot below mouse poiner was at letter P of PowerOff:
This shows both vertical and horizontal shift as well as going off the screen (bottom of browser window is visible). Fo the last graph in the list nothing is visible at all. I’d expect this pop up being displayed above cursor in such scenario.
Anyone else facing such issue? Can this be result of some theme settings?
Yeah, that looks exactly like the error-stack that I see.
An I mean exactly. So it’s not just my system. That’s a first 
Ok, I just found this:
So, known bug… possibly caused by broken data from OWM. We’ll see how this pans out.
AAAAnnnndddd: As mentioned in that bug: a reboot of the HA-server “fixed” it.
This release is miserable. Z-wave FUBAR for me.
This release is great. Nothing FUBAR. Working better with every release.
2 Likes
Can’t speak for the other two but ESPHome is working fine.
2 Likes
same here!
I don’t think requiring 9 updates to fix bugs/broken things would be considered “a great release”.
What’s worse is that it seems that different things get broken in each “fix” update.
edit: whoops, replied to wrong post…
1 Like
Would you prefer they just rolled them up in 0.109 And made everyone just wait? This is a good thing. I don’t judge the quality by the number of point releases.
1 Like
No
I agree that it’s good they fixed their mistakes and didn’t make people wait.
You may not but I think it’s a good measure of how many mistakes were made that needed fixing
I guess it depends on the the definition of “great” or what constitutes “success”.
I personally don’t subscribe the “the orange man’s” definition of “greatness” or “success” which this release was definitely an example of.
call it what you want and go ahead and be a cheerleader but at least have the integrity to admit that there were a bunch of errors made which then required fixes. But those “fixes” broke other things that then required more fixes.
I think I remember another release a few back that went badly, and even though it wasn’t quite as bad as this one, you yourself made a comment on how wrong it went.
Almost nobody expects a completely trouble free update but at least call a spade a spade.
Things happen. Mistakes are made. Admit it and move on.
1 Like
Well if the chat in the beta channel is anything to go by 0.109 should be better. Or we need more beta testers (my money’s on the latter).
Perhaps a blog post on how to be a beta tester would help.
1 Like
Having more beta testers would definitely be a tremendous help. Bug reports get fixed extremely fast during the beta period. There’s almost daily beta builds (5 betas in 7 days for this latest release).
But it’s always the same tiny group of beta users reporting these issues. Such a limited testing pool cannot possibly be expected to uncover issues in all 1,582 available integrations and all installation methods / hardware types.
If we had a lot more beta testers, this stuff would be found and fixed earlier in the process and not require as many post-release patches.
1 Like
I think a blog post outlining how to join the beta program and how easy reverting is if there is trouble (especially with Supervised) would get more members involved.
I’ve made a decision not to do so as I am 5400km away from my Home Assistant server for another 12 months but will get with the program when I return.
@tom_l I have already tested 0.109.obj4 and it is still broken for my config which was broken on 3 of the releases I tried briefly on 0.108.xx. Lucky that falling back was possible on all of those attempts.
The way this project is going I think my intention is to skip the aggravation and be content with something around the late 0.099.xx mark prior to the world falling apart in the 0.100+ era. It’s been a bloody nightmare right through all that keeping at the bleeding edge.
Unlike others my use case does not require all the ‘bells and whistles’ I just need certainty that my config continues to work. I may from time to time test my config out on a release that seems to have few faults but to be honest I cannot really see why I should bother any longer the direction this is all heading?
PS: Can anyone recommend a good solid version in the range 0.090.xx to 0.099.xx
PPS: Just noticed that 0.109.0 has been released yesterday…never tried that…not likely to either.