Feature requests

Avatar
Jürgen Jürgenson
  • updated
  • Under review

I thought I'd create a new feature request thread that consolidates known feature requests into one topic. Please feel free to add your own requests here.

Here are some updates I've been waiting for:

  1. Improved search options - for user logs and general devices. Some logs have filter/search options, but most of them don't. If we need to debug user logs, it can be challenging to find specific entries, especially in a large apartment building with 180+ apartments.
  2. The ability to disable/enable drivers from themes/programs.
  3. The option to insert links into the bOS web browser/camera jpeg links directly from a program.
  4. The option to disable the bOS internal chat or limit chat access to admins only.
  5. The ability to export data to Excel, particularly metering values and other relevant information for building managers
  6. Better graphs for analog logs - zooming and pinpointing values. 

    Forum feature - make it so the user/topic creator is able to edit its posts - it lets you edit for only a short time period after posting.
Replies 22
Avatar
0
Arno Padar

It would be nice to modify values directly without opening multiple windows. For example, if we have \sensor1.value, and for another panel we need to use \sensor2.value. I understand that using the device tree ensures correct data without errors, but could it be validated if we change the values directly in the configurator field?

Avatar
0
Jürgen Jürgenson
Quote from Jürgen Jürgenson

Also alert messages inside bOS app should be in a separate window, so they wont cover(overlap) the full screen. For example if there is an error with push query - then its impossible to use the app if it only spams errors.  Sometimes the admin needs to turn off the unit that has errors but again its hard when the events are actively updating. 

Image 4681


Also in the events windows, would be nice if there was a button "acknowledge" or something - as every new device that logs into same account has to scroll thru all the events to clear the red mark(new events active). 

Mark events as read button is needed also for new device(mobile or tablet) installs. Right now I have two options. Scroll thru few years of events or delete them all. I don't want to delete them, but clients keep asking how to clear that red dot on the events.

Avatar
1
Jürgen Jürgenson
Quote from Arno Padar

It would be nice to modify values directly without opening multiple windows. For example, if we have \sensor1.value, and for another panel we need to use \sensor2.value. I understand that using the device tree ensures correct data without errors, but could it be validated if we change the values directly in the configurator field?

To add to this.
I would like to have Values and Function in the same window/tab:

Image 5159

So when we need to refresh values we dont need to click around between two tabs.

Avatar
0
Jürgen Jürgenson

Hey

Another wish of mine. For Modbus connections. Where one main line is used. Would be great if there was an enable/disable for current slave address connection, so if it has communication error I could just turn it off so it wont slow down the servers requests for the functioning units. Some commands may even go missing if the server is dealing with dead devices on the line.

Here I have 4 units that are either disconnected or having some other troubles. If I want to turn off the reading of registers I need to do it manually for every register. One button to disable it until its fixed would save some clicking.

Image 5290

Avatar
0
ComfortClick Support

Hello Jurgen,

thank you for your suggestion/wish!

It will be adde to our pipeline for future releases.

As a workaround, instead of disabling the reading, you could create a new modbus driver, use the same connection settings, cut/paste just the working slaves and leave the rest in the disabled modbus driver. You might have more nodes at the end, but you'd say a lot of time :)

Best regards

Avatar
0
Jürgen Jürgenson
Quote from ComfortClick Support

Hello Jurgen,

thank you for your suggestion/wish!

It will be adde to our pipeline for future releases.

As a workaround, instead of disabling the reading, you could create a new modbus driver, use the same connection settings, cut/paste just the working slaves and leave the rest in the disabled modbus driver. You might have more nodes at the end, but you'd say a lot of time :)

Best regards

This works if there are no logs I need to save. Cuting and pasting it will delete the logs. Or I have to save the logs separately.

Avatar
1
ComfortClick Support

Hello Jurgen,

indeed you're correct. For nodes with logs, this won't be an ideal workaround.

An internal ticket for slave disabling has been created.

Best regards.

Avatar
0
Jürgen Jürgenson

PATCH and DELETE for http node/driver is also needed. As I'm making different API alarm templates these are needed for modifying user/device groups.

Thanks :)

Avatar
1
ComfortClick Support

Hello Jurgen,

the additional commands are in development along side with Oauth as well. You can expect them in the future release.


Best regards.

Avatar
1
Daniel Lefterache

A node-red instance would be a great option. 


Customer support portal powered by UserEcho