Cumulocity IoT Feedback Portal
ADD NEW FEEDBACK

All feedback

Showing 407

MQTT static template - Operation for clearing an alarm on the source device

Devices can raise alarms via SmartREST templates such as 301, 302, 303, 304 and 305. Devices can also clear alarms via SmartREST via the templates such as 306 and 307. However, there is no standard way to backpropagate the alarm status to the devi...
Guest 3 months ago in Cumulocity IoT Device Mgmt. & Connectivity 1

Password expiry warning

Problem Statement: At the moment user doesn't get any warning about their password expiry. If user didn't login for a while and password lifetime expired, then they only get to find it out at the time of login. This becomes a problem when user use...
Khademul Kabir almost 2 years ago in Cumulocity IoT Platform Services / Platform Management 1 Future consideration

Certificate refresh for connected devices

One method to authenticate devices to the platform is certificate-based authentication. But to enhance security, a growing number of standards and best practise guides are encouraging device manufacturers to issue certificates for their devices wi...
Neil C about 2 years ago in Cumulocity IoT Device Mgmt. & Connectivity 2 Planning / planned

Add the Ability to Clone a Tenant

Currently setting up a new tenant is a manual (and error prone) process e.g., users must be added, widgets added and customized, smart rules created, and device protocols configured. To quicken this process, it would be useful to be able to clone ...
Iain Mackenzie about 1 year ago in Cumulocity IoT Platform Services / Platform Management 3 Future consideration

Notification 2.0 API - Allow to subscribe to events from all devices

The Notification 2.0 API only allows to subscribe to events for a single device / managing object at a time. Subscription to all events (i.e. at the tenant level) is needed for the wm.io Cumulocity trigger
Frédéric Joulin over 2 years ago in Cumulocity IoT Platform Services / Data in Motion 0 Planning / planned

UPdate fields available for Azure SSO integration

When we configured Cumulocity to integrate SSO with azure, we needed to use the custom template to have OAUTH2 work. Specifically, we needed to add the scope field and set the scope to ${clientId}/.default
Dave Presuhn 3 months ago in Cumulocity IoT Platform Services 0

add a field "received_time" in measurements

I have a use case with logical devices that send batches of measurements. It happens that the data is completed or recomputed at ground side and measurements are sent again to Cumulocity. We experience problems when deleting existing measurements ...
Guest over 1 year ago in Cumulocity IoT Platform Services / Data at Rest 4 Future consideration

User Preference Settings: Timezone, Date Format, Number Formats, etc.

There are various users trying to access a single dashboard. Some might be operating from different time zones, and sometimes a single person is responsible for overseeing machines that have different time zones. Some users prefer to view the data...
Rahul Talreja 7 months ago in Cumulocity IoT Cockpit and WebSDK / Dashboarding 0

Notification API 2.0 - Allow to subscribe to measurements to all devices

We would like to subscribe to the measurements from all managed objects (devices) on the platform using the Notification API 2.0. Currently, a subscription must be created for each individual managed object.This makes it easier to subscribe to the...
Thomas Kühn about 2 years ago in Cumulocity IoT Platform Services 1 Unlikely to support

Digital Twin: Include last measurements and events in the managedObject of the device

To improve performance of dashboards, and to allow faster access to digital twin, it would be good, if for each measurement and event type, the last received object was also cached in the managedObject. In case new measurement/event of the same ty...
Peter Gaspar about 3 years ago in Cumulocity IoT Platform Services / Data at Rest 4 Planning / planned