10:45:55] INFO: Setup mosquitto configuration
[10:45:55] WARNING: SSL not enabled - No valid certs found!
[10:45:55] INFO: No local user available
[10:45:55] INFO: Initialize system configuration.
[10:45:55] INFO: Initialize Hass.io Add-on services
[10:45:55] INFO: Initialize Home Assistant discovery
[10:45:55] INFO: Start Mosquitto daemon
1580447755: mosquitto version 1.6.3 starting
1580447755: Config loaded from /etc/mosquitto.conf.
1580447755: Loading plugin: /usr/share/mosquitto/auth-plug.so
1580447755: |-- *** auth-plug: startup
1580447755: ├── Username/password checking enabled.
1580447755: ├── TLS-PSK checking enabled.
1580447755: └── Extended authentication not enabled.
1580447755: Opening ipv4 listen socket on port 1883.
1580447755: Opening ipv6 listen socket on port 1883.
1580447755: Opening websockets listen socket on port 1884.
1580447755: Warning: Mosquitto should not be run as root/administrator.
1580447805: New connection from 192.168.31.20 on port 1883.
[INFO] found mqtt on Home Assistant
1580447807: New client connected from 192.168.31.20 as DVES_B0E649 (p2, c1, k30, u'mqtt').
Great!
I can control my switches via Google Assistant via Google Home - they are switches like any other. Just follow the setup docs. I use the manual config rather than nabu casa but both work.
Also if you add more switches, make sure they have a different topin… (ie don’t use sonoff again)
Ok, a question and an observation about your tasmota device :
question : what .bin did you flash? Not all .bin’s support autodiscovery
observation: your full topic is wrong.
Once HA has seen the device, the device name won’t change even if you change the friendly name.
IF you use MQTT Discovery, the full topic should be set to:
%topic%/%prefix%/
IF you DON’T use MQTT Discovery, the full topic should be set to:
%prefix%/%topic%/
Tasmota will set these AUTOMATICALLY when you enable discovery but will not reverse it if you turn discovery off - you need to do that yourself.