Different Buttons = different payload, want to display payload

[JohnneyBoy]

Yep, tried that, and a number of other 'settings', bit of a shame.

[Michael McSharry]

I doubt it, but you can play with some of the misc properties on the Edit tab. Show Values would be reasonable candidate to try. It was a chore to figure out the misc properties to get each of the renderings I was trying to achieve for the Control/Status UIs.

[JohnneyBoy]

I made progress, it was very odd, it looks like the device was added, but when I when back to the device page that gives the recent topics that have been seen, the 'a' box was not clicked. I clicked it, and then the textbox and return value worked. hummm.

Is there anyway of stopping the return value from also being put into the textbox.

Hope this makes sense, if not I'll screen shot.

John

[Michael McSharry]

Looks like the VSP is setup for control only. I believe it needs to be Both if you want status updated. This should happen automatically when you select Number as the Control/Status UI type on the Edit tab. I think this wall also result in the "Includes Values" setting to be enabled too.

[JohnneyBoy]

I have been testing out the free text (textbox) input method.I can see the text going out on the 'command' topic, and see the incoming 'status' topic. But the device value does not get updated.






Regards John

[JohnneyBoy]

Hello,

Ran some tests this afternoon, working just fine, Thank you.

John

[Michael McSharry]

The most current version is http://mcsSprinklers.com/mcsMQTT_5_3_3_3.zip but changes are related to Daikin and not the device name.
Make certain mcsMQTT_2020.dll is not in HS folder, but is in \bin\mcsMQTT folder. The one is the zip is where the logic was updated for the name.

[JohnneyBoy]

Hello,

I have installed as per previous instructions, aka exe and dll. Restarted HS3, looked at an existing mqtt device I had created. It does not seem to have any where to input/or show the device name... am I missing something?

[Michael McSharry]

Added in http://mcsSprinklers.com/mcsMQTT_5_3_3_0.zip

[JohnneyBoy]

Hello Michael,

All is going well.
I have had a thought, In the configuration of the MQTT device screen would it be possible to also have a field to input the device name into, you have the locations, this would make it easier to find the device once setup.

Regards John

[JohnneyBoy]

Hello,

Looks very good, setup a number of tests, all working as expected. Again, thank you.

Regards John

[JohnneyBoy]

Hello,

So far, testing looks good, thank you. I will test more over the next couple of days.

Regards John

[Michael McSharry]

I ran down the problem. The update is at http://mcsSprinklers.com/mcsMQTT_5_3_0_2.zip

Two choices to install.
Disable mcsMQTT from Interfaces page.
One option is extract mcsMQTT_2020.dll and put in in the \bin\mcsMQTT folder. If you also want HS to reflect this version number then copy HSPI_MCSMQTT.exe to the HS folder.
Second option is to copy the zip to \updates3\Zips folder. Extract updater_override.txt from zip and put it in HS3 folder. Browser to HS Interfaces page, Update Listing button, Local Updates, select mcsMQTT. Install. Remove updater_override.txt from HS3 folder.
Enable mcsMQTT from Interfaces page.

It looks to me that in this use case there is a limited number of responses on this topic that reflect its state. This means that VSPs can be setup. Two for the buttons and two (or however many) for the states. This would all be defined in the VSP section of Edit tab. When all done then use HS Device Management to change the VSPs from Both to either Control or Status. Change the numerical value of the Control buttons to be the same value as the corresponding status. If you do it this way then HS DeviceValue will be maintained to match the status returned from the topic and then DeviceValues can be used in events. Status will show the same as what is provided in the topic via the VSP association.

Of course you can also use the new feature I added to store the status from the topic into DeviceString. The downside is that DeviceValue is no longer being maintained.

[Michael McSharry]

It is treating it as a WLED Segment to be controlled. WLED Segments use TCP/HTTP rather than MQTT. I should be able to figure out why the topic looks like a WLED topic.

[JohnneyBoy]

Hello,

Here is the output after pressing buttons SetA and SetB

21/06/2020 09:37:10 81950 | ActoOnMessageForTrigger Topic home/shed/status,Payload=Ready, Triggers=0
21/06/2020 09:37:10 81976 | SetIOMulti 1546, oCAPI.ControlType=Button, MQTTReceiveRefDictionary.Contains=True
21/06/2020 09:37:10 81976 | SetIOMulti Trace 0
21/06/2020 09:37:10 81976 | SetIOMulti Trace 1
21/06/2020 09:37:10 81976 | SetIOMulti Trace 2
21/06/2020 09:37:10 81976 | SetIOMulti Trace 3 Value=SetA
21/06/2020 09:37:10 81976 | SetIOMulti Trace 4
21/06/2020 09:37:10 81977 | SetIOMulti Trace 5
21/06/2020 09:37:10 81993 | SetIOMulti Trace 6
21/06/2020 09:37:10 81994 | SetIOMulti Trace 7
21/06/2020 09:37:12 83664 | HSEvent VALUE_CHANGE| 1024| C55E86C6-010-Q62| 317.5| 317.3| 1408
21/06/2020 09:37:12 84110 | SetIOMulti 1546, oCAPI.ControlType=Button, MQTTReceiveRefDictionary.Contains=True
21/06/2020 09:37:12 84110 | SetIOMulti Trace 0
21/06/2020 09:37:12 84110 | SetIOMulti Trace 1
21/06/2020 09:37:12 84110 | SetIOMulti Trace 2
21/06/2020 09:37:12 84110 | SetIOMulti Trace 3 Value=SetB
21/06/2020 09:37:12 84110 | SetIOMulti Trace 4
21/06/2020 09:37:12 84111 | SetIOMulti Trace 5
21/06/2020 09:37:12 84111 | SetIOMulti Trace 6
21/06/2020 09:37:12 84111 | SetIOMulti Trace 7
21/06/2020 09:37:12 84323 | ActoOnMessageForTrigger Topic home/shed/status,Payload=Ready, Triggers=