Topics with arrays, and decimal dot

[stefxx]

Hi, looking for some advice. I have the following topics (from a Shelly 2.5 device):



First, these topics contain an array for both switches of the dual device. What is the best way to handle this? In HS4 I would makes sense to have 2 features for each of those topics.

Secondly, and probably based on my regional Windows settings, the decimal dot is ignored. So I always have to divide the result by 10, 100 or more depending on the number of decimals. It there any way this could be managed more intelligently by the plugin?

Thanks!!

[Michael McSharry]

For the array the control/status type will be CSV. A feature will be created for each array element. Search for CSV in the manual.
For the period use edit tab, inbound subscription, expression row REPLACE($$PAYLOAD:,".",",") or use the regular expression replace \. with ,

[stefxx]

I searched for array in the docs, not for CSV. Now it makes perfect sense.

For decimals, I can't get REPLACE($$PAYLOAD:,".",",") to work. But the regex (replace \. with ,) works fine, I will use that from now on. Much better than dividing by 10 or 100. Still think it would be better if the plugin would handle this internally.

Thanks for your ongoing support! I appreciate the plugin more every single day. It seems to have a solution for almost every situation

[Michael McSharry]

Glad it is working. I tried REPLACE function and worked for me when replacing one number for another. I will leave it alone.

I suspect I could do the substitutions automatically if the user has selected a control/status UI that expects numbers. I put this in 5.3.3.2 http://mcsSprinklers.com/HSPI_mcsMQTT_5_5_3_2.zip. Please confirm it works with your regional settings.

[stefxx]

Great! However, it doesn't work for me.

Not sure how you implemented this, but instead of replacing dots with comma's, it might be easier to just do

System.Convert.ToDecimal(MQTT-value, New System.Globalization.CultureInfo("en-US"))

which should always work, any region, as long as it is a valid number. I use this in my plugins when reading JSON values (which also have decimal dots).

[Michael McSharry]

I put your suggestion in the attached.