@Mark you can, just wrap in <span> tags, there are other ways, but depends how technical you want to be

Fox

1)make a virtual datasource binary datapoint, add it to the script context points. Tick the checkbox that this point triggers the script.

we shall call the context point switch.
Then add your mqtt point to the context. We shall call it toggle. It does not need the checkbox to the right filled. Ensure the mqtt point is settable
This is the script.

if(switch.value===true) { toggle.set("on"); } if(switch.value===false) { toggle.set("off"); }

See how you go. I do not use the mqtt client myself, but generally all points can be set - some which send the value back out the data source. I am hoping this is the latter...

Hope this helps

Fox

Hi Mark,

The Modbus read data tool in Mango displays the register result in hexadecimal, so 0x37 is 55. Might the value have changed between the readings? You can use the point locator test tool if you want to decode the register by describing the type of data in the register. Another part of the mystery is that Mango begins its addressing at 0, where associating the values in 1025 and 1026 may suggest modscan uses a base address of 1.

Edit: Also, I find it strange you say Modbus RTU when the screenshot from Mango is of an IP data source.

The url is inside the get call. Not the host part of the header.
You want to 'get' calll the page, you're calling the 192.168... at the root level of the server, not the relay page.

Secondly, your context point var is not used to correlate to being on or off. Since the point is an alphanumeric and not a numeric/binary, your parameters should be:

var parameters = { "turn": info }

You're calling a script but I think you are unaware of how everything works. I take it it has been a long time since you've done this.