Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mac address conflict on sonoff R2 device #21696

Closed
14 tasks
MrX999 opened this issue Jun 26, 2024 · 0 comments
Closed
14 tasks

Mac address conflict on sonoff R2 device #21696

MrX999 opened this issue Jun 26, 2024 · 0 comments

Comments

@MrX999
Copy link

MrX999 commented Jun 26, 2024

PROBLEM DESCRIPTION

A clear and concise description of what the problem is.
I have two sonoff R2 devices that now have a conflict and won't connect to the MQTT broker at the same time. After doing a bit of digging I realised that everything works when you disable the MQTT on either device. I then noticed that they bought have the same Mac address. I have only ever used tasmotizer locally or downloaded directly from the Tasmota web downloader. Never compiled or connect to Arduino etc. recently I replaced one with the backup of the other and stopped using the original. Now that I'm using the original with new setup I noticed the issue with the Mac address. Any idea what to do now? Is one of these now for the bin?

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

  • Read the Contributing Guide and Policy and the Code of Conduct
  • Searched the problem in issues
  • Searched the problem in discussions
  • Searched the problem in the docs
  • Searched the problem in the chat
  • Device used (e.g., Sonoff Basic): _____
  • Tasmota binary firmware version number used: _____
    • Pre-compiled
    • Self-compiled
  • Flashing tools used: _____
  • Provide the output of command: Backlog Template; Module; GPIO 255:
  Configuration output here:

  • If using rules, provide the output of this command: Backlog Rule1; Rule2; Rule3:
  Rules output here:

  • Provide the output of this command: Status 0:
  STATUS 0 output here:

  • Set weblog to 4 and then, when you experience your issue, provide the output of the Console log:
  Console output here:

TO REPRODUCE

Steps to reproduce the behavior:

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

Repository owner locked and limited conversation to collaborators Jun 26, 2024
@Jason2866 Jason2866 converted this issue into discussion #21697 Jun 26, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant