02.10.2024, 13:08
Check LM Error log. Are you using encrypted or plain connection?
MQTT Client app
|
02.10.2024, 13:08
Check LM Error log. Are you using encrypted or plain connection?
02.10.2024, 13:11
02.10.2024, 13:37
Thanks, the problem is that your server does not support MQTT V5. It is required by the app to filter out unneeded messages. We can add a config option to allow older protocol versions to be used at your own risk
11.10.2024, 10:52
New app version has been published, see the first post.
New features:
(11.10.2024, 10:52)admin Wrote: [*]Added 1-bit Boolean to on/off string conversion[*] Thank you for keeping improving the application and also adding sorting to the table that makes it easier to manage mappings. I have few questions: 1) why you decided to make conversion incompatible with json path? Conversion allowed to simplify /SET topics for relays, but STATUS topics still need to take variable from json path and convert from on/off to boolean using script. I'm not sure why they can't work together. 2) why conversion values are case sensitive? AFAIK /SET commands for zigbee devices are case insensitive, and for STATUS values some send upper case, some send lower case. Of course one can first capture what end-device is sending and put exact value, but i don't see any breaking cases when upper/lower case actually matters. also little fix needed: for "In" mappings, it needs to be called "String to boolean conversion", as we're getting string from MQTT and need to write boolean value
14.10.2024, 11:08
Hi all,
How do i install the app? From system menu it requires signature file.
14.10.2024, 11:09
Apps are installed via app store Use install by file.
------------------------------
Ctrl+F5
14.10.2024, 11:37
Forgot the three lines :-)
16.10.2024, 07:46
App has been marked as stable and published in LM app store.
The latest version allows using JSON path together with boolean <-> string conversion. The conversion is no longer case sensitive for values coming from MQTT.
17.10.2024, 12:13
i have found a bug:
if i set up configuration with an empty "OFF string", it will accept as correct configuration, but any value will write TRUE to the target object. Example configuration attached. My expectation is that any other value will be ignored (i do not expect to write FALSE values in any case, hence using empty OFF string).
17.10.2024, 12:36
It's a feature
Currently both values are required otherwise conversion is skipped. This will be fixed in the next version. |
« Next Oldest | Next Newest »
|