Well, that at least closer to the root of the problem.
There have been some changes to the see handling since 4.1, but no one else has reported anything like this, so it’s still no clear if this is a bug in OH or some aspect of your system.
Just brainstorming some other possibilities, there are a few other questions you can explore.
Do you have any unusual network architecture (vlans, reverse proxies etc.)?
Are you using the same connection protocol (http or https) on the desktop and the mobile devices?
Do you have external access to OH via myopenhab and does that have a proper sse connection?
Have you tried closing all the active sessions (click on the user profile button in the lower right corner)?
You have not said, but I assume you are running this on a rPi of some sort. Have you check that system to make sure it’s resources are still sufficient?
I’m running OpenHab within a ProxMox Container. All other working clients also access OH by the same fqdn as my desktop. I also checked if disabling the web protection of my anti virus is the root cause (Sophos), but temporary disabling the web protection nor adding the fqdn to the exclude-list did change something.
I’m using vlans in my network but moving my desktop to the same vlan as the working clients also didn’t change something.
What i found in the console now after some try and error is this:
Those named items are the ones not updating. What does this “No connection id…” mean?
Following the whole log i see at the console of chrome browser:
Initializing state tracking store proxy
app.a727701d1d13ee2cbb47.js:2 sseConnected false
app.a727701d1d13ee2cbb47.js:2 Start tracking states
app.a727701d1d13ee2cbb47.js:2 new SSE connection: http://openhabian.iot.local:8080/rest/events/states, 1 open
app.a727701d1d13ee2cbb47.js:2 [EventSource]
app.a727701d1d13ee2cbb47.js:2 Loading semantic tags ...
app.a727701d1d13ee2cbb47.js:2 Setting initial tracking list: []
app.a727701d1d13ee2cbb47.js:2 sseConnected true
app.a727701d1d13ee2cbb47.js:2 Loading semantic model and building semantic homepages ...
app.a727701d1d13ee2cbb47.js:2 Successfully loaded semantic tags.
app.a727701d1d13ee2cbb47.js:2 Proxy: need KOSTAL_PLENTICORE_Plus_Ertrag_Tag
app.a727701d1d13ee2cbb47.js:2 Proxy: need KOSTAL_PLENTICORE_Plus_100_Ertrag_Monat
app.a727701d1d13ee2cbb47.js:2 updateTrackingList: Pending tracking list update, not calling the API
app.a727701d1d13ee2cbb47.js:2 Proxy: need KOSTAL_PLENTICORE_Plus_100_Ertrag_Jahr
app.a727701d1d13ee2cbb47.js:2 updateTrackingList: Pending tracking list update, not calling the API
app.a727701d1d13ee2cbb47.js:2 Proxy: need UI_Refresh_Timer
app.a727701d1d13ee2cbb47.js:2 updateTrackingList: Pending tracking list update, not calling the API
app.a727701d1d13ee2cbb47.js:2 Proxy: need VARTA_Netzbezug
app.a727701d1d13ee2cbb47.js:2 updateTrackingList: Pending tracking list update, not calling the API
app.a727701d1d13ee2cbb47.js:2 Proxy: need KOSTAL_PLENTICORE_Plus_AC_Power
app.a727701d1d13ee2cbb47.js:2 updateTrackingList: Pending tracking list update, not calling the API
app.a727701d1d13ee2cbb47.js:2 Proxy: need VARTA_Gesamtverbrauch
app.a727701d1d13ee2cbb47.js:2 updateTrackingList: Pending tracking list update, not calling the API
app.a727701d1d13ee2cbb47.js:2 Proxy: need VARTASpeicherXMLData_VARTASpeicherLadestand
app.a727701d1d13ee2cbb47.js:2 updateTrackingList: Pending tracking list update, not calling the API
app.a727701d1d13ee2cbb47.js:2 Proxy: need HueStehlampeFenster_Helligkeit
app.a727701d1d13ee2cbb47.js:2 updateTrackingList: Pending tracking list update, not calling the API
app.a727701d1d13ee2cbb47.js:2 Proxy: need HeizungISM8i_Ausentemperatur
app.a727701d1d13ee2cbb47.js:2 updateTrackingList: Pending tracking list update, not calling the API
app.a727701d1d13ee2cbb47.js:2 Proxy: need HUETVLicht_Helligkeit
app.a727701d1d13ee2cbb47.js:2 updateTrackingList: Pending tracking list update, not calling the API
app.a727701d1d13ee2cbb47.js:2 Proxy: need WarnungenReichenschwand_Warning1
app.a727701d1d13ee2cbb47.js:2 updateTrackingList: Pending tracking list update, not calling the API
app.a727701d1d13ee2cbb47.js:2 Updating tracking list: ["KOSTAL_PLENTICORE_Plus_Ertrag_Tag","KOSTAL_PLENTICORE_Plus_100_Ertrag_Monat","KOSTAL_PLENTICORE_Plus_100_Ertrag_Jahr","UI_Refresh_Timer","VARTA_Netzbezug","KOSTAL_PLENTICORE_Plus_AC_Power","VARTA_Gesamtverbrauch","VARTASpeicherXMLData_VARTASpeicherLadestand","HueStehlampeFenster_Helligkeit","HeizungISM8i_Ausentemperatur","HUETVLicht_Helligkeit","WarnungenReichenschwand_Warning1"]
app.a727701d1d13ee2cbb47.js:2 Successfully loaded semantic model and build semantic homepages.
I could analyse it down to a combination of Sophos Home Endpoint Protection Web Filtering and Chrome and Safari at Mac OS.
After switching off Web Filtering in Sophos all the values are shown in Openhab. Tried to exclude the openhab fqdn from web filtering but this seems not to work.
