Another thing I have thought about is perhaps a timestamp in the logs.
So instead of:
{"data":[{"unique_id":"currently_active_window","type":"sensor","state":"Settings \u2013 Home Assistant och 11 sidor till - Arbete \u2013 Microsoft? Edge","icon":"mdi:application"}],"type":"update_sensor_states"}
OK
you get:
{"datetime": "2022-08-19 14:25:00", "data":[{"unique_id":"currently_active_window","type":"sensor","state":"Settings \u2013 Home Assistant och 11 sidor till - Arbete \u2013 Microsoft? Edge","icon":"mdi:application"}],"type":"update_sensor_states"}
OK
sad to say they are not nativelly suported in .NET platform i will need to take closer look and it will be really time demanding will do next Month when i will have mor free time and app will be mor click and cleaned from initial debris from development
@Hellis81 maybe try to register app then close it vith close butoon not x button and then start it again sometime HA badly rebister WS when registering it when just conect to registered instance everything work at leas for me
So I believe the issue is not in the app but something with HA and the communication to the computer.
It could be that since message is blocked since it’s a work computer.
Our computers are so crippled they aren’t much of computers anymore.
I have this disable ass well those are native browser notifications, Can you please provide information if Websocket notification are working on same network on your mobile phone ?