We use cookies to try and give you a better experience in Freshdesk.
You can learn more about what kind of cookies we use, why, and how from our Privacy policy. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies.
We’ll also assume you agree to the way we use cookies and are ok with it as described in our Privacy policy, unless you choose to disable them altogether through your browser.
LuvitRED 2.16.0 has been released and is now available on CloudGate Universe.
Minimum firmware: 2.82.1
Highlights:
The minimum firmware has been bumped to 2.82.1 to fix a problem when using a flow downloaded from the CloudGate Universe. This problems was addressed in version 2.14.0 but also required a firmware update. It is strongly advised for anyone using version 2.14.0 or above to upgrade to this firmware or a more recent one.
Starting from 2.16.0 you can setup lorawan sensors with class C support. A class C sensor is always listening for messages from the server when not transmitting. This allows you to send messages to the sensor without the sensor having to initiate communication. The downside is the continuous power consumption. Most sensors using class C are therefore not battery powered. Broadcasting is not yet supported.
Up until now you could only connect a CloudGate device to Cumulocity. Now the CloudGate can act as an agent to create and remove other devices.
The ui input and select allow you to set a default value which would be updated when the value changed. The value would reset to its default when the cloudgate rebooted. Creating a flow to store this in flash and set it again on reboot was a cumbersome process. Now this can be done internally by the node simply by checking a box.
Modbus defines some exception code, e.g "Slave Device Busy". When an exception occurred and was sent to the extract node, it would think it was normal data and decode it incorrectly. The node now ignores this and optionally you can suppress the exceptions form being send as a message. These exceptions will still be thrown to the catch node.
Full Change-log:
2.16.0:
2.15.5:
2.15.4:
0 Votes
0 Comments