-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
Received message on illegal discovery topic #123
Comments
I haven't seen this, but will keep my eyes peeled. |
@swa72 v3.1.0 is very old, there are a lot of fixes since that, also the wrong |
Hi, my bad. Will do. Hopefully, this does not end in a big rename orgy of
entities in HA ;-)
Am Mi., 22. Sept. 2021 um 09:54 Uhr schrieb MichaelDvP <
***@***.***>:
… @swa72 <https://github.com/swa72> v3.1.0 is very old, there are a lot of
fixes since that, also the wrong warm water prefix in ha has changed to ww.
Please update.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#123 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEGI2E6I6KINUWB5DCDBVTTUDGDT5ANCNFSM5EPQ6DEA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Stefan Waldherr
Phone +49-151-1131-6967
|
Well, updated to 3.2.1. Same warnings.
Do I have to reset anything in MQTT? |
These are old mqtt entries with retain-flag. You have to remove them from mqtt-broker. |
Michael is correct, these are the old names and need to be removed manually. I've been exploring how to get EMS-ESP to clean up old MQTT topics (I'll create a new issue for this) |
Ok, removed the messages using MQTT Explorer (HA and EMS-ESP were still running). Rebooted HA. All clear :-) |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Question
Recent HA log reports
Device information
The text was updated successfully, but these errors were encountered: