THR320 Sonoff Tasmota - troubleshooting

[Titou43]

Hello
This is my first real post on this forum, so please be gentle!!

A few months ago I installed Gladys on a Raspberry Pi 4 (8GB) under Docker with updates managed by Watchtower
I also monitor my containers with Portainer
I monitor my Pi 4 notably with Webmin

I decided to go further into home automation by starting to monitor temperatures and relays…
I just acquired a Sonoff TH Origin 20A (THR320) + temperature sensor
I hate having to go via the neighbor to go from my kitchen to the garage, so going through the eWeLink servers NO!! NIET!!

So step 1: flashing the Sonoff to Tasmota with esptool and Tasmota web:
ESP identification
backup
erase
flash
configure Tasmota

At this point I have Tasmota reporting into Gladys after enabling MQTT which created a new container under Docker…

However, and this is where I’m stuck: the THR320 is recognized as a relay but not the temperature (Grrrr)

Not knowing Gladys, MQTT and other Tasmota tools, I think I need to look in the logs, maybe confirm the Tasmota configuration of the THR320…

Can someone explain how to approach this problem?

Thanks

[Barbudor]

Hello

I am one of the Tasmota contributors and I am discovering Gladys Assistant
I saw in the documentation that Gladys supported discovery of Tasmota devices (discovery) but this seems outdated and there have been changes at Tasmota regarding the publishing of discovery MQTT messages.

Historically, Tasmota used the « Home Assistant » standard and published its Discovery messages on the topic homeassistant/..... This mode was notably enabled by using the configuration command Setoption19 1.
But in parallel the Tasmota team developed its own discovery standard which uses the topic tasmota/... in order to offer home automation software a solution independent of « Home Assistant ».

Over time, the Tasmota development team no longer had anyone to maintain the code associated with the « homeassistant » standard and it was decided to disable this code in new releases starting from 11.x
On their side, the Tasmota developers proceeded with the migration by creating a hatasmota plugin for Home Assistant.

In conclusion, if the integration of Tasmota in Gladys depends on the homeassistant standard, this mechanism should be considered obsolete.

I am at your disposal if you need more details

Best regards

[Titou43]

Hello
On my side I tested with and without the SetOption19 option and with a reboot between each attempt…
Nothing changes, the temperature sensor is not detected…

I downloaded the MQTT Explorer client
We can see:

