Welcome to Smart Home Forum by FIBARO
Search the Community
Showing results for tags 'quickappchild device'.
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
When the success() function is executed after an http request, are there any constraints on what can be done within that function? I am not thinking about starting another http request, instead I wonder if I try to update my child devices as part of the function would be a problem. One thing that could happen (rarely, I hope, but still a possibility): if the child device had been deleted between iterations, my child device update procedure would create a new child device. So there is a minimal amount of overhead with simply updating the child device but probably twice as much overhead involved in the creation process. It strikes me that many of the examples of success() functions are short, sweet, and to the point. Currenty my development stores that data and deals with it on the next polling loop (about every ten seconds). But it also means that the device data is already ten seconds old when it gets updated. For my current devices the request/response time is short because it is on the same home network. I have another device I want to create that I am forced to go out to the cloud to control. That is not ideal but it is what it is. Thank you for any assistance. Peter