I’ve recently encountered a glitch where my FX30 is sending three messages instead of one in the stream. It is not linked to one edge action that I can tell and happens for multiple variables, not just one. In these three messages, the first two messages will have the previous value of a variable, and the last variable contains the correct value. This is causing problems with our program, and we need to fix it.
Is there anything built into the FX30 that would send multiple messages if there was another problem such as bad connection? Or has anyone ever experienced this problem before?
I don’t think we are using any of these features, but I’ve sent you an email with a link to the device. One thing I’ve noticed with the duplicate messages is the delta shown in the stream is higher than our other devices.
I also have this problem on my FX30S devices. But this forwarding of three messages occurs only at the time of device reboot. Just like you described, the first two messages have the previous value and only the third is sent with the current value. It also bothers me a lot, since the gateways sometimes reboot and at that moment they send such spam.
Thanks for sharing and contributing! I do not think that our device is rebooting, but I can look into it. I think we get ~140 instances of these duplicate messages a day, so that would be a lot of reboots. However, it would explain some of the erratic behavior associated with it and why it does not follow any pattern I can see.
Yes the message that is sent contains around 20 variables where some are virtual resources, some are the values of some Energiya inputs (we are using the Universal Converter + and the addON 8i), and some are the FX30 inputs.
And yes, the FX30 is on 3.5.2.
Most likely you know about this, but still I will say: if the cellular network coverage is poor and the cellular network signal disappears, then the watchdog timer built into the FX30S gateway can reboot your gateway. And by default, the value of the watchdog timer is 15 minutes.
Yes, these repeated messages come from virtual resources that, when their value is updated, send it to the stream. So it turns out, in my case, that during a reboot, apparently the virtual resource is updated several times with the previous value written to it, as a result of which these values enter the stream.
I observe this problem throughout all the firmware that I had to test. Probably since version 2.1.4.
Thanks for this info, hopefully this will help @djudkins with his search. I can’t follow much in this other forum post, but I will try to read up on the relevant documentation. If this issue is three years old, I hope it can get resolved.