LoxBerry MQTT

[Christian Fenzl]

Probier
test <v>

[Davejje]

Funktioniert!

So simpel und doch übersehen. Danke für die Antwort!

Es ist beispielsweise auch möglich, separate Conversions pro Thema zu erstellen

Test:
Aus = 0
Starten = 1

Test 2:
Starten = 0
Aus = 1

[Christian Fenzl]

Conversion pro Topic: Echt? Nicht das ich wüsste...?
Oder war das eine Frage?

[Davejje]

Das war eine Frage, aber ich denke, Ihre Antwort gibt mir bereits eine Antwort.

[w4Rd3n]

Guten Morgen.
Kann mir jemand sagen wie ich am einfachsten Temperaturen von Loxone an den MQTT Gateway schicke ?
Ich will ein paar Trends extern besser darstellen um meine Heizung zu optimieren..
Vielen Dank
Grüsse
Angelo

[Christian Fenzl]

https://www.loxwiki.eu/pages/viewpage.action?pageId=39356011

Für jede Temperatur erstellst du einen Vietuellen Ausgangsbefehl, und dort hängst du jeweils die Temperatur an.

[w4Rd3n]

Ich sende den Temperaturwert über UDP . Jedoch klappt etwas noch nicht. Würde aber gerne lieber über HTTP senden.
Wie muss ich das in Loxone programmieren. Gibt es ein Beispiel dazu ?
Grüsse

[Christian Fenzl]

Senden Loxone->MQTT ist einfacher und schneller per UDP.
Zeig was du hast.

[Gast]

Hellow from my side.

I am new user of loxberry and I have first troubles :-)
I want to use shelly swtich 2.5 trough loxone.
When I finished with installation of MQTT I got next errors.


I uninstall MQTT and after that install one more time. I got same error.
Is it that ok?
And second trouble, I can not see any virtual input from shelly on incoming overview.




Thanks in advance for any help.

With best regards.
Jery

[Christian Fenzl]

For installation errors: Please send the full log.

But MQTT seems so work.

Please double-check this: https://www.loxwiki.eu/display/LOXBE...shooting+Guide

Furthermore, double-check user/pass you‘ve copied from the plugins Settings page to the Shelly webpage.
Check that in plugin‘s Subscription page shellies/# is subscribed.

Regards, Christian

[Gast]

I checked five times user/pass and read troubleshooting guide, but I don't have any idea what is wrong.
Subscription page is clear, no one shellies inside :-(


In the attachmet please find full log. As you can said MQTT looks good.

Regards.
Jery

[Christian Fenzl]

Could you please enter the SecurePIN on the Settings page, press Save & Apply, and after that, the right Restart button.
Check in the footer line if Mosquitto goes to green again and gets a new PID.

It seems that Mosquitto still has a problem with a plugin config file (I thought I fixed this).

If this does not work, please install the plugin again, but without uninstalling it before. This should re-write all the configs, re-set the permissions and renew the symlinks.

[Gast]

Yes, masquitto get new PID.
But I still don't see any input from shelly.

I install MQTT one more time without any error.

[Christian Fenzl]

In Shelly, try to use loxberry's ip instead of the hostname.

I tried this, but still don't see any input.
I don't have more idea what to do :-(

For connect to shelly I use direct IP adress, if I use host name I can not reach shelly.
I mean from web browser.

[Christian Fenzl]

Please update your screenshots from both MQTT "Settings" full page and Shelly, including passwords. If it is a secure password, change it first on both endpoints.

Include IP settings from both devices.

You are sure, that LoxBerry and Shelly are in the same subnet?

[Gast]

I get static ip/subnet on loxberry and shelly.
System work now :-)
thank you for your help.
Have a good night.
Regards.
Jery

[Gast]

Good morning everyone.
I made some tests with shelly switch 2.5 yesterday and my opinion is next. The system works stable but I see one thing. Delay time between press the button and switch light ON is approximately 1-3s.
Is that normal? I use raspberry 3B. Do we have lower delays if I buy raspberry 4 with 4GB of memory? What is your experience with this?

Regards.
Jery

[Christian Fenzl]

The MQTT Gateway usually takes about 1-2% CPU, so this usually isn’t the problem. It may be, that LoxBerry had installed os updates, that would slow down the Pi for a while, after the initial image installation.

Delays may depend to the block in Loxone you are using, and your light itself (LED lights may have a delay).

For testing, connect to output to a Loxone switch Block (not light controller), and measure the “switch until click” time (click of relay).

Don’t trust neither the Incoming Overview nor the Shelly visu about timing, as both have delays to show the current status.

[Aleq]

Hi guys,
do you also have a problem that REST triggers with to virtual input don't get always recognized? I have there:

shellies_shellyplug-s-51CC26_online
(Topic [I]shellies/shellyplug-s-51CC26/online[/I])

with

• Disable cache [X]
• Reset after send [X]

Then I monitor the Miniserver log and can confirm the HTTP requests are coming in. But they are not always recognized by the Loxone program. I have hooked many various controls to make sure it's not the fault in the program. E-mails, Tracker, ... all the same.
Right now I have in the Tracker:
- 05:45:42 PM
- 05:44:42 PM
- 05:42:41 PM
- 05:37:40 PM

I am triggering updates on Shelly devices every minute. MQTT Explorer shows connects coming every minute. HTTP request in Loxone monitoring the same.
So I wonder, is it by any chance by too short time inbetween ON and OFF?

These were not recognized, for instance:


I am on Loxone Config 8.3.3.21 if it matters? Hope not, I am staying intentionally on 8.x

Thanks!
Aleq