Closed Tux92 closed 8 months ago
there is indeed an error message that may not show up when you search by "widget" please get us the logs and mask your URL and GPS data so we can help out.
Ok, this is log
did you reproduce the issue before getting the logs? I do not see the expected log line with the error message we should see when the error view is shown.
Here I try edit widget configuration, update widget and next got to export log:
are there any HA core errors at the time of the issue? I see we have some log lines missing I may need to add them to help in debugging this.
Now I hope this is good. Here I create a new template widget and then export log.
can you please share the template that you are using?
Here is the relevant error, strange it did not show up before.
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: Exception while rendering template
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: io.homeassistant.companion.android.common.data.integration.IntegrationException: com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot deserialize value of type `java.lang.String` from Object value (token `JsonToken.START_OBJECT`)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at [Source: (okhttp3.ResponseBody$BomAwareReader); line: 1, column: 13] (through reference chain: java.util.LinkedHashMap["template"])
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at io.homeassistant.companion.android.common.data.integration.impl.IntegrationRepositoryImpl.renderTemplate(IntegrationRepositoryImpl.kt:229)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at io.homeassistant.companion.android.common.data.integration.impl.IntegrationRepositoryImpl$renderTemplate$1.invokeSuspend(Unknown Source:15)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:115)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:103)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:793)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:697)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:684)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: Caused by: com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot deserialize value of type `java.lang.String` from Object value (token `JsonToken.START_OBJECT`)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at [Source: (okhttp3.ResponseBody$BomAwareReader); line: 1, column: 13] (through reference chain: java.util.LinkedHashMap["template"])
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at com.fasterxml.jackson.databind.DeserializationContext.reportInputMismatch(DeserializationContext.java:1741)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at com.fasterxml.jackson.databind.DeserializationContext.handleUnexpectedToken(DeserializationContext.java:1515)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at com.fasterxml.jackson.databind.DeserializationContext.handleUnexpectedToken(DeserializationContext.java:1420)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at com.fasterxml.jackson.databind.DeserializationContext.extractScalarFromObject(DeserializationContext.java:932)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at com.fasterxml.jackson.databind.deser.std.StringDeserializer.deserialize(StringDeserializer.java:62)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at com.fasterxml.jackson.databind.deser.std.StringDeserializer.deserialize(StringDeserializer.java:11)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at com.fasterxml.jackson.databind.deser.std.MapDeserializer._readAndBindStringKeyMap(MapDeserializer.java:609)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at com.fasterxml.jackson.databind.deser.std.MapDeserializer.deserialize(MapDeserializer.java:437)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at com.fasterxml.jackson.databind.deser.std.MapDeserializer.deserialize(MapDeserializer.java:32)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.readRootValue(DefaultDeserializationContext.java:323)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at com.fasterxml.jackson.databind.ObjectReader._bindAndClose(ObjectReader.java:2051)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:1459)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at retrofit2.converter.jackson.JacksonResponseBodyConverter.convert(JacksonResponseBodyConverter.java:33)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at retrofit2.converter.jackson.JacksonResponseBodyConverter.convert(JacksonResponseBodyConverter.java:23)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at retrofit2.OkHttpCall.parseResponse(OkHttpCall.java:243)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:153)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
02-01 16:49:46.220 2044 4466 E TemplateWidgetConfigAct: at java.lang.Thread.run(Thread.java:919)
This is a homeassistant core error during a reboot:
Logger: homeassistant.helpers.event
Source: helpers/template.py:569
First occurred: 12:49:25 (1 occurrences)
Last logged: 12:49:25
Error while processing template: Template<template=(ENERGIA OGGI <br> Consumo: {{ states('sensor.oggi_energia_consumata') |round(1) }} kWh <br> Autoconsumo: {{ states('sensor.oggi_energia_autoconsumata') |round(1) }} kWh <br> Prelievo: {{ states('sensor.oggi_energia_prelevata') |round(1) }} kWh <br> Produzione: {{ states('sensor.oggi_energia_prodotta') |round(1) }} kWh <br> Immissione: {{ states('sensor.oggi_energia_immessa') |round(1) }} kWh) renders=2>
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/template.py", line 1644, in forgiving_round
value = round(float(value), precision)
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unknown'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/template.py", line 567, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/template.py", line 2305, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/srv/homeassistant/lib/python3.11/site-packages/jinja2/environment.py", line 1301, in render
self.environment.handle_exception()
File "/srv/homeassistant/lib/python3.11/site-packages/jinja2/environment.py", line 936, in handle_exception
raise rewrite_traceback_stack(source=source)
File "<template>", line 3, in top-level template code
File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/template.py", line 1649, in forgiving_round
raise_no_default("round", value)
File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/template.py", line 1625, in raise_no_default
raise ValueError(
ValueError: Template error: round got invalid input 'unknown' when rendering template
``` 'ENERGIA OGGI
<br>
Consumo: {{ states('sensor.oggi_energia_consumata') |round(1) }} kWh
<br>
Autoconsumo: {{ states('sensor.oggi_energia_autoconsumata') |round(1) }} kWh
<br>
Prelievo: {{ states('sensor.oggi_energia_prelevata') |round(1) }} kWh
<br>
Produzione: {{ states('sensor.oggi_energia_prodotta') |round(1) }} kWh
<br>
Immissione: {{ states('sensor.oggi_energia_immessa') |round(1) }} kWh' but no default was specified
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/template.py", line 693, in async_render_to_info
render_info._result = self.async_render(
^^^^^^^^^^^^^^^^^^
File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/template.py", line 569, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: round got invalid input 'unknown' when rendering template but no default was specified
And this is the template:
'ENERGIA OGGI
<br>
Consumo: {{ states('sensor.oggi_energia_consumata') |round(1) }} kWh
<br>
Autoconsumo: {{ states('sensor.oggi_energia_autoconsumata') |round(1) }} kWh
<br>
Prelievo: {{ states('sensor.oggi_energia_prelevata') |round(1) }} kWh
<br>
Produzione: {{ states('sensor.oggi_energia_prodotta') |round(1) }} kWh
<br>
Immissione: {{ states('sensor.oggi_energia_immessa') |round(1) }} kWh'
With previous app version I use this template without problems for years. This also work in developer tool section on homeassisntat
@Tux92 you have an issue with your template that you need to fix. Recent HA core versions require template updates for some users.
homeassistant.exceptions.TemplateError: ValueError: Template error: round got invalid input 'unknown' when rendering template but no default was specified
you need to fix your template, the app cant help with that.
This also work in developer tool section on homeassisntat
thats because you were testing when you had good values, you are nto handling when a sensor returns unknown
per teh error which is what a HA core update addressed. You need to specify a default per the error.
Ok, but this don't change anything, the widget don't showing
'ENERGIA OGGI
<br>
Consumo: {{ states('sensor.oggi_energia_consumata') |round(1, 0) }} kWh
<br>
Autoconsumo: {{ states('sensor.oggi_energia_autoconsumata') |round(1, 0) }} kWh
<br>
Prelievo: {{ states('sensor.oggi_energia_prelevata') |round(1, 0) }} kWh
<br>
Produzione: {{ states('sensor.oggi_energia_prodotta') |round(1, 0) }} kWh
<br>
Immissione: {{ states('sensor.oggi_energia_immessa') |round(1, 0) }} kWh'
At least now on reboot I no longer get the error in homeassistant core
do you still see the same error in the app logs? the same one I posted above?
This might not be isolated to template widgets as entity state widgets shows same error on latest app version.
@MrMiniMies yes. My entity state widget stopped working too. Not found anything obvious in the HA log to explain it, but I'm a newbie tbf
My widgets (entity state & switches) are gone too, after update to 2024.1.5-full Android 11
@UnitZ @hermanhobnob @MrMiniMies please get us the companion app logs ,we do not know this is hte same issue at this point. The error in the widget is generic and only the logs will tell the full picture. Without logs we cannot help.
First reproduce the issue by tapping on the widget then open the app. Settings > Companion App > Troubleshooting > show and share logs
I'm seeing the same issue with an entity widget just showing "Problem loading widget". Here's my logs from the two minutes when I tried to add a new widget.
```
02-02 17:31:29.442 8355 15779 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 17:31:29.458 8355 15779 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 17:31:29.472 8355 15779 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 17:31:29.483 8355 15779 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 17:31:29.486 8355 10249 D WebSocketRepository: Sending message 3524: {type=ping, id=3524}
02-02 17:31:29.487 8355 10249 D WebSocketRepository: Message number 3524 sent
02-02 17:31:29.528 8355 9010 D WebSocketRepository: Websocket: onMessage (text)
02-02 17:31:29.530 8355 9010 D WebSocketRepository: Message number 3524 received
02-02 17:31:34.689 8355 8355 I ViewRootImpl@577a199[WebViewActivity]: onDisplayChanged oldDisplayState=1 newDisplayState=2
02-02 17:31:34.690 8355 8355 I ViewRootImpl@b3b1032[SettingsActivity]: onDisplayChanged oldDisplayState=1 newDisplayState=2
02-02 17:31:34.714 8355 8355 D SurfaceView@890f495: 143717525 updateSurface: has no frame
02-02 17:31:34.901 8355 8355 I ViewRootImpl@577a199[WebViewActivity]: onDisplayChanged oldDisplayState=2 newDisplayState=2
02-02 17:31:34.901 8355 8355 I ViewRootImpl@b3b1032[SettingsActivity]: onDisplayChanged oldDisplayState=2 newDisplayState=2
02-02 17:31:34.905 8355 8355 D SensorReceiver: Received intent: android.intent.action.SCREEN_ON
02-02 17:31:34.907 8355 8355 D SensorReceiver: Sensor is_interactive corresponding to received event android.intent.action.SCREEN_ON is disabled, skipping sensors update
02-02 17:31:34.910 8355 8355 D ButtonWidget: Broadcast received:
02-02 17:31:34.910 8355 8355 D ButtonWidget: Broadcast action: android.intent.action.SCREEN_ON
02-02 17:31:34.910 8355 8355 D ButtonWidget: AppWidgetId: -1
02-02 17:31:34.930 8355 8355 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 17:31:34.934 8355 8355 D MediaPlayCtrlsWidget: Broadcast received:
02-02 17:31:34.934 8355 8355 D MediaPlayCtrlsWidget: Broadcast action: android.intent.action.SCREEN_ON
02-02 17:31:34.934 8355 8355 D MediaPlayCtrlsWidget: AppWidgetId: -1
02-02 17:31:34.984 8355 8355 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 17:31:34.995 8355 8355 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 17:31:34.995 8355 8355 D ServerConnectionInfo: Using internal URL
02-02 17:31:35.005 8355 8355 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 17:31:35.005 8355 8355 D ServerConnectionInfo: Using internal URL
02-02 17:31:35.023 8355 8355 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 17:31:35.023 8355 8355 D ServerConnectionInfo: Using internal URL
02-02 17:31:35.030 8355 7633 D TrafficStats: tagSocket(103) with statsTag=0xffffffff, statsUid=-1
02-02 17:31:35.061 8355 8355 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 17:31:35.061 8355 8355 D ServerConnectionInfo: Using internal URL
02-02 17:31:35.079 8355 8355 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 17:31:35.093 8355 8355 D WebSocketRepository: Sending message 3525: {type=config/entity_registry/get, entity_id=sensor.buiten_thermometer_temperature, id=3525}
02-02 17:31:35.094 8355 8355 D WebSocketRepository: Message number 3525 sent
02-02 17:31:35.107 8355 9010 D WebSocketRepository: Websocket: onMessage (text)
02-02 17:31:35.108 8355 9010 D WebSocketRepository: Message number 3525 received
02-02 17:31:35.110 8355 8355 D WebSocketRepository: Sending message 3526: {type=config/entity_registry/get, entity_id=sensor.buiten_thermometer_temperature, id=3526}
02-02 17:31:35.111 8355 8355 D WebSocketRepository: Message number 3526 sent
02-02 17:31:35.119 8355 9010 D WebSocketRepository: Websocket: onMessage (text)
02-02 17:31:35.120 8355 9010 D WebSocketRepository: Message number 3526 received
02-02 17:31:35.132 8355 8355 I AppWidgetManager: updateAppWidget() appWidgetIds = [28]
02-02 17:31:35.139 8355 8355 I AppWidgetManager: updateAppWidget() appWidgetIds = [30]
02-02 17:31:35.903 8355 8355 I ViewRootImpl@b3b1032[SettingsActivity]: handleAppVisibility mAppVisible = false visible = true
02-02 17:31:35.907 8355 8355 I ViewRootImpl@b3b1032[SettingsActivity]: stopped(false) old = true
02-02 17:31:35.907 8355 8355 D ViewRootImpl@b3b1032[SettingsActivity]: WindowStopped on io.homeassistant.companion.android/io.homeassistant.companion.android.settings.SettingsActivity set to false
02-02 17:31:35.913 8355 8355 D IntegrationRepository: isAppLocked(): false. (LockEnabled: false, appActive: false, expireMillis: 1706891339232, currentMillis: 1706891495913)
02-02 17:31:35.942 8355 8355 D InsetsController: onStateChanged: host=io.homeassistant.companion.android/io.homeassistant.companion.android.settings.SettingsActivity from=android.view.ViewRootImpl.relayoutWindow:9940 state=InsetsState: {mDisplayFrame=Rect(0, 0 - 1080, 2400), mDisplayCutout=DisplayCutout{insets=Rect(0, 88 - 0, 0) waterfall=Insets{left=0, top=0, right=0, bottom=0} boundingRect={Bounds=[Rect(0, 0 - 0, 0), Rect(512, 0 - 568, 88), Rect(0, 0 - 0, 0), Rect(0, 0 - 0, 0)]} cutoutPathParserInfo={CutoutPathParserInfo{displayWidth=1080 displayHeight=2400 physicalDisplayWidth=1080 physicalDisplayHeight=2400 density={2.8125} cutoutSpec={M 0,0 M 0,11.43427858034597 a 9.899054752987353,9.899054752987353 0 1,0 0,19.79810950597471 a 9.899054752987353,9.899054752987353 0 1,0 0,-19.79810950597471 Z @dp} rotation={0} scale={1.0} physicalPixelDisplaySizeRatio={1.0}}}}, mRoundedCorners=RoundedCorners{[RoundedCorner{position=TopLeft, radius=0, center=Point(0, 0)}, RoundedCorner{position=TopRight, radius=0, center=Point(0, 0)}, RoundedCorner{position=BottomRight, radius=0, center=Point(0, 0)}, RoundedCorner{position=BottomLeft, radius=0, center=Point(0, 0)}]} mRoundedCornerFrame=Rect(0, 0 - 1080, 2400), mPrivacyIndicatorBounds=PrivacyIndicatorBounds {static bounds=Rect(956, 0 - 1080, 88) rotation=0}, mDisplayShape=DisplayShape{ spec=-1893857183 displayWidth=1080 displayHeight=2400 physicalPixelDisplaySizeRatio=1.0 rotation=0 offsetX=0 offsetY=0 scale=1.0}, mSources= { InsetsSource: {a5fe0001 mType=navigationBars mFrame=[0,2265][1080,2400] mVisible=false mFlags=[]}, InsetsSource: {a5fe0004 mType=systemGestures mFrame=[0,0][0,0] mVisible=true mFlags=[]}, InsetsSource: {a5fe0005 mType=mandatorySystemGestures mFrame=[0,2265][1080,2400] mVisible=true mFlags=[]}, InsetsSource: {a5fe0006 mType=tappableElement mFrame=[0,2265][1080,2400] mVisible=true mFlags=[]}, InsetsSource: {a5fe0024 mType=systemGestures mFrame=[0,0][0,0] mVisible=true mFlags=[]}, InsetsSource: {3 mType=ime mFrame=[0,0][0,0] mVisible=false mFlags=[]}, InsetsSource: {27 mType=displayCutout mFrame=[0,0][1080,88] mVisible=true mFlags=[]}, InsetsSource: {598f0000 mType=statusBars mFrame=[0,0][1080,88] mVisible=true mFlags=[]}, InsetsSource: {598f0005 mType=mandatorySystemGestures mFrame=[0,0][1080,122] mVisible=true mFlags=[]}, InsetsSource: {598f0006 mType=tappableElement mFrame=[0,0][1080,88] mVisible=true mFlags=[]} }
02-02 17:31:35.944 8355 8355 I BLASTBufferQueue_Java: new BLASTBufferQueue, mName= ViewRootImpl@b3b1032[SettingsActivity] mNativeObject= 0xb4000075d7a94ad0 sc.mNativeObject= 0xb4000076279fa950 caller= android.view.ViewRootImpl.updateBlastSurfaceIfNeeded:2979 android.view.ViewRootImpl.relayoutWindow:9998 android.view.ViewRootImpl.performTraversals:4056 android.view.ViewRootImpl.doTraversal:3239 android.view.ViewRootImpl$TraversalRunnable.run:11197 android.view.Choreographer$CallbackRecord.run:1650 android.view.Choreographer$CallbackRecord.run:1659 android.view.Choreographer.doCallbacks:1129 android.view.Choreographer.doFrame:1055 android.view.Choreographer$FrameDisplayEventReceiver.run:1622
02-02 17:31:35.944 8355 8355 I BLASTBufferQueue_Java: update, w= 1080 h= 2400 mName = ViewRootImpl@b3b1032[SettingsActivity] mNativeObject= 0xb4000075d7a94ad0 sc.mNativeObject= 0xb4000076279fa950 format= -1 caller= android.graphics.BLASTBufferQueue.
Home Assistant Application version: 2024.1.5-full Home Assistant version: 2024.1.6 on OS 11.4 Android version: 14
@arthurrump can you do me a favor and tap on teh widget once and then pull the logs again? unfortunately those logs dont show any errors from the app end but its possible there may be an error on the HA core side of things as we can see websocket connection. Hopefully tapping on the widget will help us see the actual error.
Of course! I tapped it, waited a few seconds, tapped it again and then launched the app to get the logs. These are the last two minutes:
```
02-02 19:11:07.770 8355 15779 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:11:07.778 8355 15779 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:11:07.787 8355 15779 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:11:07.795 8355 15779 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:11:07.797 8355 15780 D WebSocketRepository: Sending message 3754: {type=ping, id=3754}
02-02 19:11:07.798 8355 15780 D WebSocketRepository: Message number 3754 sent
02-02 19:11:07.825 8355 9010 D WebSocketRepository: Websocket: onMessage (text)
02-02 19:11:07.827 8355 9010 D WebSocketRepository: Message number 3754 received
02-02 19:11:37.804 8355 27675 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:11:37.812 8355 27675 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:11:37.816 8355 27675 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:11:37.820 8355 27675 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:11:37.821 8355 27675 D WebSocketRepository: Sending message 3755: {type=ping, id=3755}
02-02 19:11:37.821 8355 27675 D WebSocketRepository: Message number 3755 sent
02-02 19:11:37.846 8355 9010 D WebSocketRepository: Websocket: onMessage (text)
02-02 19:11:37.847 8355 9010 D WebSocketRepository: Message number 3755 received
02-02 19:11:45.086 8355 8355 D SensorReceiver: Received intent: android.intent.action.SCREEN_ON
02-02 19:11:45.088 8355 8355 D SensorReceiver: Sensor is_interactive corresponding to received event android.intent.action.SCREEN_ON is disabled, skipping sensors update
02-02 19:11:45.096 8355 8355 D ButtonWidget: Broadcast received:
02-02 19:11:45.096 8355 8355 D ButtonWidget: Broadcast action: android.intent.action.SCREEN_ON
02-02 19:11:45.096 8355 8355 D ButtonWidget: AppWidgetId: -1
02-02 19:11:45.200 8355 8355 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:11:45.212 8355 8355 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:11:45.212 8355 8355 D ServerConnectionInfo: Using internal URL
02-02 19:11:45.242 8355 8355 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:11:45.242 8355 8355 D ServerConnectionInfo: Using internal URL
02-02 19:11:45.259 8355 8355 D MediaPlayCtrlsWidget: Broadcast received:
02-02 19:11:45.259 8355 8355 D MediaPlayCtrlsWidget: Broadcast action: android.intent.action.SCREEN_ON
02-02 19:11:45.259 8355 8355 D MediaPlayCtrlsWidget: AppWidgetId: -1
02-02 19:11:45.277 8355 8355 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:11:45.301 8355 8355 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:11:45.313 8355 29789 D TrafficStats: tagSocket(103) with statsTag=0xffffffff, statsUid=-1
02-02 19:11:45.385 8355 8355 D WebSocketRepository: Sending message 3756: {type=config/entity_registry/get, entity_id=sensor.buiten_thermometer_temperature, id=3756}
02-02 19:11:45.385 8355 8355 D WebSocketRepository: Message number 3756 sent
02-02 19:11:45.394 8355 9010 D WebSocketRepository: Websocket: onMessage (text)
02-02 19:11:45.396 8355 9010 D WebSocketRepository: Message number 3756 received
02-02 19:11:45.406 8355 8355 I AppWidgetManager: updateAppWidget() appWidgetIds = [28]
02-02 19:11:46.222 8355 8355 D LocBroadcastReceiver: Received location update.
02-02 19:11:46.229 8355 8355 D ForegrndServiceLauncher: Check if service HighAccuracyLocationService is running. Service running = false
02-02 19:11:46.230 8355 10249 D LocBroadcastReceiver: Last Location:
02-02 19:11:46.230 8355 10249 D LocBroadcastReceiver: Coords:()
02-02 19:11:46.230 8355 10249 D LocBroadcastReceiver: Accuracy: 100.0
02-02 19:11:46.230 8355 10249 D LocBroadcastReceiver: Bearing: 0.0
02-02 19:11:46.232 8355 10249 D LocBroadcastReceiver: Begin evaluating if location update should be skipped
02-02 19:11:46.232 8355 10249 D LocBroadcastReceiver: Received location that is 68 milliseconds old, 1706897506164 compared to 1706897506232 with source fused
02-02 19:11:46.233 8355 10249 D LocBroadcastReceiver: Duplicate location received, not sending to HA
02-02 19:11:52.941 8355 8355 D NotifManagerCompat: Cancel notification with tag "null" and id "0"
02-02 19:11:52.947 8355 8355 D NotifManagerCompat: Check if the notification is in a group...
02-02 19:11:52.948 8355 8355 D NotifManagerCompat: Notification is not in a group. Cancel notification...
02-02 19:11:53.018 8355 8585 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:11:53.098 8355 8585 D NotifDeleteReceiver: Notification cleared event successful!
02-02 19:12:07.827 8355 8585 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:12:07.833 8355 8585 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:12:07.839 8355 8585 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:12:07.842 8355 8585 D ServerConnectionInfo: localUrl is: true, usesInternalSsid is: true, usesWifi is: true
02-02 19:12:07.846 8355 8585 D WebSocketRepository: Sending message 3757: {type=ping, id=3757}
02-02 19:12:07.848 8355 8585 D WebSocketRepository: Message number 3757 sent
02-02 19:12:07.870 8355 9010 D WebSocketRepository: Websocket: onMessage (text)
02-02 19:12:07.885 8355 9010 D WebSocketRepository: Message number 3757 received
02-02 19:12:31.532 8355 8355 I DecorView: setWindowBackground: isPopOver=false color=ff111111 d=android.graphics.drawable.ColorDrawable@f0fa986
02-02 19:12:31.574 8355 10098 D NativeCustomFrequencyManager: [NativeCFMS] BpCustomFrequencyManager::BpCustomFrequencyManager()
02-02 19:12:31.583 8355 8355 D InsetsController: onStateChanged: host=io.homeassistant.companion.android/io.homeassistant.companion.android.launch.LaunchActivity from=android.view.ViewRootImpl.setView:1717 state=InsetsState: {mDisplayFrame=Rect(0, 0 - 1080, 2400), mDisplayCutout=DisplayCutout{insets=Rect(0, 88 - 0, 0) waterfall=Insets{left=0, top=0, right=0, bottom=0} boundingRect={Bounds=[Rect(0, 0 - 0, 0), Rect(512, 0 - 568, 88), Rect(0, 0 - 0, 0), Rect(0, 0 - 0, 0)]} cutoutPathParserInfo={CutoutPathParserInfo{displayWidth=1080 displayHeight=2400 physicalDisplayWidth=1080 physicalDisplayHeight=2400 density={2.8125} cutoutSpec={M 0,0 M 0,11.43427858034597 a 9.899054752987353,9.899054752987353 0 1,0 0,19.79810950597471 a 9.899054752987353,9.899054752987353 0 1,0 0,-19.79810950597471 Z @dp} rotation={0} scale={1.0} physicalPixelDisplaySizeRatio={1.0}}}}, mRoundedCorners=RoundedCorners{[RoundedCorner{position=TopLeft, radius=0, center=Point(0, 0)}, RoundedCorner{position=TopRight, radius=0, center=Point(0, 0)}, RoundedCorner{position=BottomRight, radius=0, center=Point(0, 0)}, RoundedCorner{position=BottomLeft, radius=0, center=Point(0, 0)}]} mRoundedCornerFrame=Rect(0, 0 - 1080, 2400), mPrivacyIndicatorBounds=PrivacyIndicatorBounds {static bounds=Rect(956, 0 - 1080, 88) rotation=0}, mDisplayShape=DisplayShape{ spec=-1893857183 displayWidth=1080 displayHeight=2400 physicalPixelDisplaySizeRatio=1.0 rotation=0 offsetX=0 offsetY=0 scale=1.0}, mSources= { InsetsSource: {a5fe0001 mType=navigationBars mFrame=[0,2265][1080,2400] mVisible=true mFlags=[]}, InsetsSource: {a5fe0004 mType=systemGestures mFrame=[0,0][0,0] mVisible=true mFlags=[]}, InsetsSource: {a5fe0005 mType=mandatorySystemGestures mFrame=[0,2265][1080,2400] mVisible=true mFlags=[]}, InsetsSource: {a5fe0006 mType=tappableElement mFrame=[0,2265][1080,2400] mVisible=true mFlags=[]}, InsetsSource: {a5fe0024 mType=systemGestures mFrame=[0,0][0,0] mVisible=true mFlags=[]}, InsetsSource: {3 mType=ime mFrame=[0,0][0,0] mVisible=false mFlags=[]}, InsetsSource: {27 mType=displayCutout mFrame=[0,0][1080,88] mVisible=true mFlags=[]}, InsetsSource: {598f0000 mType=statusBars mFrame=[0,0][1080,88] mVisible=true mFlags=[]}, InsetsSource: {598f0005 mType=mandatorySystemGestures mFrame=[0,0][1080,122] mVisible=true mFlags=[]}, InsetsSource: {598f0006 mType=tappableElement mFrame=[0,0][1080,88] mVisible=true mFlags=[]} }
02-02 19:12:31.583 8355 8355 I ViewRootImpl@127576a[LaunchActivity]: synced displayState. AttachInfo displayState=2
02-02 19:12:31.585 8355 8355 I ViewRootImpl@127576a[LaunchActivity]: setView = com.android.internal.policy.DecorView@d3028a4 TM=true
02-02 19:12:31.685 8355 8355 I BLASTBufferQueue_Java: new BLASTBufferQueue, mName= ViewRootImpl@127576a[LaunchActivity] mNativeObject= 0xb4000075d7a15870 sc.mNativeObject= 0xb4000076279ef910 caller= android.view.ViewRootImpl.updateBlastSurfaceIfNeeded:2979 android.view.ViewRootImpl.relayoutWindow:9998 android.view.ViewRootImpl.performTraversals:4056 android.view.ViewRootImpl.doTraversal:3239 android.view.ViewRootImpl$TraversalRunnable.run:11197 android.view.Choreographer$CallbackRecord.run:1650 android.view.Choreographer$CallbackRecord.run:1659 android.view.Choreographer.doCallbacks:1129 android.view.Choreographer.doFrame:1055 android.view.Choreographer$FrameDisplayEventReceiver.run:1622
02-02 19:12:31.685 8355 8355 I BLASTBufferQueue_Java: update, w= 1080 h= 2400 mName = ViewRootImpl@127576a[LaunchActivity] mNativeObject= 0xb4000075d7a15870 sc.mNativeObject= 0xb4000076279ef910 format= -1 caller= android.graphics.BLASTBufferQueue.
I'm not sure what I'm looking for exactly, but I don't see any obvious errors here either.
@arthurrump can you check if there are any HA core errors at the time you selected it. The logs suggest we were able to connect to the server and get a response. Is the entity in your widget sensor.buiten_thermometer_temperature
?
02-02 19:11:45.385 8355 8355 D WebSocketRepository: Sending message 3756: {type=config/entity_registry/get, entity_id=sensor.buiten_thermometer_temperature, id=3756}
02-02 19:11:45.385 8355 8355 D WebSocketRepository: Message number 3756 sent
02-02 19:11:45.394 8355 9010 D WebSocketRepository: Websocket: onMessage (text)
02-02 19:11:45.396 8355 9010 D WebSocketRepository: Message number 3756 received
02-02 19:11:45.406 8355 8355 I AppWidgetManager: updateAppWidget() appWidgetIds = [28]
@UnitZ can you also check HA core errors at the time? I am seeing a similar request and success messages from your server. I assume the entity in your widget is sensor.ds18b20_ulitsa_42d175d0013c
?
02-02 21:20:03.062 6098 6098 D WebSocketRepository: Sending message 2593: {type=config/entity_registry/get, entity_id=sensor.ds18b20_ulitsa_42d175d0013c, id=2593}
02-02 21:20:03.062 6098 6098 D WebSocketRepository: Message number 2593 sent
02-02 21:20:03.066 6098 17113 D WebSocketRepository: Websocket: onMessage (text)
02-02 21:20:03.066 6098 17113 D WebSocketRepository: Message number 2593 received
just for reference my own template and entity state widgets are workign and updating as expected, so we still need a bit of troubleshooting to see if these are all the same issue or if there is something else at play here.
Yes, that is indeed the entity in my widget. I'm seeing one error in the core logs around the same time (two minutes later), but I'm not sure that it's related:
Logger: aiohttp.server
Source: /usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py:421
First occurred: 19:13:23 (1 occurrences)
Last logged: 19:13:23
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 350, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 557, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message:
Invalid method encountered:
b'\x16\x03\x01\x02\x90\x01'
^
It's also there only once, while I'd expect there to be more, given that the widget has been unable to load for a while now, right?
So the entity state and template widget shoudl behave as follows:
If we are seeing successful messages from the app showing we are getting responses the issue may be from HA core or could be related to the users own networking setup. Can you guys let me know what your setup is like? Does this issue only happen locally or remotely?
I can see from the logs that sensors are able to update but sensors use a different API method so your network setup may be at play here.
I just tried with a different launcher and can confirm that it is working with (Samsung) One UI Home just fine, but in Lawnchair (what I normally use) it shows the "Problem loading widget".
but in Lawnchair (what I normally use) it shows the "Problem loading widget".
its quite possible that the app logs do not contain the relevant data, are you by chance familiar with logcat? If you are able to setup Android Studio and connect your phone you may be able to pull more logs to see where the issue comes from to see if we can fix it.
As of now though your issue seems unrelated to the original issue from the original author who had a template error.
To the others facing this issue please confirm your launcher.
@dshokouhi I think you've worked it out. I too use lawnchair. Switching back to the pixel launcher shows there isn't an issue. But according to Google Play Lawnchair last updated on my device on the 13 Dec which significantly predates this problem showing up.
My last Lawnchair update was in August (that's probably when I installed it, because the app hasn't updated since 2019...). Anyway, since @dshokouhi thinks this is a different issue, I've split it out into #4183.
@Tux92 are you by chance using the same mentioned launcher?
@Tux92 are you by chance using the same mentioned launcher?
Yes, I also use lawnchair! Do you think this is the problem? I have no issue till now.
thats the assumption and looking on their github this one issue does seem to describe similar behavior. Tesla app had an update and now it no longer loads in this particular launcher.
Lawnchair 14 was released today, can those who use that launcher please update and check if this issue got fixed in the latest version?
I confirm widget works with Lawnchair 14 beta 2 version.
Closed? Still does not work in Lawnchair 2
Yes, in version 2 it doesn't work, but on version 14 beta2 it works well.
Using CarWebGuru and HA widget always stuck on spinning after I tap it
Home Assistant Android app version(s): 2024.1.5-full
Android version(s): 10
Device model(s): OnePlus 5T (ONEPLUS A5010) and Redmi Note 8T
Home Assistant version: 2024.1.2
Last working Home Assistant release (if known): 2024.1.2
Description of problem, include YAML if issue is related to notifications: I configure 2 template widget to view faster the state of a sensor from my phone homepage without open app. But this night auto update install new version of companion app 2024.1.5-full and the widget are white background with this message "Errore durante il caricametto del widget" (Italian traslation of Error during template loading).
This is configuration of one of this:
I also try to make other widget more simple but same error. As you can see in the screen the preview of the widget is ok.
Companion App Logs: There is personal data so I try to search in the log but there aren't error regarding widget.
Screenshot or video of problem:
Additional information: