LoxBerry MQTT

[TomekWaw]

Thanks for clarification Christian Fenzl !

I have global publish settings in FHEM for MQTT:

attr mqttGeneric globalDefaults sub:qos=2 pub:qos=0 retain=1
attr mqttGeneric globalPublish *:topic={"fhem/$device/$reading"}

Now I've tried to add additional attributes to selected devices (and used physically those devices to publish new states to MQTT):

attr Aqara_Button_2 mqttPublish state:topic={"fhem/Aqara_Button_2/state"} state:qos=0 state:retain=0
attr Fibaro_Dimmer_2 mqttPublish s2clicks:topic={"fhem/Fibaro_Dimmer_2/s2clicks"} s2clicks:qos=0 s2clicks:retain=0

But it doesn't seem to do any difference - light controlled by those devices goes crazy as before.
I suspect there is something wrong with that command and retain flag is not changed successfully by this or something else needs to be restarted

PS. I've tried to change qos to 2 with that command:

attr Aqara_Button_2 mqttPublish state:topic={"fhem/Aqara_Button_2/state"} state:qos=2 state:retain=0

and in MQTTLens I still see that states go with qos 0 :/
Shall I restart Mosquito or do something else?

[Christian Fenzl]

Please try this:

https://community.openhab.org/t/clearing-mqtt-retained-messages/58221

Then restart MQTT Gateway.

First focus on a single topic to get that working. You may exactly use that one topic in Subscriptions for testing, so your house (and people) won’t get crazy 😜.

In the log, you see what is received from Mosquitto. A non-retained message is sent and forgot - on a Save or Restart of the Gateway, it shouldn’t be sent again (otherwise it is still retained).

I don’t know, if FHEM-MQTT supports QoS, but it is not relevant for the problem.

[TomekWaw]

Wow, problem solved !

Full FHEM commands I've used:

attr Aqara_Button_1 mqttPublish state:topic={"fhem/Aqara_Button_1/state"} state:qos=0 state:retain=0
attr Aqara_Button_2 mqttPublish state:topic={"fhem/Aqara_Button_2/state"} state:qos=0 state:retain=0
attr Aqara_Button_3 mqttPublish state:topic={"fhem/Aqara_Button_3/state"} state:qos=0 state:retain=0
attr Aqara_Button_4 mqttPublish state:topic={"fhem/Aqara_Button_4/state"} state:qos=0 state:retain=0
attr Aqara_Button_5 mqttPublish state:topic={"fhem/Aqara_Button_5/state"} state:qos=0 state:retain=0
attr Aqara_Button_6 mqttPublish state:topic={"fhem/Aqara_Button_6/state"} state:qos=0 state:retain=0
attr Aqara_Switch_1 mqttPublish state:topic={"fhem/Aqara_Switch_1/state"} state:qos=0 state:retain=0
attr Aqara_Switch_2 mqttPublish state:topic={"fhem/Aqara_Switch_2/state"} state:qos=0 state:retain=0
attr Fibaro_Dimmer_1 mqttPublish s2clicks:topic={"fhem/Fibaro_Dimmer_1/s2clicks"} s2clicks:qos=0 s2clicks:retain=0
attr Fibaro_Dimmer_2 mqttPublish s2clicks:topic={"fhem/Fibaro_Dimmer_2/s2clicks"} s2clicks:qos=0 s2clicks:retain=0
attr Fibaro_Dimmer_3 mqttPublish s2clicks:topic={"fhem/Fibaro_Dimmer_3/s2clicks"} s2clicks:qos=0 s2clicks:retain=0

Then I stopped Mosquito service, removed database file, started Mosquito service again and restarted MQTT gateway.
I pressed all 11 switches to make them publish state to MQTT and to get them shown in Incoming Overview.
After that I clicked "save and apply" on Subscription list and for the first time there was no disco
I also tried adding new "reset after send" flag and it also didn't go crazy.
All Virtual Inputs of those 11 switches keep state 0 during both operations.

I see now, that if I restart MQTT Gateway service, most values show up in Incoming Overview after ~2 seconds,
but not states of those switches. I suppose it confirms that these values have not retain flag anymore.

THANK YOU VERY MUCH, Christian Fenzl .
That was a very clever solution!

[KapeOne]

Moin Zusammen,

so langsam wird's Zeit, mal wieder etwas zu basteln. Versuche mich gerade am Thema "Ultraschall - Entfernungsmessung"

Folgender Aufbau:
- NodeMCU V.3 mit ESPEasy
- Sensor JSN-SR04T
- Loxberry mit MQTT Plugin

Auf der ESPEasy - Seite scheint so weit alles ok, Sensor eingerichtet, Controller (Loxberry - MQTT) eingerichtet, Daten werden verschickt:



Loxberry MQTT-Plugin installiert und Konfiguriert:



Es schaut laut LOG auf dem Loxberry auch so auszuschauen, als käme was vom ESPEasy an:



Unter "Incoming Overview" auf dem Loxberry wir aber nichts angezeigt:



Finde den Fehler - was mache ich falsch, wo habe ich noch etwas vergessen?

[Christian Fenzl]

Kannst du mal F12 im Browser machen, ob es dort einen JavaScript-Fehler gibt?
Und was dort am Tab Network im Sekundentakt hereinkommt (sollte ein json sein).

Es fehlen ja auch die eigenen Topics vom Plugin, also der ESP funktioniert jedenfalls korrekt.

lgcf

PS: Welcher Browser?

[KapeOne]

Kein JavaScript Fehler. Browser Chrome und Firefox (beide aktuell).

Im Sekundentakt kommt da index.cgi rein:

[Christian Fenzl]

Und wenn du auf eines der index.cgi draufklickst, welchen Response zeigt er dann an?

