Jan Čermák

@beralios @js4jiang5 @V4ler1an Core has no influence on these log messages whatsoever. Please only report back in this issue if you tried the special OS version I linked above, anything...

@js4jiang5 Thank you very much for the feedback, I'll report it back in the mailing list. About the other issue, it's simply a case of missing `-i` parameter for the...

@js4jiang5 I forgot about this in the instructions, but could you please also send the output of `cat /proc/fs/cifs/DebugData`? If you reverted back to the previous version, you should be...

Hi everyone. Can you post some more details about your setup - especially the complete ESPHome device config? First I thought there might be something in the latest ESPHome or...

I see, thanks for the clarification. This happens when the re-flashing of the original stock firmware (or other firmware using different baud rate) fails, as explained here: https://github.com/joBr99/nspanel-lovelace-ui/issues/862#issuecomment-1510483928 Otherwise the...

What kernel version have you tested with on Raspberry Pi OS? It's a shot in the dark but you can try the [latest dev build](https://os-artifacts.home-assistant.io/index.html) to see if it's resolved...

Thanks for the PR! It will unfortunately conflict with changes from #33, so either we can hold it off until that one is merged, or you can rebase it to...

Do you have any USB peripherals connected? See #3210 for a very similar case.

@muhkuh666 So far we were not able to reproduce the issue and your report lacks any information that could be useful for tracing it. What hardware are you running on?...

This seems to be either a driver kernel regression or AX210 doesn't like the new firmware. I think I have this card somewhere, I will check if I can reproduce.