Feature requests

Avatar
  • 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.
Avatar
Noel Fuentes

Hello,

Here is my suggestion:

+1 to enable/disable drivers (KNX, Modbus, etc.) on program tasks and themes.

New field on every node settings tab, called let's say "Visualization name", that bOS uses to display that node everywhere by default (theme, scenes, home assistants, etc.).

Imagine that we have our work done, with 35 scenes, 20 time schedules, home assitants configured, etc. and our client wants to change the name of 1 light. It would be nice to change it only in one place instead of doing it in each of 35 scenes, schedules, etc. I thing this feature would save a lot of time for us.

Another one: let end users create their own schedules and scenes with no need of using bOS config to do it.

Best regards

Avatar
ComfortClick Support

Hello Noel,

the driver enable/disable request has been quite frequent for a while now and internal tickets have been created. In many cases there is not a clear reason why certain communication breaks (like the classic: Did you try turning it off and on again? Which in many cases simply resolves the issue without additional headaches).

Note that this has been noted and put into pipeline, ETA on release it not known yet.

Same goes for the scene/schedule creating. We made some improvements in the latest versions, adding more options and even more options for scene/schedules are also planned.

Best regards.