[TAMOSTA] Error 500 MQTT Discover

[VonOx]

@atrovato I've a tamosta device up and running publishing on MQTT container configured in MQTT Service.

When I try to discover Tamosta device in MQTT

Gladys UI retrun generic error
Error discovering Tasmota devices.

Nothing in server logs :/

[atrovato]

Ok, you are on v4.0.3 ? I will take a look ASAP.

[VonOx]

Yep latest release , just a question, is this service compatible with tamosta sensors?

[atrovato]

Yes it should. But I develop it based on Tasmota v8 documentation, now it is v9, I may miss some new sensors.
For more, only Gladys compatible sensors are done.
But you can make any request to update service if yours is missing.

[VonOx]

I will check

FYI, http discover sayed that my device is not managed.
( SR04P ultrasonic sensor)

Is error 500 normal in that case?

[atrovato]

That's weird, I don't have to error... maybe due to Tasmota device and ultrasonic sensor...
Sure you don't have any logs on back side?

[VonOx]

Yes for sure, my first check is to verify logs

[VonOx]

Service not started ( Explain error 500 )

[Pierre-Gilles]

@atrovato I had some serious issue too with the task we wrote to avoid the service from starting (when we had the Bluetooth bug), now I agree with you maybe we should remove this...

[Pierre-Gilles]

I was using MQTT and nothing was working, at the end I realized the service was not started because of the task to avoid crash at startup. I think this thing of service "started", "stopped" is not working properly + not explicit enough in the UI

[atrovato]

I created a new issue #1021

[Pierre-Gilles]

Thanks! +1