Yes. The History comes up correctly in 4-5 seconds on a Windows client or Linux browser client. My HA runs on a NUC.
The data is there in the browser. If you poke your finger on the white area you get the same pop up windows with correct content as when you hover the mouse over the area in windows/Linux browser.
You can also see that the browser in IOS adds a scroll bar on the right and you can scroll down in the white area. The data is there.
It is just rendered white on white which makes me think CSS issue
Well, I doubt anything will be done because the issue you keep linking isn’t correct for everyone. I have iOS 12 and iOS 13 devices, including an iPad with working history. If this is the case for the devs, then how can they correct an issue they can’t see?
I run all default colour scheme. I have no custom anything related to styling my HA. I like the default design. And it should be the same in IOS and on Windows/Linux clients.
I have an important update in debugging the history on IOS but I think we have hijacked this enough. I just wanted to raise an awareness post. I will put some updates on the github item and I will be updating more later today (I am at work now)
Anyone else having an issue with a wake on lan switch
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 130, in handle_call_service
connection.context(msg),
File "/usr/src/homeassistant/homeassistant/core.py", line 1260, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1295, in _execute_service
await handler.func(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 209, in handle_service
self._platforms.values(), func, call, required_features
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 454, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 595, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 485, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 621, in async_turn_on
await self.hass.async_add_executor_job(ft.partial(self.turn_on, **kwargs))
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/wake_on_lan/switch.py", line 103, in turn_on
port=self._broadcast_port,
File "/usr/local/lib/python3.7/site-packages/wakeonlan.py", line 79, in send_magic_packet
sock.connect((ip, port))
TypeError: an integer is required (got type NoneType)
direct service call on wake_on_lan.send_magic_packet seems to work.
On the off chance you aren’t joking, PLEASE don’t do that. And even if you were joking, others may not realize it - so don’t encourage others to do that unless they have useful debug information to add that isn’t already in the thread.
The proper way to “me too” is to click the reaction icon (thumbs up) on the original post of a issue.
Not sure if it has been mentioned but has the server restart button been moved above the yaml reload buttons in the server controls page? If so, thank you! I like the new position.
