In the embedded device world, updates can be hard to support. Everything is project oriented. The project gets built. The programmers, the hardware designers, and the manual writers get paid; and then almost all of them go on to other things. There is little if any software maintenance.
Not to excuse Schneider, but this is the reality of the embedded world. When was the last time you got a software update for your 3 year old oven, your washing machine, or your refrigerator?
The end users assume all the risk here. It sucks, but that's how it is. Those of you who glibly rant about this as if it were just another app, please get a clue. This device is not meant to be exposed to the internet in any way. Yet many make the mistake of doing just that. It happens because people demand real time data for all sorts of projects that, if they really understood the risks, would not have happened. The engineers either didn't know enough to object or, if they did object, were overruled.
If you want to do something productive, stop making snide remarks amongst yourselves and try educating the world as to why this is a bad thing. You will rapidly see why stories like this are not unusual, and why it is amazing that anything good came of this in the first place (note the age of the product). This is primarily a social, not technical, problem. The solutions are not nearly as easy as they seem.