Jump to content

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!



Smart Home Forum by FIBARO Team

Search the Community

Showing results for tags 'ui'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • FIBARO Community
    • FIBARO Portal and Forum policy
    • FIBARO
    • Say hello!
    • Off-topics
  • FIBARO Update
    • FIBARO System Update
    • FIBARO Mobile Update
  • FIBARO Community Support
    • Scenes and Interface
    • FIBARO Products
    • FIBARO Mobile
    • FIBARO HomeKit
    • FIBARO Assistant Integrations
    • Other Devices / Third-party devices
    • Tutorials and Guides
    • Home Automation
    • Suggestions
  • FIBARO Społeczność
    • FIBARO
    • Przywitaj się!
    • Off-topic
  • FIBARO Aktualizacja
    • FIBARO System Aktualizacja
    • FIBARO Mobile Aktualizacja
  • FIBARO Wsparcie Społeczności
    • Sceny i Interfejs
    • FIBARO Urządzenia
    • FIBARO Mobilnie
    • FIBARO HomeKit
    • Integracja z Amazon Alexa i Google Home
    • Urządzenia Firm Trzecich
    • Poradniki
    • Automatyka Domowa
    • Sugestie


  • Scenes
  • Virtual Devices
  • Quick Apps
  • Icons

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL





Found 10 results

  1. I want to do some normal validation of the UI (normal for people other than Fibaro which doesn't seem to understand the finer things of the user interface concepts). My immediate desire is to take two values from the UI and pass them both to the API where they will be processed. The device is a thermostat and is using the com.fibaro.hvacSystemAuto device type. This presents the user a heating setpoint and a cooling setpoint when the thermostat is in Auto mode. But when the "Set" button is pressed, it sends the heat setpoint as an action, then it sends the cool setpoint. But the API expects both setpoints when the device is in Auto. Further, it burps if the heat setpoint is hotter than the cool setpoint. Even worse, the device control is in the cloud so the round trip is quite slow. It appears that the heat setpoint property I retrieve using fibaro.getValue(self.id, "heatingThermostatSetpoint") doesn't appear to be the value which was just sent (and passed to the cloud) during the heat setpoint onAction() method [remember, BOTH values are sent to the API on each call]. My original idea was to adjust the current setpoints so that the cooling setpoint was 2° higher than the heating setpoint when that setpoint is about to be set if they are not already in a valid state. Then, during the cooling setpoint adjustment, I would change the heating setpoint to be 2° cooler than the cooling setpoint if they are not already in a valid state. Of course an even better solution would be to be able to peek at the other setpoint in the UI and send it. And ideally, I would like to be able to keep the state of the two setpoints in a valid state at all times. The app used by the thermostat adjusts the heating down if the cooling setpoint is adjusted down too much or it adjusts the cooling up if the heating setpoint is adjusted up too much. So it would be good practice to do something similar in the Fibaro UI. 🙄 But that's not likely to happen anytime in my lifetime or my children's lifetimes either. The code I'm using is: elseif (self.properties.thermostatMode == "Auto") then self:debug('Original coolingThermostatSetpoint ' .. self.properties.coolingThermostatSetpoint) -- The coolingThermostatSetpoint must be greater than the heatingThermostatSetpoint. -- Since both the heating and cooling setpoints are updated individually but the -- API must be adjusted for both values at the same time, there are problems when -- the heating setpoint is hotter than the cooling setpoint. Solution (for now) is to -- adjust the coolingThermostatSetpoint to be 2° higher than the new heatingThermostatSetpoint. -- **Note: If the user has not set these two setpoints correctly, the actual heating and cooling -- setpoints will reflect a 2° difference from whichever setpoint has been called last. local coolValue = fibaro.getValue(self.id, 'coolingThermostatSetpoint') self:debug(string.format("getValue() returned %f", coolValue)) if coolValue <= roundedHeatValue then coolValue = roundedHeatValue + 2 end My first pass used the self.properties.coolingThermostatSetpoint value. Then I tried the call to fibaro.getValue() but that didn't seem to help either. The code to set the cooling setpoint is a duplicate of the above except the heating setpoint is adjust downward by 2 vs. the cooling setpoint being adjusted upward. So what am I doing wrong? Thanks in advance to any ideas or solutions. Peter PS: After working on this some more I FINALLY recognized this is a symptom of the async nature of web communication. Both setpoints are called back to back (duh). But the first call gets all the way to sending the API command out and then yields while that happens asynchronously. Then the other setpoint is changed and does the same thing. EXCEPT, the original heating setpoint has not been updated in the hub because that process is not executed until the success of the API call. I know how basic this is to people but I'm something of a dinosaur and cannot get it through my pea-sized, dinosaur brain that things have to happen asynchronously because of the latency of internet communications. Ok....now I'm back on board with all of this and I must find some elegant solution to resolve this. Forgive me for showing my ignorance but I learned a valuable lesson (again, but maybe it will stick this time).
  2. So I have been working on integrating my ceiling fan & light into my HC3 hub. I want to treat the fan control as a device and the light control as a device. But the problem is that I need buttons and sliders for user interaction. I get that the focus is primarily on z-wave integration but it is very shortsighted to imagine that everything the user installs in his/her Smart Home will be z-wave enabled. Furthermore, it seems that Fibaro does not have much market share in the United States. Consequently we are left in the dust having to integrate our devices ourselves. The Fibaro tech support seems very non-responsive to its community of owners and simply patches bugs without sharing new and updated features. For example, I noticed there is a new thermostat UI that appeared recently. Or at least I did not see it before a certain recent FW update. I presume it was made available because Fibaro needed it to sell their own thermostat device. Truly, I love my hub. The use of a web interface is far superior to using a smart phone app, IMHO. And, if I cannot easily find a z-wave enabled device, I can create or help someone else create a device handler for this device. I use and enjoy my Alexa but home automation is far more than telling Alexa to turn on my lights. And why should I rely on an internet device for more sophisticated control strategies? Right now my z-wave continues to operate even when my ISP goes offline. My ceiling fan will rely on my WiFi operating but it does not have to go to the cloud to be controlled. Only my Nest Thermostat will lose connection to my hub when my internet goes offline. When the time (and money) comes, I will replace it with something z-wave or maybe WiFi but not cloud controlled. I think the biggest takeaway from this rant is that there needs to be a means to create custom UIs for child devices. An added bonus would be a few different control objects. Things like a select box, a multi-select box, a check box (or something that looks like a pushbutton?), ways to group things (a container) or a means to draw a line between sections. Granted that images may be memory hogs so adding a bunch of icons or other small pictures would be memory intensive but small icons that could be added to a global list in the device might mitigate some of that. It seems that many of these structures are integral to the HTML world and a part of the web client. We just need a way to safely use them in the UI. Also, a comprehensive list of Lua methods that we can use along with simple descriptions of their use. Fibaro relies too heavily on its community so leverage that community to learn and share their knowledge on use. Fibaro need not shy away from providing this list because they don't want to write extensive descriptions of each and every method. Reward your faithful users with better tools to take advantage of your systems and you may be rewarded with an increase in sales. You could think of it as hiring a huge team of unpaid integrators who develop creative ways to solve problems. I was impressed with one user who described his sophisticated solution to control his home energy use based on the hourly electric rates that his utility company makes available each day. We don't have that need in North America (yet) but I am aware of a niche market that could be tapped for remote locations who exist off-grid and use solar energy exclusively. Thank you for your time in reading this. I feel better having expressed myself even though I figure this will be ignored or looked at as impractical. Have a great day (or night). Peter
  3. I am using a Z-Box hub which appears to be based on the HCL. Everything is Fibaro with the Z-Box brand. I presume it is based on HCL because it only supports 32-bit math. My FW is 5.141.59 beta. I have a fan/light device that I want to treat as two separate devices. All is well creating the child devices. The fan is a com.fibaro.binarySwitch device. I want to add six speed selector buttons, a direction toggle, a sleep timer value, and a "Wind" toggle (maybe with a max speed setting of some sort). The light is a com.fibaro.multilevelBinary device. I want to add a sleep timer value, and maybe a ramp speed for the dimmer ability. The sleep timers could be a slider value. I'm not sure which I prefer. Is there a way to add these elements to the UI screen for each child device? I have the six button layout defined on my parent app and I can see the view layout in the properties and the $json element added as an additional element to the view top level definition below the ts element. I'm wondering if "ts" means it's TypeScript that comes below the asset urls. I find it rather frustrating that so much is open to view but the means to implement a change is limited (or not documented). While I only have the single fan/light combo, I hope to add three more devices someday. Especially in the living room which has a vaulted ceiling and the fan is rather high. Besides, I hate pull cords and isn't that why I implemented my Smart Home? Thanks in advance. I'm really afraid of the answer I will get to this question. Peter
  4. Hi FIBARO community! I'am hoping someone can help me out with something. I wrote a little quick app with VD to set a global variable on UI. We use both Yubii app on our iPhones and the dashboard in browser on our MacBooks. So, I'd like, that my VD device looks like the "factory" design... For example: In app, in the ROOMS view the device's icon is on the left side, the name of device with less size font and the main value of this device is on the right side. Same than the "factory look" device, like on the 1st attached app pic, the "Hőmérséklet" device is a factory device (Fibaro Motion Sensor's temperature sensor), the "Célhőmérséklet" device is mine VD. Or in browser view on the tiles the device's icon is on the left upper corner, the name of device with less size font in center position and the main value of this device is in center position, with big blue font. Same than the "factory look" device, like on the 2nd attached dashboard pic in browser, the "Hőmérséklet" device is a factory device (Fibaro Motion Sensor's temperature sensor), the "Célhőmérséklet" device is mine VD. Is there any solution to make it, or it's remain a dream for me? Thanx: Laszlo
  5. matispf84

    UI Updates

    Hi guys, do you plan to migrate the UI of HC2 to something similar to HC3 soon?
  6. Hello, I try to build a VD and I have added a url on a label. It works very nice on web UI but on the android tablet I see the html code. I like to ask if there is a compatible way to work on web as also on android tablet app. To be more specific I like to open the coordinates of a user to google maps. Also I like to ask if there is a way fibaro to "understand" from client what type of device is. I like to build a scenario that if client is a tablet/mobile app or web browser. Thanks!
  7. What I want? I want to show and edit Global Varibles via my device (Iphone) on the Fibaro App. What have I done so far? 1 / I have made a global variabel called "Counter" in the panel section of HC2 2 / I have made som LUA code that can count fibaro:setGlobal("Counter", fibaro:getGlobalValue("Counter")+1) fibaro:debug(fibaro:getGlobalValue("Counter”)) So far it works - I can count! 3 / Now I want to show the variable in my interface device I have tried to make a Virtuel Device, but it seems like it is only possible 2 set a value through a slider or by programming a button. Not what I want. 4 / It seems to be a basic an very relevant think to enable edit and show variables in a user interface using HC2 and Iphone apps in Fibaro. I have search on different Fibaro Forums, looked after tutorials and asked Danish resellers, but found no help. Can anybody help me with a simple example? BR Uffe Rasmussen
  8. Hi, is there a way to have 2 buttons for VD's on the UI? Two buttons like a regular light (on/off). any suggestion are welcome
  9. Would love to add information like a status directly to the main screen of the user interface. Any pointers to get this implemented or is this area protected by Fibaro? Thanks, P.
  10. Hi , I was working with imperihome but found it a bit limiting. I don't have the skills to create a UI from scratch but came across OpenRemote. You run a controller on a NAS or a Pi (I'm using a Pi) and you create panels for tablets and phones using http/api calls to the HC2 I've figured out some of the building blocks and it's not that intuitive plus the site documentation isnt great and the forum appears small but with one or two very helpful members... This is what I have working with bi-directional control/response How to get a switch working (swiid and fibaro dual relay) How to get a slider working (fibaro dimmer) How to get a sonos zone controlled. from my initial testing the response is instant across a number of devices at the same time. I'm looking to create something similar to the attached image for myself... If people would be interested I'd be willing to document my few examples/settings/etc that would give people a good start - it should be just time and icons to scale to a few screens. ... just gauging interest levels before I put pen to paper ... -Frank
  • Create New...