{« sn »:{"Time

[Barbudor]

Did you change the FullTopic config?
On which topic do you see the above message?
Alternatively paste here an excerpt of the Tasmota console log, notably with the STATE and SENSOR messages

[Titou43]

On MQTT Explorer :

Under tasmota/discovery/782184BC276C

{« sn »:{« Time »:« 2022-08-24T17:59:31 »,« DS18B20 »:{« Id »:« 3C6404577D30 »,« Temperature »:23.4},« ESP32 »:{« Temperature »:46.7},« TempUnit »:« C »},« ver »:1}

Under tele/tasmota_BC276C/SENSOR

{« Time »:« 2022-08-24T19:09:29 »,« DS18B20 »:{« Id »:« 3C6404577D30 »,« Temperature »:23.5},« ESP32 »:{« Temperature »:46.1},« TempUnit »:« C »}

[Barbudor]

Can you type the command status 8 in the console and say if the temperature appears in Gladys?

---

I think I’ve found it
It seems that Gladys only supports the DHT11 and AM2301, not the DS18x20
And Gladys may also not be looking for it the right way

See Gladys do not parse Tasmota SENSOR message correctly · Issue #1590 · GladysAssistant/Gladys · GitHub

You need to provide more details about your configuration

[Titou43]

The status 8 command in the Tasmota console gives the following message (in the console):

20:25:46.714 MQT: stat/tasmota_BC276C/STATUS8 = {« StatusSNS »:{« Time »:« 2022-08-24T20:25:46 »,« DS18B20 »:{« Id »:« 3C6404577D30 »,« Temperature »:23.6},« ESP32 »:{« Temperature »:46.1},« TempUnit »:« C »}}

I also find this message in STAT/STATUS8 under MQTT Explorer

But I have nothing in Gladys when refreshing the discovery of Tasmota devices

[Titou43]

I did a quick comparison - cross-test with Home Assistant:
Pour le fun j’ai ajouté deux sondes de température DS18x20

I hope Gladys will be upgraded

[VonOx]

We’ll take a look when we get back from vacation

Thanks for debugging @tiboys and @Barbudor

[Titou43]

I’ll take the thanks for myself??? Lol

I like testing things anyway if it helps Gladys evolve,
It’s almost more interesting than when it works on the first try… you get bored quickly (lol)

il ne faut pas aider à me chahuter et me solliciter

[AlexTrovato]

Hello,

@Barbudor

In conclusion, if the integration of Tasmota into Gladys depends on the Home Assistant standard, this mechanism should be considered obsolete.

Gladys does not depend on the homeassistant standard

@Barbudor

Did you change the FullTopic config?

We want to avoid having to modify the firmware’s default configuration (except for debugging). However, if it is recommended to apply certain options, we will propose them via Gladys.

@Barbudor

It seems that Gladys only supports the DHT11 and AM2301, not the DS18x20

Indeed, device integration is done incrementally; not having the hardware to test, and not monitoring new integrations in Tasmota as they appear, we wait for the community to request them.

@Barbudor

And it may be that Gladys, on top of that, doesn’t look for them the right way

I looked at the ticket on GitHub, the hack is to add the prefix StatusSNS as a key on the last argument of the method.

server/services/tasmota/lib/mqtt/tasmota.mqtt.handleMessage.js

Thanks to @Barbudor for taking part in the discussions around Tasmota; we welcome any best practices to apply that we may have misinterpreted.

Thanks @Titou43 for your feedback, we will integrate your device ASAP. We have the same request for the BL09XX.

[Barbudor]

Hello @AlexTrovato
Thanks for your feedback

Regarding the limitation on DHT11/AM2301 sensors (the worst possible on the market😁) why not just ignore the nom-du-chip key? Currently you filter but you don’t use the value of the nom-du-chip key. Why not go straight to \\\\..+\\. ?
The majority of Tasmota users use the DS18x20 for temperature (I’ve seen up to 20 DS18x20 on one Tasmota) or the BME280/HDC1080 for temperature+humidity.
When using more than one DS18x20 for example, the keys are "DS18B20-1":{...}, "DS18B20-2":{...}
Or even (via an option) DS18B20-XXXX using the last 4 digits of the

[Titou43]

Hello
I’m just checking in to see if I can help with testing…

Thanks for your help

[Titou43]

Hello
Quick bump to the developers, were you able to find a bit of time for this topic?

Thanks!!

[pierre-gilles]

For your information there is a PR in progress ( Tasmota: Add more temp devices by atrovato · Pull Request #1570 · GladysAssistant/Gladys · GitHub )

@AlexTrovato Is there a test Docker image?

[AlexTrovato]

I just generated an up-to-date one

[Titou43]

Good evening
You need to tell me a bit more…sorry, I’m new!!
What should I do to test?

Thanks

[pierre-gilles]

Hi @Titou43 !

I had made a post back then that explains how to launch a test image:

Lancer une image Gladys de test?

Alors si c’est dans un but uniquement de test (pas pour développer), il vaut mieux lancer une image Docker « en condition réelle » plutôt que de faire ça dans un environnement de développement (ce qui ne reflète pas vraiment la réalité et n’est pas forcément facile à mettre en place) Pour lancer une image Docker, c’est le même process que décrit sur la page d’installation de Gladys via Docker ( Installation avec Docker | Gladys Assistant ), à savoir lancer un container Docker sur la machine ou …

[Titou43]

Hello…

And ARG I can’t start the MQTT server from the image atrovato/gladys:tasmota

If I enable MQTT in a Docker container it won’t work

[VonOx]

You’re going to have to tell us more about what you did to get there ( we had warned you )