Welcome to Smart Home Forum by FIBARO
Dear Guest,
as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.
As a member you can:
- Start new topics and reply to others
- Follow topics and users to get email updates
- Get your own profile page and make new friends
- Send personal messages
- ... and learn a lot about our system!
Regards,
Smart Home Forum by FIBARO Team
Search the Community
Showing results for tags 'feature request'.
Found 9 results
-
I would like to propose adding the feature userLabel to the Conditions / Triggers this way a user could find out what was the trigger event that triggered a scene where multiple conditions are present, simply: example: { conditions = { { isTrigger = true, operator = "match", property = "cron", type = "date", value = { "00", "22", "*", "*", "*", "*" }, userLabel = "time22" }, { isTrigger = true, operator = "match", property = "cron",
-
The title says it all. It would be nice if we could choose the color of the virtual device button so it is easier to the eye and change the color of the text inside. Thank you!
- 2 replies
-
- 2
-
-
- suggestion
- colored
- (and 3 more)
-
Hello, I have more than 6 thermostats in my house connected to fibaro (McoHome MH8) and i have changed all the icons of my devices but the only thing I cannot change are the thermostats icons. I do not see any reasons to not have that option as the icons do not change when there is a change in the thermostat. I think it would not be too hard to add the custom icons to thermostats too. Thank you!
-
Hello, more often I need at LUA Scenes filter devices by SectionID. At virtual devices it is not difficult, but at scenes is not comfortable to use REST API due asynchronous http get. Would be great to have LUA function get RoomsID by SectionID. fibaro:getRoomsIDBySectionID(sectionID) Then is possible filter devicesID by RoomsID. Thank you very much Martin
-
Hi, When editing a scene in lua the screen is very small. So I got this script to add a fullscreen button to make it easier to read en edit my lua, you paste the code in my Developer Console and hit enter. But of course after a refresh the button is gone. var sheet = document.styleSheets[0]; sheet.insertRule(".CodeMirror-fullscreen { position: fixed !important; top: 31px; left: 0; right: 0; bottom: 0; height: auto !important; z-index: 9; }", 1); CodeMirror.defineOption("fullScreen", false, function (cm, val, old) { if (old == CodeMirror.Init) old = false; if (!old == !
-
@Fibaro, It would be great if we were able to label each HC2 device in our HC List. Currently it can get confusing if you have many different HC units to choose from, see below: Unless you memorised the HC number or have a customised URL, how are we supposed to know which HC2 to connect to?
-
Hi, I'd like to request the ability to disable all scenes and virtual devices through a checkbox option. It could be added under the Configuration section and have a separate check box for scenes and vd's. I believe the capability exists already for scenes and for virtual devices it would be just a simple case of stopping the main loop code. It would essentially stop all the automation on the HCX device I had a mechanism to do this through a global variable but when I added this to all my scenes and vd main loop, it seemed to cause issues on s -
Hi Wondering why we don't have resizable txt boxes in the LUA scripting page ? It's not often I code in LUA in HC2, but when I do .. gee it's annoying Thanks, al.
-
Today the RGBW Controller has two options as it was before was power cut (memorized) or off. I would like to have another option "device turns on with status set in parameter XX". This would give the possibility of cutting the power to the LED Driver and upon power-on set a default value. Today: 16. Memorize device status at power cut. Device will be set to status memorized before power cut. Default setting: 1 0 - device does not memorize its status at the power cut. Load is disconnected. 1 - device memorizes its status at the power cut. Load will be set to the status from befo
