#HA state issue
1 messages · Page 1 of 1 (latest)
Yes, the state in HA is ’Off‘, when I switch it On via a card in my HA dashboard, the bulb switches On, but the state stays ‘Off‘.
I can’t switch the bulb Off, via the card in my HA dashboard, but I can switch it ’Off‘ via a Philips Hue Dimmer (physical button automated with a Light Group Helper for two Nanoleaf Essentials bulbs via HA).
The Hue Dimmer Switch is also paired to HA via a Philips HueBridge. However… the state in HA stays ‘Off‘, even though I switch it On via the Philips Hue Dimmer.
My bulbs aren’t paired to Apple Home or the Nanoleaf app. I removed all my Nanoleaf bulbs from MultiAdmin to get stability in the meshing procedure. My bulbs are bridged from HA to Apple Home via a HA HomeKit Bridge.
Switching this bulb On/Off multiple times, did not produce any logbook entry. Look here, it’s empty and in the state ‘Off‘:
Regarding Test 1: You mean this‘Reload‘ button in the context menu of the Matter integration?
Regarding Test 2: You mean this ‘Restart Home Assistant‘ button?
Test 3 is clear to me, but I can’t use other ’apps‘ than HA.
Thanks for the extensive info - so that rules out multi admin. Good to know, that narrows it down already a fair bit
yeah
use any app, so that may also be HA;-)
Ok, let me try that.
Is my understanding of test 1 correct?
before I start, I want to be sure.
😉
yes it is correct
with behaves you mean it still exist ?
yes, but wait, I will give you a video in some secs. IMO its slightly different. I will describe what you see.
But I am unsure about the difference. I didin't test it this way before the reload. At least this what I think... 😄
In the video you see, that I open the Matter bulb ’Wohnbereich Spot 2‘ in the Matter integration. Then I scroll down to the logbook. The log entries you see were written, when I reloaded the Matter integration.
Then I switch the bulb on, but it switches off after some seconds automatically, without me doing anything. I scroll down to the logbook again and you do not see any new log line. I repeated the tests. But it didn’t help.
In the last test of the video I recognized, that when I am fast enough, I can switch the bulb off again. For that I have to press the switch before it goes back to off by itself.
Give me a sign, when you want me to start test 2. Or should I do something else?
Yeah, that is clearly a lack of state updates. To be clear: the light actually did toggle right ?
Toggling the bulb ’On’ always works, but to get it ‘Off‘, you need to be fast enough or use a Hue Dimmer Switch in my case.
Yeah, that I understand. Thanks for the clarification
So it seems we indeed have an issue then with subscriptions. We now have multiple reports here on discord and on Github. I had seen the issue myself on my production instance but then I was never able to reproduce it on my test and dev instance.
There was nothing out of interest in the log right ?
I updated my network switches in the night of 23. August 24 (round about 23:00 o'clock). One device (EVE D&W, node id 248) didn't came back to live in HA after that. It stayed unavailable. Over night it also died in Apple Home. In the morning I removed and reinstalled the batteries of node id 248. After the log got really quiet. Yesterday evening I installed HA 2024.08.3 and I recognized the bulbs with that issue. Here ist the complete log from the beginning of the network switch update.
Wait, I switched the 'On level' to 254... by accident, while switching through different apps on my phone. Now the bulb works.
I will post a new video in some seconds
hmmm, ok that is interesting....
can you please have a look at the full Home Assistant logfile ? So not the matter server but the HA
what is the command?
Just go to settings --> System --> Logbook
Here is the video: https://imgur.com/a/8ws2Qtm
When I switched it 'Off', it switched 'On' and 'Off' by itself afterwards.
There is no video in that link
Sorry, there is no 'Logbook'. What do you mean exactly?
Sorry, that was the wrong link. Look here: https://imgur.com/a/FN7R53a
Just the home assistant core log
OK, interesting, so you changed the "startuponoff" setting and that fixed the state updates somehow ?
Sorry, that happened by accident. I don't know what I did, I saw that log in the logfile and than it worked. 🤔
A lot of these WARNING log lines:
2024-08-26 10:21:11.130 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'value' when rendering '{{ value_json.value }}'
And some xiaomi miio errors, I have since ever.
Oof your log is unreadable because of that. You should check your automations and scripts if you can find one that is trying to read json and remove/disable that.
Also this is not the full log but only a fraction
Yeah, I can download the full log, but you can not see much more information and I cannot upload this logfile here directly. I also have to go the way via dpaste.
Here ist it: https://dpaste.org/kG0Tq
Yeah that log is unreadable due to that json error, you should probably fix that first as something is hammering
Yeah, I definitly have to find out, whats wrong, but its not hammering. Only 6 log lines every 2 minutes. I already saw much worser things in the Matter server log... 😉
no no, things being logged is not hammering, that is just verbose logging of progress. In your HA log I see that something is continuously trying to convert that json value and fails. You should fix that for multiple reasons but most important because your log is now completely unreadable
One last question, even though its offtopic for you. Do I understand it right, that the log is coming from my template helper sensor 'sensor.stromzahler_energy_total':
I dont know - could be
I restarted HA again and now the log is much smaller.
nice, and the issue still exists with the non working state changes ?
No, I didn't try that. I am on the fixing the issue that 'hammers' my home assistant core log. 😉
The bulb still works now.
ok, that is strange...
Just wanted to reiterate that I had the exact same issue being shown here on my bulbs.
@unreal vine Do you by chance have an Aqara M3 Hub? I dont think they are certified on Matter 1.3 and am wondering if having that in the thread network makes things janky
No, I do not have any M3 hub (7 Apple Home Hubs/TBRs only). Maybe you can proceed with the tests Marcel described above. I tried a lot of things to nail down my issue in the HA Core Log, but for the moment I do not find the cause for the json error. IMO that issue is unrelated to the state behavior. But it makes it unreadable.
Hi @pine meteor, I found the source of my value_json.value issue. It comes from one of my MQTT devices. I only have two. When I disable the Mosquitto broker, the messages stop coming up. Round about 12 of my 23 Nanoleaf devices currently have the issue. I didn’t check the EVE devices, but I think there should also be such issues. I will let it in that state for today, because it’s late here in Germany. I will try to do the tests tomorrow. Have a nice day
Thanks!
@unreal vine @manic shard is that something which you think got introduced with Matter Server add-on 6.4.1. update (which brought the Python Matter Server 6.4.0), or was that behavior already before observable for you?
@obtuse linden Yes, now that I think about it and look at my backups, it's possible that this is related to the 6.4.1 addon update. I've had these problems for a little over a month now. I had registered this shortly before my holiday and then again after my holiday. I wasn't at home for 2 weeks. I am unsure about 6.3.0 or 6.3.1. I have backups for both.
Should I still do the tests described above by @pine meteor or can I perform the downgrade directly?
Doing those tests is good nevertheless - so would be good for us to know
But besides that we would really appreciate if you can test restoring the backup
You didnt add any new devices since then ?
Just keep in mind downgrade is alwasya bit risky as it restores the old version of the server side data.. So if you added new devices, this might be painful.
I am unsure. But that’s not a problem for me, when it helps to nail down the issue. Shouldn’t I see it in the logs?
Well, any devices you may have added AFTER the 1.3 version backup will become unresponsive and need to be factory reset
Yeah, that’s not an issue for me.
At the moment I am at work. I am unsure, when I can do the tests. I will keep you updated.
No rush, we're glad you want to help with the tests
So, at the moment I had one Nanoleaf Essentials light bulb with the issue. But I did the following, to reduce the logs in the HA Core logs and to have a clean situation:
- stop MQTT addon
- reboot HAOS
I am sure that I will have a MoT device with the state issue, when all MoT device are reconnected to HA Matter server. When I found such a MoT device I will do the tests above.
I've released a Matter Server add-on with some more debugging options.
@unreal vine @manic shard what you describe seems very similar to this issue: https://github.com/home-assistant/core/issues/124503. Can you try what I suggest in my comment?
https://github.com/home-assistant/core/issues/124503#issuecomment-2324670172
I don't know if it's related to this but I updated HAOS, OTBR, Matter, etc on Friday for the first time in many months, and now HA cannot see any of my MoT devices. The logs for both Matter and OTBR look generally OK though.
I’ve honestly had no issues, and other people don’t seem to be reporting anything out of the ordinary
I reverted to the backup of the Matter 5.6.0 version of the addon (the last working version I had) and things are coming back online.
You on the beta matter-server?
Do you mean 6.4.2 that was just released? I'm on 5.6.0.
Thanks for that, but now I am unsure.
I have backups to the following Matter server versions:
6.4.0
6.3.1
6.3.0
6.2.1
Should I do the tests described by Marcel above or should I update to 6.4.2 directly?
I do not have much time at the moment. So, I would prefer the update to 6.4.2, when the chance gets higher to find the issue with that version.
But I can also start with the 6.4.1 tests, than downgrade to any version listed before or upgrade to 6.4.2. I can do whatever you want, but at the moment it’s not clear to me. 😂
In your case reverting to your 6.3.1 backup is easiest, most important because you are not running the beta
Ok, so I will do the downgrade after tests or before the tests? Which beta are you talking about? I see a new Matter server release 6.4.2. But that’s general available and not a beta release.
You do not have the beta toggle enabled is what I mean.
Just downgrade to 6.3.1 and let it run for a while if the issue dissapears with the weird state, no more tests needed other than that
Ok, perfect! That’s easy! 😂
So, I've been back on 3.6.1 for about 3 hours and everything is working as expected at the moment. But it's still too early to say whether it works or not.
For me, disabling the OTBR firewall seems to help with Thread reachability. With it on, I usually have a few unreachable devices but I don't have that when the setting is off.
But we are not talking about unavailable devices. I have available devices, that do not change the state and also do not work as expected, even though they are available. 😉
Some minutes ago I tested most of my 60 Matter over Thread devices. They all still work as expected with Matter server 6.3.1. But I still think it’s too early to say something about the stability regarding the state issue.
Some minutes ago I tested most devices again. They still work as expected, states are also correct. I think the issue is not in Matter server 6.3.1. Let’s wait until tomorrow.
Everything still works as expected.
Thanks for letting us know and do the extra tests - we have identified the root cause and are working on a fix
Today I had a power outage for two seconds. So everything was off power, rebooted, remeshed and reconnected. All works as expected. When you have a new beta release of the Matter server, I could test it. Please tell me, when it is ready for a beta test.
@unreal vine there is a new beta now, 6.5.0b2. Let me know if it works for you, I have first postive reports already 🤞
Ok, installed 6.5.0b2 round about 4 hours ago. At the moment everything looks good. Thanks again for the fix! @obtuse linden and @pine meteor
Hi guys, everything is connected, works as expected and all states are correct. Great! 👍
Here is my logfile from the point where I installed version 6.5.0b2 yesterday evening: https://dpaste.org/cOOhb#L658
HA Matter server 6.5.0beta2 still works here! 😃👍