App keeps crashing lowkey
It stops working randomly and when I check the logs there's an exception. Last time I reported the app randomly stopped working you told me it's my config. it is not.
66 Replies
Whenever I find this it's because it's when I try to hibernate my pc and it won't because the sensors have stopped reporting and automations are not processed because of it.
Version number pls
@Amadeo
I don't see any exception that could cause the crash - all of them are first chance exceptions (part of debug logs)
Are there any suspicious things in the event viewer?
Could you please try beta2 - https://github.com/hass-agent/HASS.Agent/releases/tag/2.1.0-beta2 (please pay attention to installation directory if you used a custom one)
GitHub
Release 2.1.0-beta2 · hass-agent/HASS.Agent
Changes:
Added "SetAudioInputCommand" (thanks to Chrisdegod for the suggestion) - #41
Added "ScreenshotSensor", functioning as camera entity (huge thanks to @denisabt for the i...
Last time I reported the app randomly stopped working you told me it's my config. it is not.Reference please
beta1
hass.agent.svc looks like it has no issues
Only thing that crashed around that time was Touchportal
TouchPortalServices.exe
Hmm
There were two audio bugs that could crash just like that - audio library and during media play from HA - in theory both should be fixed in beta2
It just stops reporting for some reason
Still crashing presumably?
yes
today
stopped reporting again
last update 01;56
HASS never connected back after rebooting my HAOS server. Even tho it shows all is green
after a fail it just stops trying
untill you do something
like edit a command
R U still running beta1?
If so try 2.1.0-beta2 in #🚀・releases
beta2
im going to sleep
ttyt
from the last logs it looks like HASS.Agent tried to connect but couldn't
is the device being used while HASS.Agent is reported by HA as not available?
thinking about the posibility of device going to sleep
my pc has been on since the error when I rebooted hass
untill 2 ish
3 ish
iirc
but it never actually comes back online until I restart hass
it's a desktop pc? asking for such details as new devices use s0ix sleep which is almost unrecognizable but also problematic
no no
the hass server was rebooted
then it never connected
I was updating hass and rebooting that
and my normal pc was on
hass server?
oh, home assistant
the connection issue is another topic, if hass.agent tried to connect but failed I'd need to be checked when is occurs again (is the issue occuring for hass.agent only of for other apps like browser also)
im pretty sure it stopped working due to me rebooting the server. Ill try to replicate later today:
Sat service: same thing but worse:
It disconnected and never came back untill I re-stored all commands and sensors
I just rebooted my hass.server again and sat service didn't come back.
this image is from sat service btw
this bottom one is from normal:
all greyed out instead of blue
Srry for the wall btw
just to clarify:
I came home today, rebooted HAOS and both sat service and normal hass.agent are down as shown in the pictures. PC was on the whole time after hibernation from last night. After I booted it seemed like everything was in order. I rebooted both HASS and the server to check if anything was already going on.
I then checked what was being reported towards mqtt and rebooted HAOS including add-ons. End result is the last two images.
Everything expect for local API was green
* still is because I only use mqt
I think I'm confused about 'HASS', 'HASS and the server' 😄
That log basically says that it tried to connect and couldnt because server refused it
What kind of mqtt broker you're using?
yeah failing once doesnt mean it should crap out and stop working 🥲
im absolutley baffeled... 😮
Am I right in thinking you are running HA on top of another server @PagitosDiablos ?
Let me get a few things straight @PagitosDiablos
1. You rebooted HA and mqtt?
2. PC was not rebooted
3. It did not show commands and HASS.Agent would not connect?
HAOS on proxmox as a VM.
HASS => Hass.agent
server of HAOS => Home Assistent VM
I'm redoing my mqtt completly
the mqtt-explorer showed it updating values
but it didn't show in HA
__
I redid the whole thing
redid this:
re-installed the MQTT addon from HA
all is working
now to test if hass.agent survives if I reboot my Home Assistant installation
during reboot
addons rebooting i guess:
home assistant is back up:
but mqtt is still blue
Okay so you have mqtt inside of HAOS
yes
Can U connect from mqttexplorer?
i am
current state after reboot including HA-addons
@Amadeo, basically mqtt and HA are tied together, if they are rebooted and hass.agent are not the mqtt does not connect, everything else does
Can you try rebooting just hass.agent app and see if it reconnects?
yeah it does, but that's not the point
Ik but just checking since you redid things
I don't wanna reboot hass.agent EVERY time i reboot the server
yeah i know the reboot is gonna bring it back
which it did
Look personally I don't see why you are rebooting Ur server more than your PC but yes I can see how this needs to be fixed anyway
Im away from home for a week but hopefully I can tailscale for a bit this Arvo and have a look
reboots happen because of automated supervisor updates, updating of my HA install, addons, proxmox maintaince, etc
thanks for the time you spend on this btw
appreciate it
may not show, but I do
Rebooting both sat service and hass.agent normal fix disconnects untill my Home assistant reboots or disconnects from the network
sidequestion: using either mqtt v3.1.1 vs v5 doesn't matter for hass.agent correct?
Nope, afaik our use cases/libraries don't care
Not sure if this weekend but next week I'm going to make some tests with the mqtt and/or homeassistant restarts
Aight cool!
Did you manage...?
I/ve managed to do the tests but not to replicate the issue
How long do you let the connection be gone? Because it needs to be showing both API and MQTT disconnection for it to happen
Iirc
see i rebooted the HA OS device completely and hass.agent just stops passing values.
even if its all green
so weird
mqtt explorer DOES pickup the values
Could this be it?? https://community.home-assistant.io/t/discovered-mqtt-entities-not-available-after-restart-ha/306900/2
Home Assistant Community
Discovered MQTT entities not available after restart HA
That is exactly what will happen when the payload, published to the Discovery topic, is not published as a retained message. It’s the normal behavior of MQTT. When you publish a payload to a topic, all the clients connected to the broker and subscribed to that topic will receive the payload. The payload is not normally stored on the broker so ...
Is it true that saving the sensors or commands in HASS.agent triggers some sort of a birth signal causing my entities to come back?
so then hass.agent is owrking correctly
but only if the new values are 100% visible in mqtt explorer
now you made me think
but the discovery messages should be persistant
so this doesn't happen
do you have the option to disabled that on maybe?
which option is that?
the mqtt addon works good too afaik
i have retain disabled by default.