Skip to Main Content
Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 149

LWM2M custom decoder for a whole object

For some objects, it is more efficient for a device to report whole object in one message. Therefore it would be good to have a possibility to use custom decoder on the whole object and not resource by resource. Location updates already work this ...
Peter Gaspar over 4 years ago in Cumulocity IoT Device Mgmt. & Connectivity / LWM2M 1 Future consideration

I18N support for webApps and microservices

The C8Y platform itself supports I18N and also has APIs where user created content (webApps/microservices) add assets to C8Y. The webApps/microservices of course can provide I18N, but there is no support from C8Y. Especially, assets like roles/per...
Guest almost 5 years ago in Cumulocity IoT Platform Services / Product Infrastructure & Microservices 0 Future consideration

case-insensitive filtering in inventory

today, the devices from inventory can only be filtered by case sensitive queries for name or other fragment. Idea is to implement option to filter case-insensitevly. MongoDB provides enough expressions to be used to extend filtering options and st...
Peter Gaspar almost 5 years ago in Cumulocity IoT Platform Services / Data at Rest 3 Future consideration

Documentation "custom search" result links should jump directly to the found text

Example: On "https://cumulocity.com/guides/users-guide/getting-started/" add "add data subscription" (with quotation marks) in"custom search" field. Click the hit. The it brings you to the top of https://cumulocity.com/guides/users-guide/enterpris...
Guest almost 5 years ago in Cumulocity IoT 2 Future consideration

Reports on Timezone-settings instead of UTC

The reports are now scheduled on UTC instead of the timezone of the customer. This cannot be true for a Internet Service. If a customer out of the UTC-zone wants to schedule his reports he/she has to calculate on which time he has to set the sched...
Guest almost 5 years ago in Cumulocity IoT DataHub 1 Future consideration

Add smart rule for email on alarm SEVERITY

Most of our customers only want to be emailed for critical alarms. This is a challenging process with the current smart rules. We have to gather together all the potential critical alarms (we can have up to 1000 of these). Having smart rule which ...
Guest about 5 years ago in Cumulocity IoT Streaming Analytics (inc. Apama) / Smart rules 1 Future consideration

Better to display alarm text instead of alarm type in explorer window

Due to the number of alarms our system can create, the alarm type does not really reflect the actual alarm. For example, lots of engines use a CAN standard called J1939 which has a diagnostic message with thousands of alarms - we tend to give thes...
Guest about 5 years ago in Cumulocity IoT Cockpit and WebSDK 3 Future consideration

Additional aggregation intervals

When our customers analyse data via the data explorer, they are always complaining about the large jump in aggregation between 1 minute and 1 hour. Something like 5 or 10 minutes would be a good intermediate average for analysis
Guest about 5 years ago in Cumulocity IoT Platform Services / Runtime Services 1 Future consideration

HTTP requests that contain a batch of multiple requests, to remove round-trip latency issues

Currently, for nearly all operations (apart from create measurements) the only option is to perform a network roundtrip - send a request, wait for a response. While it's possible to do this over multiple connections concurrently, this is inefficie...
Guest about 5 years ago in Cumulocity IoT Platform Services / Runtime Services 2 Future consideration

Allow admin-usernames with more than 50 characters

Already analyzed: https://itrac.eur.ad.sag/browse/IOT-5966 --- When creating a tenant the "ADMINISTRATOR'S USERNAME" has to have <= 50 characters. This also counts for direct API call (property "adminName"). Idea is to remove this legacy v...
Guest about 5 years ago in Cumulocity IoT Platform Services / Platform Management 1 Future consideration