Cumulocity Edge should support devices communicating using the LwM2M protocol. This would allow deployments with devices that do not support C8y's REST/MQTT protocols and/or require a more lightweight transport protocol than HTTPS (i.e. COAPS). Th...
Bulk device registration – Support json & xml files
Currently, for LwM2M devices, bulk registration only supports csv files. It would be useful if other file types, in particular json & xml were supported as well. It would also be useful if these files supported the addition of custom device at...
Adding a static template for c8y_SendConfiguration operation
Hello, After resolving a problem on my side, I noticed that there isn't static template for c8y_SendConfiguration operation for text-base configuration. it is very strange/disturbing to not have a static template for that operation as: There is a ...
Our existing IoT gateway device uses Device Management to register with the C8y platform, which creates a device account containing the device credentials. Two of our use cases involve being able to restrict the device's access to the platform tem...
As a manufacturing company, we have PLCs with large set of variables all corresponding to a single machine. Creating devices with a large set of measurements/events/alarms is thus more than common. At the moment, the GUI of OPC UA is ok for adding...
Remote Access over HTTP to Device UI with Configuration
Some devices have a Configuration tool on the device side which could be accessed over cumulocity with the remote access Microservice. Remote Access does not support http (443) connect. Some of the device configuration are device specific and are ...
device-info page: 1000 events UI limitation should be removed
SAG R&D confirmed that in the current version the maximum of 1000 events are limited as per the UI. Having a hard limit on 1K means that often what is default view for the user will appear broken as not all events in the default timeframe can ...