twilit phoenix
Something has broken with my HA install. I can no longer go to the Matter Server page. Just stalls on "Connecting...." I'm not using the Beta, just the standard python server. I've been upgrading a bunch of inovelli switches firmware to their new release over the past day or so. Not sure why that would cause this. Any ideas about how to debug?
I tried restarting my matter server, and then a full Home Assistant reboot. Neither helped.
I'm running a pretty valilla setup: just a HA green with a ZBT-2 antenna.
hollow cove
Can you go to Settings -> Apps -> Matter Server, then the Logs tab? That should have some startup logs from the matter server which might explain what has gone wrong.
twilit phoenix
none of that looks worrisome to me? but maybe others will see something amiss ?
hollow cove
yeah, nothing obvious in there, it looks like a normal startup.
If you click the "open web ui" button from the app page, does that open the ui properly?
twilit phoenix
No, I go to the same place with the same stall on "Connecting...."
hollow cove
there's something weird about the url in your first screenshot. It ends in /core_matter_server, but it should end in /app/core_matter_server.
did you recently upgrade home assistant? try clearing your browser cache.
twilit phoenix
cleared cache. didn't seem to help. also went to /app/core_matter_server manually and got the same thing
also, for giggles, tried connecting with a manual ip address instead of through my nginx proxy. also didn't help (not surprised, but worth a shot)
hollow cove
That's all very strange. Maybe try going to Settings -> System -> Logs and select "Supervisor Logs" in the top right (i think it's the supervisor which is responsible to handling display of app web ui within the home assistant ui)
twilit phoenix
ok, poking around there
willow linden
Does ingress for other apps still work?
twilit phoenix
ya, I just tried the terminal app, and that's working fine
same with file editor
nothing really notable in the supervisor logs. no errors
hollow cove
Is it just the matter server ui that's broken (are your matter devices still working in home assistant)?
twilit phoenix
ya, the devices work. just a UI problem
I am having some connectivity issues with a few decivces, but I suspect that's related to the firmware update I was doing on them.
I dunno why a firmware change would mess up the matter UI though. Seems very odd
willow linden
Anything in the Chrome/web console?
twilit phoenix
hollow cove
interesting, that indicates that the matter server ui is actually loaded, but it's failing to do the backend connection via websocket to the matter server
claims to be a normal connection close
twilit phoenix
that does explain why it would stall on Connecting. the backend is just closing without sending over any data
so the client has nothing to do
willow linden
How many Matter devices do you have?
twilit phoenix
71
63 inovelli switches, 1 aqara door lock, 3 aqara sensors, 4 eve blinds
As I said, I've been updating the firmware on the switches over the last 24 hours. So maybe somehow those firmware updates caused a problem. Seems weird though.
And things were definitely fine last night when I had updated maybe 40 switches. Something happened this AM when I updated 5 more.
Or maybe that's a coincidence / red herring.
honest fox
This problem started for me last fall using the Python Matter Server. Sometimes the page would come back, and then mostly it was inaccessible. I ended up opening up the port on the Matter server configuration page and accessing the web ui that way when I was home. When I was away, I had to use a VPN if I really wanted to see the Web UI (despite my Nabu Casa subscription). I posted a bug about it and didn't get any meaningful response or help and then it was closed. After a while, the page stopped working 100 percent of the time and never figured out a solution. Rebooting, upgrading, etc. didn't help. It was just gone. Ingress has always worked fine for other apps, like Node Red. In the end, the only thing that fixed it for me was installing the beta Matter Server. It's been working 100 percent of the time for the past month or so. (Also, the performance of the beta Matter Server is multitudes better for my 73 Inovelli switches, 2 Aqara locs, 20 Sunricher RGB controllers, and 7 Eve Energy plugs. I can share more about that if you want. But, yeah, you have to be comfortable with beta.)
twilit phoenix
I've thought about upgrading to the beta. I was gonna get through this firmware update first as I kind hate changing two things at once, but maybe I'll just take the plunge.
honest fox
I've thought about upgrading to the beta. I was gonna get through this firmware ...
You could always wait until you do the firmware updates first. Assuming you are home, it's easy to open the port on the Matter Server configuration page and just see the UI there in the meantime. But, yes, I have found the performance of the beta to be life-changing for us. Stability is so much better and my matter disruptions have been short and fast-healing. But we can also use our voice to turn on or off dozens of switches at once without the matter server crashing. So, yes, probably good to do one thing at a time! Good luck!
twilit phoenix
"open the port on the Matter Server configuration page and just see the UI there in the meantime" <--- how do I do this ?
turn this on ?
honest fox
Yep. Then, from the browser go to <ha ip address>:5580
twilit phoenix
ok, gonna try that
thx!
ok that worked great. should get me through this firmware upgrade cycle and then I'm gonna investigate the matter server beta. tysm @honest fox !
honest fox
Great! Good luck! Did you follow the #new-matter-server channel? https://discord.com/channels/330944238910963714/1461119138713047274
twilit phoenix
Yes, I'm in there
limpid furnace
yeah, the HA ingress facadeing the matter server internally (effectively adding authentication) has a payload limit of so and so many KB. The accessed payload json carries much more data than displayed in the frontend. Depending on your device mix and the state of these devices this limit kicks in earlier or later. some see it at 130, some at 170 devices. Opening the port effectively removes that payload limit, but also the data can now be accessed by anyone on your network.
twilit phoenix
Ahhhhh, that makes perfect sense.
I can definitely see how a firmware change would increase the amount of data per device.
I must have just crossed the threshold this AM.
Very iluminating @limpid furnace!
limpid furnace
filtering the unnecessary attributes would probably give quite a bit of headroom, but then nobody was probably interested in fixing this in the dawn of the new server.
twilit phoenix
could the data limit be increased? might be a simple fix to get by until the new server is released out of beta
honest fox
@limpid furnace yes, thanks for this. At the time it happened to me, I was growing the number of devices. For a while there the page would come back and then go away until finally it never came back. I must have gone way over the threshold.
limpid furnace
I am not a HA developer, but I can imagine the limit being there for a reason. Probably the ingress not being streaming. In that case there is no sensible upper limit. Someone will always hit it. Acknowledging that, the server should have made the information accessible in chunks or filter unnecessary attributes or whatever seems fit. Don't know. But yeah, increasing the limit would be an easy fix. At least for some of us.
twilit phoenix
If I get a mintue I'll see if I can track down where the limit is and try bumping it a bit. Just for funsies.
limpid furnace
there is a ticket for that. iirc, the ticket already hints to the code where the constant for the limit is defined. iirc it's about 400k.
limpid furnace
at that time I wondered why that shouldn't be enough, then looked at the json and was surprised how much data is being exposed that we never see in the UI
don't nail me on the numbers, it feels like a year ago or so.
if you find it put it in here. maybe it was even an order of magnitude higher...
twilit phoenix
I'll let you know if I find it.
twilit phoenix
relevant bug: https://github.com/home-assistant/core/issues/146353 marked closed as not planned as was discussed in this thread
