perhaps it’s better to create a FR for Frontend
Same issue here! Since the update from 0.107.7 to 0.108.1 all my MyStrom Switch are gone. Home Assistant doesn’t show anymore Entities for MyStrom devices.
yeah running core in venv same error.
Update myStrom:
The power consumption values and temperatures fom this devices are still available. I read this with REST sensors out, this values are all still available. Only the switch entities are gone.
i doubt it. It missed the beta so probably next release
@PtP After moving from 107.7 to108.1 When I try to load the Dev Tools…or Configuration…nothing loads. So obviously can’t see the logs…The UI is opening but errors on many cards that were perfect under 107.7 such as:
- type: conditional
and
- type: entities
Didn’t bother going further than that…bailed back to 107.7 and all good.
Might look again after seeing what gets mentioned about the modbus issues you have noted above. Nothing mentioned in the breaking changes for Modbus that I can see?
yaml is going away rapidly is very obvious. We’ve just not been informed of when yet.
@amelchio When it was stated (by @balloob) it was not just a wishy washy statement it was more an emphatic promise made! Have HA devs polled their users to determine the numbers who use yaml config or not? Hey @nickrout were you polled…I certainly haven’t been? How then do HA devs know that “YAML usage is shrinking” ?
PS: I have tried to find the ‘emphatic promise made’ but I can’t find it anyone else know where it was? Has it been removed?
108.1 broke Vizio SmartCast bar. Only the Google cast. This bar has Google assistant built in. Worked in 108
ERROR (Thread-8) [pychromecast.socket_client] [Soundbar:8009] Failed to connect to service SmartCast-Sound-Bar–1eabbb691d70ebdd4fc823a1f3ac4039._googlecast._tcp.local
Is anyone else having trouble with garaget? I keep getting an error Garadget device ###### seems to be offline. This was working fine before the update and nothing in my configs for this have changed.
I also see a second log entry that says this:
- Unable to retrieve access token
- Garadget device ##### seems to be offline
Oh, I can see that this was an ambiguous statement. I meant that new integrations are primarily UI based and old ones are being converted. Nothing is moving in the opposite direction.
I went trough the UI and started a fake automation, then clicked on the show yaml. I’m sure there is a better way, but was just testing at the moment
@123 are you unaware of the statement I am referring to?
The one made some months ago by @balloob where he actually promised that the YAML config option would remain?
Thanks, I didn’t know where to make this suggestion.
I’m aware of this adage:
“If you want to know someone’s mind, listen to their words. If you want to know their heart, watch their actions.”
It’s seems that a line graph is no longer clickable, just the area with the current sensor state at the top of the card is. Is that a bug or feature?
Upgraded to 0.108.0 yesterday and today to 0.108.1 and I have some issues:
- Configuration validation takes much longer and does not finish, the wheel just spins and nothing happens. --> solved after a restart of HA
- I have a lot of new errors in de Log, specially for my BMWConnectedDrive integration
- Sonos service calls did not seam to work anymore, also fixed after a restart of HA
- and these
2020-04-09 15:50:34 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 418, in start
resp = await task
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py", line 458, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 119, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/real_ip.py", line 39, in real_ip_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 72, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 127, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 123, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/calendar/__init__.py", line 192, in get
request.app["hass"], start_date, end_date
File "/usr/src/homeassistant/homeassistant/components/caldav/calendar.py", line 139, in async_get_events
return await self.data.async_get_events(hass, start_date, end_date)
File "/usr/src/homeassistant/homeassistant/components/caldav/calendar.py", line 171, in async_get_events
vevent = event.instance.vevent
File "/usr/local/lib/python3.7/site-packages/caldav/objects.py", line 995, in _get_vobject_instance
self._vobject_instance = vobject.readOne(to_unicode(self._data))
File "/usr/local/lib/python3.7/site-packages/vobject/base.py", line 1156, in readOne
allowQP))
File "/usr/local/lib/python3.7/site-packages/vobject/base.py", line 1101, in readComponents
vline = textLineToContentLine(line, n)
File "/usr/local/lib/python3.7/site-packages/vobject/base.py", line 925, in textLineToContentLine
return ContentLine(*parseLine(text, n), **{'encoded': True,
File "/usr/local/lib/python3.7/site-packages/vobject/base.py", line 813, in parseLine
raise ParseError("Failed to parse line: {0!s}".format(line), lineNumber)
vobject.base.ParseError: At line 31: Failed to parse line: X-APPLE-STRUCTURED-LOCATION;VALUE=URI;X-ADDRESS=<address removed>\
My solution to fix the mystrom issue for the meantime is, to create a command_line switch.
- platform: command_line
switches:
tv_command_line:
command_on: "curl -X GET 'http://192.168.1.40/relay?state=1'"
command_off: "curl -X GET 'http://192.168.1.40/relay?state=0'"
command_state: "curl -X GET 'http://192.168.1.40/report'"
value_template: '{{ value_json.relay == true }}'
friendly_name: TV
My mystrom switch works all fine again with this solution in 0.108.1