forum

Hello

Trying to make MxMQTT subscriber to get figures from the broker after a disastrous update.
Display Current MQTT Connection State
for Create virtual device
you typicaly need to give Device Title and indicate Icon

I dont remember what to write in the Icon field, hence nothing works ; cant save changes

please help
Had this working like champ prior to latest update..

I guess the MxBasemodule Library isnt properly installed?
> Copy the app folder on the server computer to userModules folder. how do I make this on a raspi with mosquitto running?

Trying to make MxMQTT subscriber to get figures from the broker after a disastrous update.

I hope it wasn't an update of MxMQTT Subscriber or MxBasemodule Library.

Do you use the latest update of MxMQTT subscriber V1.2.6?

you typicaly need to give Device Title and indicate Icon. I dont remember what to write in the Icon field, hence nothing works ; cant save changes

I thought the text is clear:
- Without path and without extension: standard zway icon.
For example: alarm, temperature, ...
- Without path but with extension: local icon from htdocs folder (not hfdocs, there's a write error).
For example icon.png or any other icon you put to the local htdocs folder.
- With path and with extension: icon from different location.
Insert whatever you want, <path>/<file>.<png, even a URL.
In this case simply use the presetting: icon.png.
Additional hint: some things cannot be changed after once it's stored, like this icon.
Workaround: disable the instance, duplicate it, change the value and save the new instance.

I guess the MxBasemodule Library isnt properly installed?

Install MxBasemodule in the same manner as all other modules:
- download from store (V3.8.1)
- if it isn't installed: add app + store
- or if it is already installed: open and store again, if you think there's a problem with it

Copy the app folder on the server computer to userModules folder

This text is very old and obsolete. download the latest version.

Base model is 3.8.1 ; the shell script “automation/userModules/MxBaseModule/sh/execShell.bash” to put in .syscommands, Is this necessary ?

I'm on 4.1.0 and have had some issues with the upgrade.
Is the latest Mxmodules tested on 4.1.0 ?

I'm evaluating reverting to 4.0.3 instead of trying to make things work on 4.1.0 , but if its supposed to work I'll give it a try

Hardware
Vendor: RaZberry by Z-Wave.Me
Vendors Product ID: 1024 / 2
Z-Wave Chip: ZW0500
Firmware
Library Type: Static Controller
SDK Version: 6.82.01
Serial API Version: 05.39
Software Information
Version number: v4.1.0-23-g89a32d68

Base model is 3.8.1 ; the shell script “automation/userModules/MxBaseModule/sh/execShell.bash” to put in .syscommands, Is this necessary ?

The entry in .syscommands is not necessary for MxMQTT Subsciber. It doesn't use this function.

Is the latest Mxmodules tested on 4.1.0

I've upgraded to 4.1.0 at 19.6.23. Everything is running since that time without problems.

Back on 4.0.3 and MxMQTT Subscriber works like before; without the shellscript in .syscommands

goodbye 4.1.0

thanks a lot !

I'm glad to hear that.

Your case is a good example of the importance of documenting the parameters.
The MxInfo2 Tool Collection provides a convenient way to do this.
The InstanceCompare item allows you to create documentation for all your modules. Use Print to PDF.
Install it from app store.

Hello
I hope you are more successful than me with the 4.1.0

Need a tip regarding an app for calculating the relation between two subscriber element > to create a new element

"Price Now" / "Price Max" > gives a number less than or equal to 1 [Energy Cost Level]
A virtual element "Energy cost High" is switched ON when "Energy Cost Level" is higher than .98 or whatever.

Mathematica gives a number for "Price Now" / "Price Max" when Units are set to NOK !!!

magic ...