Home Automation Domotica Forum Europe, Bwired Forum

Hi, is HS restarted in the meanwhile? Can you enable the logging in the MQTT plugin (MQTT Config page, set loglevel to WARN). What is in the logging when you disable and enable the plugin. It seems that the settings are not stored in the database, maybe the logging gives me more info. Regards, Geert...

Hi, The issue is that the URL parameters (as used in the Homeseer webpages) are encoded as 'parameter=value'. If the 'value', i.e. the event parameter, contains the '=' sign, there is no way to differentiate between a 'parameter=value' and a value containing the '=' sign. They are all handled as 'pa...

Hi,

the 'monitor' broker setting is non-persistent. Idea at the moment of implementing was to prevent a flood on subscriptions, so it is not a bug - it is a feature.

Regards,
Geert-Jan

Mario, did you upgrade from a previous MQTT version recently? The error points to the fact that the plugin cannot find the MQTT configuration stored for the device. Can you check the content of the MQTT plugin / Subscription page. You should egt an overview of all the MQTT topics, including the Home...

Hi,

in the "MQTT / Publish" configuration screen you can change the default topic name. (for the value update only, the string value is always published using the default topic)

Regards,
Geert-Jan

Deleting the device should be sufficient. If you stop and start the plugin the list of subscriptions is rebuild, maybe that can help.
What is exactly conflicting?

Regards,
Geert-Jan

Hi, change &hs to &nhs and it should work. &nhs.PluginFunction("MQTT", "", "publish", {"/LED_DEN/cmd", "lcd,1,1,hello world"}) In a script you can use: dim result as object result=hs.PluginFunction("MQTT", "", "pu...

Hi, difficult to say with limited information. Can you check the logging of the MQTT broker? Maybe the connection with the broker (or its clients) gets lost. Also check the configuration of the MQTT plugin; the QoS for publish is per default set to 'Exactly once'; the message is delivered only one t...

Hi, strange issue; I could not reproduce this in my homeseer test virtual machine (which probably differs from a RPi2 set-up, which I do not have available at the moment). The mqtt.ini file is not part of the installation, it is created when the plugin is started. To enable debug logging create mqtt...

Hi, you used the RPi version from this thread? That version is quite outdated and I do not know if it still works with the current homeseer version. Also that version has limited logging and configuration capabilities. Better install the plugin via homeseer. If you are not able to adjust the logleve...

Hi, which version of the MQTT plugin are you using? Can you set the loglevel of the MQTT plugin (via the Config page) to LOGLEVEL_INFO and stop/start the plugin to see what happens. This gives me more data to troubleshoot this issue. Note that you will get a lot of messages in the logfile, so turn o...

Hi, which HS3 version and which OS are you using? Can you check if the following file exists in your HS installation folder: 'Data/HS3MQTT/hs3mqtt.sqlite'. The installer should install this empty database file. Also check the access right, the HS user should have read/write access to this file. Than...

Hi,

in the configuration I see that you connect anonymous to the MQTT broker, and you also supply username/password.

If the MQTT broker needs a username/password than uncheck the 'anonymous' flag.

Regards,
Geert-Jan

Hi,

in the current version the port number cannot be changed. I plan to implement this together with the TLS/SSL support.

Regards,
Geert-Jan

Interesting feature request, that already popped-up several times. Makes Homeseer a bridge between MQTT and other protocols like z-wave. It is on the feature list, but due to my limited time, what has a higher priority: TLS/SSL encryption support or this request to control HS devices via MQTT? Regar...