Feature requests

Jürgen Jürgenson

2 years ago
updated 2 weeks ago
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:

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.
The ability to disable/enable drivers from themes/programs.
The option to insert links into the bOS web browser/camera jpeg links directly from a program.
The option to disable the bOS internal chat or limit chat access to admins only.
The ability to export data to Excel, particularly metering values and other relevant information for building managers
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

Newest first
Newest first Oldest first

ComfortClick Support

2 weeks ago

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.

Reply Link

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

Daniel Lefterache

4 months ago

A node-red instance would be a great option.

5 months ago

Hello Jurgen,

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

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 :)

7 months ago

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

An internal ticket for slave disabling has been created.

Quote from ComfortClick Support

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 :)

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.

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.

11 months ago

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:

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