[Christian Fenzl]

Ahhhh
"No Miniservers defined"

Kannst du das mal nachholen ;-)

[KapeOne]

Die folgende:

{
"Noncached" : {},
"health_state" : {
"broker" : {
"count" : 0,
"error" : 0,
"message" : "Connected and subscribed to broker"
},
"configfile" : {
"count" : 0,
"error" : 0,
"message" : "Configfile present"
},
"udpinsocket" : {
"count" : 0,
"error" : 0,
"message" : "UDP-IN socket connected"
}
},
"http" : {},
"resetAfterSend" : {},
"udp" : {}
}

[Christian Fenzl]

"No Miniservers defined"
Kannst du das mal nachholen ;-)

[KapeOne]

Ooops - warum auch immer, nicht sauber abgespeichert nach dem neu aufsetzen.

Am Ergebnis hat das aber nix geändert .

[Christian Fenzl]

Jetzt bist du Verursacher von zwei Issues :-)

https://github.com/mschlenstedt/Loxberry/issues/1077

https://github.com/christianTF/LoxBerry-Plugin-MQTT-Gateway/issues/34

[KapeOne]

Geil - hab dafür mal auf den Spenden-Button geklickt ;-)

[Christian Fenzl]

Danke, der funktioniert :-)

[Federbein0815]

Seit einiger Zeit läuft mein Mosquito Service nicht mehr. Habe den Loxberry Neu gestartet, das Plugin Deinstalliert und wieder installiert, die User Cred deaktiviert, die Miniserver Cred vereinfacht (ohne Sonderzeichen). Jedoch hat das alles inchts geholfen. Per SSH komme ich auch nicht auf den loxberry. Anbei der Log des MQTT Brokers.

18:57:11.089 INFO: LoxBerry Version 2.0.0.2 ( is_raspberry.cfg )
18:57:11.089 INFO: MQTT Gateway Version 0.8.3
18:57:11.089 INFO: Loglevel: 7
18:57:11.127 INFO: KEEP IN MIND: LoxBerry MQTT only sends CHANGED values to the Miniserver.
18:57:11.128 INFO: If you use UDP Monitor, you have to take actions that changes are pushed.
18:57:11.151 cfg mtime: 1572198820
18:57:11.151 cred mtime: 1572198553
18:57:11.151 OK: Reading config changes
18:57:11.151 OK: MQTT Gateway topic base is loxberry/mqttgateway/
18:57:11.154 JSON Dump:
18:57:11.155 $VAR1 = {
'subscriptions' => [
'sonoff/#',
'beca/#'
],
'Main' => {
'udpinport' => '11884',
'brokeraddress' => 'localhost',
'convert_booleans' => bless( do{\(my $o = 1)}, 'JSON::PP::Boolean' ),
'use_udp' => $VAR1->{'Main'}{'convert_booleans'},
'pollms' => '50',
'msno' => '1',
'udpport' => '11883',
'use_http' => bless( do{\(my $o = 0)}, 'JSON::PP::Boolean' ),
'enable_mosquitto' => '1'
}
};

18:57:11.156 INFO: MSNR: 1
18:57:11.156 INFO: UDPPort: 11883
18:57:11.156 INFO: Connecting broker localhost
18:57:11.156 INFO: Login at broker
18:57:11.156 INFO: Sending Last Will and Testament
18:57:11.159 INFO: Subscribing sonoff/#
18:57:11.159 INFO: Subscribing beca/#
18:57:11.159 INFO: Subscribing loxberry/mqttgateway/#
18:57:11.170 OK: No conversions set
18:57:11.170 Creating udp-in socket
18:57:11.171 OK: UDP-IN listening on port 11884
18:57:11.172 Creating udp-in socket
18:57:11.172 OK: UDP-IN listening on port 11884
18:57:11.183 INFO: Relayed topics are saved on RAMDISK for UI
18:57:17.010 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:57:23.044 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:57:29.014 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:57:35.041 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:57:41.008 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:57:47.039 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:57:53.005 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:57:59.033 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:58:05.060 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:58:11.025 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:58:12.002 INFO: Relayed topics are saved on RAMDISK for UI
18:58:17.014 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:58:23.040 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:58:29.006 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:58:35.033 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:58:41.001 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:58:47.035 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.
18:58:53.005 WARNING: No connection to MQTT broker localhost - Check host/port/user/pass and your connection.

Danke und mit freundlichen Grüßen

[Christian Fenzl]

Hast du mit dem 2.0.0.2er Image begonnen, oder mit einem früheren Image, oder von 1.4.2 aktualisiert?
Definitiv läuft Mosquitto nicht, aber erst muss SSH funktionieren.
Hast du Monitor und Keyboard am Raspberry?

[Federbein0815]

Ich habe mit einer 0.X.X begonnen, bin von Anfang an dabei. Habe nun ein Backup wiederhergestellt von 2.0.0.1, da funktionierte noch SSH. Anbei die Fehlermeldung der Console

[Christian Fenzl]

Sehr gut - Michael hat für kurze Zeit mal die SSH-Config zerlegt, das sollte gefixt sein. Du kannst also wieder auf 2.0.0.2 updaten.

Danach mach bitte mal

sudo apt-get install —reinstall mosquitto

Danach sollte es gehen, oder wir müssen weiterschauen.

Du musst im Gateway danach nochmal speichern, damit die Credentials übernommen werden.

Es ist wahrscheinlich ein Problem mit dem Logverzeichnis. Das ist zwar in LB schon gefixt, aber wenn du alle Updates mitgemacht hast, zieht das wahrscheinlich nicht mehr rückwirkend.

Backup war eine gute Entscheidung 😉

LG, Christian