[MQTT Periodic Publication maxed at 10s]

Thanks, @Cara Bereck Levy, looking forward to the fix.

[MQTT Periodic Publication maxed at 10s]

Thanks, will do that, yes. I mean it is not breaking anything for me, it is just annoying making additional timers in ladder just for those cases, when I need to send my daily or hourly aggregations to the server. 

[MQTT Periodic Publication maxed at 10s]

Hi, team!

Just wondering what is the reasoning behind limiting the period to 100 units of 100ms here? What difference would it make if you allowed 10 or 100 times that or am I missing something here?

Aleš

[How to monitor a value change]

Thanks, Robin, will explore that option.

[How to monitor a value change]

Thanks, I am sure it works that way, but I was hoping for some kind of advanced functionality included with Unilogic, like observers or onChange events to not having to add those compare statements for every variable. What I would love to see is having a table of observed variables and set boundaries on them (either fixed or relative) and they would change a "state" of a variable (low-low, low, normal, high, over-the-moon or up-5-percent, down-5-percent)  which you could also use for styling the display on HMI. Right now I am struggling with that too.

Ok, now I am ranting, but thanks for your time and suggestion. Many things can be done in a such a "manual" way, but I am always looking for more automation. That's our business, right?

[How to monitor a value change]

Hello!

I am tracking some values in my application thru MQTT and would like to trigger a publish event if for example a value changes for a fixed amount or percentage. What I am using right now is periodic transfer but would like to save some bandwidth if data isn't changing much. Also, I need some kind of general solution to implement it on 50 values.

Let me give you an example: we are monitoring an outside temperature. The sensor is quite unstable and changes in tenths every few seconds. It's value table at 10am might look like this:

10:00:01    102 = 10,2 degrees C
10:00:02    102
10:00:03    103
10:00:04    104
10:00:05    104
10:00:06    103
10:00:06    103

...  You get the idea. Now, I do not need to transfer these minor changes to my broker every second or on every change. I would like to detect a change of 5 tenths and only then send the data to my server. And periodically every hour for example to have records with timestamps.

What are the possible solutions with UniLogic to achieve this kind of reaction with hysteresis?

Regards,

Ales