Closed ikke-t closed 3 years ago
seems to origin from tasmota, I created a ticket there: https://github.com/arendst/Tasmota/issues/10796
that was my fault. I used client-id the same as topic, which is not allowed, and sonoff changes the topic to default if done so. This would be great to be checked in ansible and have it fail if set so.
It seems there is still bug in topic setting, I'll do PR
@deveth0 please have a look and give feedback since this is from you. PR is also available.
@ikke-t regarding
This would be great to be checked in ansible and have it fail if set so.
Feel free to create a PR for this. Due to time limitations I can not take care of this.
I updated the sonoff dual with tasmota 9.2. So everything latest. The MQTT topic won't get set up right.
I have both these in my ansible:
and from ansible playbook I can see it both from debug and the actual run that the topic is carried ok:
so definitely the ansible get's the topic for the role, but it doesn't get set in tasmota. The host specific command for topic should not be needed, but I tried forcing it. However, after such run the topic is "tasmota_%06X" in tasmota GUI.