Need Assistance with installing my Tasmota Switches in HA (Warning I'm totally new to this)

Confessions,
I have many devices already running like 10ea Tuya devices and Shelly integrated into HA.
But setting up MQTT and Tasmota seems way complicated. So I confess my ignorance in advance.
My two test devices are Athom PG03-US16A Switches. They are setup and running Tasmota and I can access them via their IP addresses. I’ve installed MQTT and Tasmota in HA, but nothing is automatically descovered like my other devices, like Tuya and Shelly.
I tried to follow the directions but not nothing seems to work. I’m running the latest version HA 2021.10.7
Can anyone assist me ??

What version of Tasmota is on the devices ?

Did you configure them already on the Tasmota web-interface ?

I think the latest version, as I updated them both when I installed them via their web-interface.
Here’s what the page says…
Program Version 10.1.0(tasmota)
Build Date & Time 2021-12-08T14:47:33

Not sure what you mean by configure them? But they are fully accessible by their Web-Interface.

BTW: I installed a Windows diagnostic program called TasmoAdmin that I saw on a YouTube video and it found both of the Smart Plug devices on my network. But still can’t figure out how to et running in HA.

Thank You for your assistance…

In the web console, enter so19 it should be OFF or so19 0

Is that what shows on your devices?

Screenshot_2022-01-07-17-25-06-07_40deb401b9ffe8e1df2f1cc5ba480b12

This is what was returned…

17:25:51.253 CMD: so19 0
17:25:51.257 RSL: RESULT = {“SetOption19”:“OFF”}
17:25:51.705 LOG: Home Assistant MQTT Discovery disabled.

Can you show a screenshot from

Configuration → Configure Other

Also, restart the device and post the output.

You should have something like this.

After restarting device it should show as connected. If not, you would get some errors in the console log.

Here’s one of three I have installed.

This is Config Other

You’ll need to enter your MQTT User and the Password for your MQTT Host

In the Topic section, I would also name the device. DON’T change anything in the Full Topic field.

In the Other parameters section you can make changes to the Device Name and Friendly Name 1 fields. This would be better than having them named Tasmota2, Tasmota3 etc.

You should be good. :crossed_fingers: Post the output of the console if you have further problems

Awesome Progress … Yes
Well sort of And honestly I’m not sure how, or what I did, Way Complicated , but hopefully I’ll learn as I go along, as I plan to use many more devices
OK Here’s the Problem
MQTT has found my one tasmota1 device that I entered the info on, and it enabled all the about 15 Entities
So I Created a test Card on my main dashboard including many of the Entities. However if I click the ON/Off button, it slides over but immediately goes back to ON

SO It has found the Device Called tasmota1 and all it’s Entities,
But It is not able to Communicate with the device called tasmota1
Any suggestions?

And Thank You so very much this seems so complicated at this point, but with your help, I’m learning

OK, Quick Update… HA does indeed communicate with my new tasmota1 device, however the On/Off function does not work. It will read if I turn it On/Off manually by the WebUi intetface or by using TasmoAdmin program and it says on HA that it’s On or Off, also shows the Energy Readings and Power status etc… But can’t turn on or Off with HA

Getting close.Any suggestions ?

Looks like you are close.

In the screenshot you posted from Config Other,

In the template part, replace it with this template for your device.
https://templates.blakadder.com/athom_PG03-US16A.html

Change the Device Name and Friendly Name 1 to something suitable. eg Bedroom Plug.

In Home Assistant, stop then restart your Mosquitto broker. Check the log outputs here. Click Refresh down the bottom for updates. You should get info from all your devices connecting, also there shouldn’t be any errors.

mq

Also, can you post the output from the console after the device restarts, just to see everything’s ok.

I would do 1 device at a time. Go onto the next one once each device is known to be working as it should.

This is the errors from the Mosquitto broker log…
I prefer to use the Tasmota1 name for the time being if thats ok.
The template you suggested I replace is the one installed. Its is the Anthom Template.

[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] mosquitto.sh: executing…
[00:35:10] INFO: SSL is not enabled
[cont-init.d] mosquitto.sh: exited 0.
[cont-init.d] nginx.sh: executing…
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[00:35:13] INFO: Starting NGINX for authentication handling…
[00:35:14] INFO: Starting mosquitto MQTT broker…
1641706514: mosquitto version 1.6.12 starting
1641706514: |-- *** auth-plug: startup
parse error: Expected string key before ‘:’ at line 1, column 4
[00:35:16] ERROR: Unknown HTTP error occured
[00:35:16] INFO: Successfully send discovery information to Home Assistant.
[00:35:17] INFO: Successfully send service information to the Supervisor.
1641706514: Config loaded from /etc/mosquitto/mosquitto.conf.
1641706514: Loading plugin: /usr/share/mosquitto/auth-plug.so
1641706514: ├── Username/password checking enabled.
1641706514: ├── TLS-PSK checking enabled.
1641706514: └── Extended authentication not enabled.
1641706514: Opening ipv4 listen socket on port 1883.
1641706514: Opening ipv6 listen socket on port 1883.
1641706514: Opening websockets listen socket on port 1884.
1641706514: Warning: Mosquitto should not be run as root/administrator.
1641706514: mosquitto version 1.6.12 running
1641706514: New connection from 127.x.x.x on port 1883. (((Whats this IP for?))))
1641706514: Socket error on client , disconnecting.
1641706515: New connection from 192.168.xx.xx on port 1883. ((((Tasmota2 device))))
403: Forbidden1641706516: Socket error on client , disconnecting.
1641706521: New connection from 192.168.xx.xx on port 1883. ((((Home Assistant IP)))
403: Forbidden1641706521: Socket error on client , disconnecting.
1641706530: New connection from 192.168.xx.xx on port 1883. ((((Tasmota1 device))))

I’ve blocked out any IP’s , not sure if that is a security problem or not. Hope this makes sense.
Thank you again…
Thanks again…

One quick update.
For what it’s worth, I did add another pre-flashed device to the mix by another vendor, and it works perfectly also, as far as energy monitoring and diagnostics … BUT Power Switch DOES NOT Work on this device either… So I’m missing likely one simple setting.

And Thank You so Very Much for your Help !!

I would try changing the device name/topic in the web console. Maybe even restarting the Tasmota integration and test with only 1 device plugged in.

Check if this may help you out too?

https://www.google.com/url?sa=t&source=web&rct=j&url=https://m.youtube.com/watch%3Fv%3D31IyfM1gygo&ved=2ahUKEwjmh_i0iaT1AhVagtgFHXZUB-kQwqsBegQIAxAE&usg=AOvVaw1BytYsTxliDfGCmyVPUuht

OK Thanks my friend. I’m getting close to figuring this out.
I’ll take a look at the link you supplied…

Hey Dexter

As the old saying goes in IT. “If you’re computer is not working, try rebooting it”
Bingo a simple restart of Home Assistant fixed it, and Tasmota Working. YESSSSSS !!!
Still Not sure I have everything exactly as should be. I’ve still got a lot of learning, and this is very addicting and time consuming.
Good thing I’m retired, and lots of free time to tinker…
Thank you again sincerely for your help…

Glad it’s working for you now :tada:

The rabbit hole goes very deep my friend. There are many people on this forum and discord who are more than willing to help out.

Take care :+1: