Shims issue after upgrade

[roquej]

Have this configuration, that was working great before the upgrade bonanza.

Screen Shot 2022-06-06 at 12.33.17 PM.png (131.04 KiB) Viewed 3330 times

Screen Shot 2022-06-06 at 12.33.17 PM.png (131.04 KiB) Viewed 3330 times

Now, not getting anything in the logs, even with Shims set to "verbose debug". MQTT Connector seem to be working:

MQTT Connector Debug MQTT Broker: processReceivedMessage: homeassistant/climate/house_nativezone/temperature, payload: 76

But the trigger never gets nor shows in the log.

Ideas?

[FlyingDiver]

Unfortunately, not really. Have you tried just recreating that trigger?

[roquej]

I deleted the trigger and recreated it. Rebooted.

MQTT message is correct:
MQTT Connector Debug MQTT Broker: processReceivedMessage: homeassistant/sensor/house_nativezone_temperature/state, payload: 75

Logging is set to debug. The trigger never hits.

Again, this was working well before the upgrades.

As a nice, I am using ShellyMQTT and everything works there.

There is something going on with the MQTT Connector or the MQTT Shims plugins.

JP

[FlyingDiver]

I deleted the trigger and recreated it. Rebooted.

MQTT message is correct:
MQTT Connector Debug MQTT Broker: processReceivedMessage: homeassistant/sensor/house_nativezone_temperature/state, payload: 75

Logging is set to debug. The trigger never hits.

Again, this was working well before the upgrades.

As a nice, I am using ShellyMQTT and everything works there.

There is something going on with the MQTT Connector or the MQTT Shims plugins.

If the trigger never fires, it's not getting to the Shim. So it would have to be a connector issue.

That's a different topic than the ones from the screen shots. Previously you had "climate", now "sensor". Is this two different topics, with two different triggers? Both failing?

Any chance you can replicate this with a new database with just the trigger in it? Probably don't even need a shim.

[roquej]

1. downgraded both MQTT Connector and MQTT Shims. Triggers started working again.
2. upgraded MQTT Shims, triggers continued to work
2. upgrade MQTT Connector, triggers stopped working

There is something going on with the MQTT Connector plugin.

JP

[FlyingDiver]

1. downgraded both MQTT Connector and MQTT Shims. Triggers started working again.
2. upgraded MQTT Shims, triggers continued to work
2. upgrade MQTT Connector, triggers stopped working

There is something going on with the MQTT Connector plugin.

JP

Understood, but on my system they work as expected. So unless I can get something that exhibits the problem I'm stuck. Maybe take your existing database, make a copy, and delete all the non-MQTT stuff?

[FlyingDiver]

Oh, and what's the latest version that does work? Python2 or Python3?

[roquej]

Python 2 v0.4.10

[FlyingDiver]

I deleted the trigger and recreated it. Rebooted.
As a nice, I am using ShellyMQTT and everything works there.

Doesn't ShellyMQTT use the standard MQTT-Connector trigger system? And those triggers show in the log?

[FlyingDiver]

Your issue sounds a lot like this one: viewtopic.php?f=316&t=26222

That was fixed by deleting and recreating all the mqtt devices and triggers. So I never did find out what was wrong with what he had.

I compared the trigger detection code between 0.4.10 and current, and it's essentially unchanged. Mostly formatting changes to clean it up for Python3.

The only thing I have left to try is running your database on my dev system so I can run the plugin through the debugger. I have a few hours to look at that tomorrow, otherwise it'll be the weekend.

[roquej]

Your issue sounds a lot like this one: viewtopic.php?f=316&t=26222

That was fixed by deleting and recreating all the mqtt devices and triggers. So I never did find out what was wrong with what he had.

I compared the trigger detection code between 0.4.10 and current, and it's essentially unchanged. Mostly formatting changes to clean it up for Python3.

The only thing I have left to try is running your database on my dev system so I can run the plugin through the debugger. I have a few hours to look at that tomorrow, otherwise it'll be the weekend.

Finally was able to get the db clean up to send to you. How can I send?

JP

[FlyingDiver]

Sent PM.

[FlyingDiver]

Ok, there's definitely something weird going on. I think it has to do with the processing of the "End" statement in the match list. That's only needed when you have topics of variable length and need to match on both the short topic and the longer topic (which contains the short topic). Such as "foo/bar" and "foo/bar/alpha" both having their own triggers.

In your case, I don't think you need it. So take it out and see if your triggers work. Meanwhile I'll see if I can figure out why it's failing, as I know it used to work.

[FlyingDiver]

Try this pre-release with your existing triggers with the 'End' term: https://github.com/FlyingDiver/Indigo-M ... g/2022.0.3

There's got to be some subtle difference in the way exceptions are handled between the Python versions, as the plugin was using an exception to catch an end of array error to determine if the End term was correct. That worked in Py2, but failed in Py3. So I'm testing for the correct number of topic components differently now, which works in Python3.

[roquej]

That worked.

Cool - thank you!

JP