Product Feedback

Since Akenza is a critical part of our data pipeline, the ability to enable 2FA in a workspace would improve security.

When I am creating a virtual device to summarize data from other device, I want also to see in the device if this device is already used in rules as an output device. Currently, only rules are listed in the Device Details which this device is used as an Input. It would also be helpful if the device would be marked if it is an input or an output device.

If you have identical devices, being able to have one dashboard where you can "flip" between devices would be very nice. For example, if you have 50+ air quality sensors (all the same) to be able to have only one dashboard, not 50+ dashboards, as the information is all the same, only need to update the values according to the chosen device.

In case of an outage of outbound rules provider (like sms/e-mail) many retries should be performed by default, so the relevant events don't get lost.

This device is unfortunately not in your list of known devices. :-( Would you possibly consider to add this device? See: https://www.seeedstudio.com/Wio-Tracker-1110-Dev-Board-p-5799.html

It would be great to inlcude a Life Cycle Support input inside a rule, where I can use for example the offline state to trigger an action.

It would be very helpful if users with workspace admin(and or editor) rights could access the custom logic blocks, add new ones and edit existing ones (at least ones used in their workspace)

In certain situations, a QR Code can serve as a virtual device, eliminating the need for a physical one on-site. This is particularly useful for events activated by customers (ex. Aktenvernichter, Toiletten, Meetingrooms, etc.) As a result, it would be advantageous to develop a virtual device represented by a QR Code. This device would function similarly to a button and could be administered as a standard device.

User and Access Management should include: 1.) Dashboard-Exclusive Access where users can view dashboards without the ability to switch to the core system. 2.) Selective Dashboard Access where users are assigned to one or several specific dashboards, preventing them from viewing other dashboards (limited to a single dashboard view).

Similar to the grouping (or categorisation) functionality in the Dashboard, a corresponding grouping feature should be implemented for Rules and Device Types to enhance organization and management.