Shelly MacAddressMismatchError

Tilmann-Glaeser commented 1 week ago

The problem

Introduction

I have "reorganized" the static IP addresses of all my Shelly Gen1 switches.
I've created a new KVM instance based on haos_ova-13.2.qcow2. (But I can reproduce this error even with older versions e.g. with haos_ova-7.5.qcow2) with a bridge network
I have issues with address mismatch errors for my shelly's
I've read all available threads in regards of this issue from others but I found no valuable help.
I did a factory reset for the shelly's.
I have the issue with Enable CoIoT with mcast and with static IP Address of my HA-Instance
I started HomeAssistant with default loglevel "Debug"
I've installed the ll in HomeAssitant and I've created a tcpdump on the network interface
I have no clue what is causing the sudden wrong ip address change for the device under test.

Scenario: (I've shortened hostname and mac address to the last 5 chars and the IPv4 address (192.168.178.xx) to the last octet) 1st Shelly Device Devicename: OGDLD1 Hostname: shelly1-...70cd4 MAC: ...70cd4 ColoT: mcast IP: .61 2nd Shelly Device Devicename: OGALD1 Hostname: shelly1-...24f14 MAC: ...24f14 IP: .63 ColoT: mcast

Start HA VM (KVM)
Login to Web-UI
The two Shelly Devices are automatically detected
Select the device shelly1-...70cd4
the pop up dialog shows the correct IP address 192.168.178.61
The device is added properly
Go to the device
The connected lamp can be switched on and off successfuly
after a couple of seconds the device became unavailable
error message is shown that a mac address issue is detected "MacAddressMismatchError('Input MAC: E8DB84D70CD4, Shelly MAC: 98F4ABF24F14')"
When a manual reconfiguration is triggered, the pop up dialog shows the IP address from the other device 192.168.178.63
after changing the IP address to .61, the manual reconfiguration is successful and the device is working again for a couple of seconds till it became unavailable again with the same error message.

What version of Home Assistant Core has the issue?

core-2024.11.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Shelly

Link to integration documentation on our website

https://www.home-assistant.io/integrations/shelly/

Diagnostics information

Shelly-debug-log.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 week ago

Hey there @balloob, @bieniu, @thecode, @chemelli74, @bdraco, mind taking a look at this issue as it has been labeled with an integration (shelly) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `shelly` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign shelly` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

shelly documentation shelly source _{^{(message by IssueLinks)}}

Tilmann-Glaeser commented 1 week ago

I hope that someone can help, because I am very frustrated. I've spent hours in investigations. I can provide the full HA debug logfile and the tcpdump as well, if required.

thecode commented 1 week ago

Try to reboot the router

Tilmann-Glaeser commented 1 week ago

@thecode I had already read the comment in other discussions before, that the router should be rebooted. I had therefore already rebooted the router several times. I had also removed all network devices and re-added them to the list of known devices. None of this helped. But your comment rang a different bell. I have a WiFi mesh network consisting of devices from AVM (FRITZ!Box) in the house. After I disconnected all these mesh router devices from their power supply and switched them back on, my Shelly's are working again.

I am glad that the problem was due to the mesh WIFI network. Hence the tip to all those who have the same problems: Reboot all active network devices!

Thank you and best regards Tilmann

home-assistant / core