[MSR] Rule do not fire

[toggledbits]

OK. I can see on my Tasmota devices that it doesn't send the retain flag on... and I can't find that in Tasmota configuration... seems like a big hole, actually. I assumed that would be somewhere, and I'm disappointed that I'm apparently wrong.

So, init will be required. However, your init should work with the included template (no need to copy the template to your local config, just put your init after uses_template). If that's not working, I'd like to know.

EDIT: I found it... it's obscure. In the Tasmota console (it's not in the GUI), you need to type each of:

PowerRetain on 
SensorRetain on
StateRetain on
SwitchRetain on

For your temperature sensor, SensorRetain may be sufficient, but I don't see why you would not use it for other types as well.

[Crille]

@crille said in Issue with Tasmota sensors and MQTTController later than 22024:

I've set SensorRetain 1 in Tasmota and the value is now retained in openLuup

Yes, I've done that but the value does not get set when I restart MSR for some reason.

[toggledbits]

I had to restart my Tasmota device to get it to work, and of course, force state/value changes on the device to get it to send a first message with that flag set.

[Crille]

This is from openLuup retained messages:

[toggledbits]

Here's what my log looks like with Mosquitto broker and the Tasmota device disconnected from power (so unable to publish -- anything Tasmota is therefore retained and sent from the broker):

[###BUILDVERSION###]2022-04-03T17:37:38.285Z <MQTTController:null> Module MQTTController v22092
[###BUILDVERSION###]2022-04-03T17:37:38.323Z <MQTTController:5:Controller.js:90> [MQTTController:constructor] created controller mqtt
[###BUILDVERSION###]2022-04-03T17:37:38.323Z <MQTTController:INFO> instance topic ident is mqtt
[###BUILDVERSION###]2022-04-03T17:37:38.376Z <MQTTController:5:MQTTController.js:70> MQTTController#mqtt configuring entity blueiris_cam6_motion
[###BUILDVERSION###]2022-04-03T17:37:38.376Z <MQTTController:5:MQTTController.js:70> MQTTController#mqtt configuring entity blueiris_cam13_motion
[###BUILDVERSION###]2022-04-03T17:37:38.376Z <MQTTController:5:MQTTController.js:70> MQTTController#mqtt configuring entity "75e505_1"
[###BUILDVERSION###]2022-04-03T17:37:38.377Z <MQTTController:5:MQTTController.js:70> MQTTController#mqtt configuring entity "75e505_2"
[###BUILDVERSION###]2022-04-03T17:37:38.377Z <MQTTController:NOTICE> Connecting to broker mqtt://192.168.0.66:1883/
[###BUILDVERSION###]2022-04-03T17:37:38.377Z <MQTTController:5:MQTTController.js:241> MQTTController#mqtt connecting to mqtt://192.168.0.66:1883/ with options [Object]{ "reconnectPeriod": 15000, "clientId": "reactor_drupal_mqtt", "connectTimeout": 10000, "resubscribe": false, "will": { "topic": "reactor/mqtt/LWT", "payload": "offline", "qos": 1, "retain": true, "properties": { "willDelayInterval": 30 } } }
[###BUILDVERSION###]2022-04-03T17:37:38.474Z <MQTTController:INFO> connected; opening subscriptions
[###BUILDVERSION###]2022-04-03T17:37:38.477Z <MQTTController:INFO> Sending inits and going online!
[###BUILDVERSION###]2022-04-03T17:37:38.478Z <MQTTController:NOTICE> Controller MQTTController#mqtt is now online.
[###BUILDVERSION###]2022-04-03T17:37:38.488Z <MQTTController:5:MQTTController.js:521> MQTTController#mqtt handling tele/tasmota_75E505/STATE for "75e505_1": {"Time":"2022-04-03T18:32:34","Uptime":"0T00:10:10","UptimeSec":610,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER1":"ON","POWER2":"ON","Wifi":{"AP":1,"SSId":"SupremeGarden","BSSId":"44:D9:E7:03:C7:3A","Channel":6,"Mode":"11n","RSSI":54,"Signal":-73,"LinkCount":1,"Downtime":"0T00:00:04"}}
[###BUILDVERSION###]2022-04-03T17:37:38.489Z <MQTTController:5:MQTTController.js:626> MQTTController#mqtt setting Entity#mqtt>75e505_1 power_switch.state=true
[###BUILDVERSION###]2022-04-03T17:37:38.489Z <MQTTController:5:MQTTController.js:521> MQTTController#mqtt handling tele/tasmota_75E505/STATE for "75e505_2": {"Time":"2022-04-03T18:32:34","Uptime":"0T00:10:10","UptimeSec":610,"Heap":26,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"POWER1":"ON","POWER2":"ON","Wifi":{"AP":1,"SSId":"SupremeGarden","BSSId":"44:D9:E7:03:C7:3A","Channel":6,"Mode":"11n","RSSI":54,"Signal":-73,"LinkCount":1,"Downtime":"0T00:00:04"}}
[###BUILDVERSION###]2022-04-03T17:37:38.489Z <MQTTController:5:MQTTController.js:626> MQTTController#mqtt setting Entity#mqtt>75e505_2 power_switch.state=true
[###BUILDVERSION###]2022-04-03T17:37:38.494Z <MQTTController:5:MQTTController.js:521> MQTTController#mqtt handling stat/tasmota_75E505/POWER1 for "75e505_1": ON
[###BUILDVERSION###]2022-04-03T17:37:38.494Z <MQTTController:5:MQTTController.js:626> MQTTController#mqtt setting Entity#mqtt>75e505_1 power_switch.state=true

You can see on line 10, it says connected; opening subscriptions, and then immediately thereafter it gets the retained messages from the broker. You should be able to confirm similar behavior at log level 5. Given that retain is a new feature for openLuup, I would suggest you confirm it's actually sending the messages; clearly it knows it should, but that doesn't prove it does.

[Crille]

Yup, that's it. I moved the Tasmota device to Mosquitto and can replicate your log. So with openLuup I have to use init as it does not seem to respond with the retained messages at MSR startup.
I will consider moving all my devices to Mosquitto in the future, except for those I need to do Luup calculations and variable sets on virtual devices.

Oddly the rebuild seems to resolved most of my problems and I'm now up to date with the MQTTController, which was the main issue. Thank you very much for that!

[toggledbits]

No worries!

Paging @akbooer.... see the last couple of messages above. Apparently @Crille has some retained messages (they show as retained in the openLuup UI) that are not being sent by openLuup's broker when Reactor subscribes. FYI, Reactor uses a "catch-all" subscription (complete wildcard, i.e. # is the entire subscription request).

[akbooer]

@toggledbits

Thanks for the heads up. Clearly something missing here that needs to be investigated.

[akbooer]

@Crille

What topic(s) are you subscribing to which isn't sent? I have found a possible error if it contains a wildcard, but just wanted to check. Thanks.

[toggledbits]

@akbooer It's Reactor that's subscribing, and as I posted earlier, Reactor subscribes with # alone, so it's 100% wildcard ("give me everything").

[akbooer]

Ah, OK, I wasn't clear. I am now. That's clearly a bug. Thanks.