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!

 

Regards,

Smart Home Forum by FIBARO Team


All Activity

This stream auto-updates

  1. Today
  2. Yesterday
  3. Niedawno zmigrowałem z HC2 na HC3 i od tamtej pory mam same problemy... Praktycznie wszystkie urządzenia fibaro mają duże 2-3 sekundowe lagi. Prosta scena (gdy otworzę drzwi to zapal światło) powoduje, że to światło zapala się po około 2-3 sekundach. Też macie takie problemy?
  4. Hello, Is this a non working feature? I've a AEOTEC Gen 5 Meter - 3 Phase set up and I've selected it as my main energy meter but when I check my Yubii app all I can see is the sum of all of my devices power consumption. Is there any way of checking my Home Energy Consumption from within the App itself? Thanks.
  5. Hi...I have the temp set at 225 with a 3 negligible nourish rate. It remained at 225 for 35 mins at that point raised to 245 for 20 mins. Presently I’m sitting at 240 with a add up to cook time at 85 mins. The barbecue is in a area where the encompassing temp is 80. It’s 90 exterior of its location. At this point I don’t know what else to do with this barbecue. I will keep observing it for another couple of hours on the off chance that it rises over 250 at that point I will got to switch to ancient steadfast. As I’m out side it appear as in case the fan is making this peculiar commotion that it was not making when I to begin with got it.
  6. Hi TN92, An old post, i know.. But is it possible that You would share your QA for the Tasmota RF Bridge?
  7. i'm not using a gateway, using Apple Homekit (support my HomePod is the gateway). I found in the FIBARO for HomeKit Devices app I can turn off the tamper feature. But there is nothing in that app about turning off the acoustic alarm. I'd very much like to turn that off. If there is no way with the app perhaps there is an option with this button which is inside under the cover? Would prefer not to have to somehow break the speaker if I can avoid it.
  8. Hello, the e excluded and included several times and it still does not work, with the mobile it works perfectly, but in zwave I think it lacks some parameters, I leave a photo so you can see that for some reason I have blank fields and I think that would be the reason that it does not work in Fíbaro.
  9. No, that's line 55 inside the json library So it's probably a json encode/decode that blows up. Add this to the beginning of your QA code (top-level outside onInit()) do local encode,decode=json.encode,json.decode function json.decode(...) local stat,res = pcall(decode,...) if not stat then error(res,2) else return res end end function json.encode(...) local stat,res = pcall(encode,...) if not stat then error(res,2) else return res end end end and you will hopefully get an error that points out the right line in your code
  10. @Sankotronic I use only your module, not Fibaro sprinklers panel :). But what you wrote is also good. Actually I do no know why I did not think about it like you :). You are right that I can do it like you wrote. Good solution too. I just need to little change my habits I have from previous Toro Evolution controller. So thanks for you idea how to do that :).
  11. So, fibaro.call returns nada, that we know. A fibaro.call is translated to an api call that look like api.post("/devices/<deviceID>/action/<actionName>",{args={...},delay=<number>}) the updateProperty call could look like api.post("/devices/"..72.."/action/updateProperty",{args={'value',77.8},delay=0}) Most api calls (I haven't checked all) returns an error (HTTP 404) if the device doesn't exist. However, fibaro.call doesn't return that to us, it just silently ignores it without telling us. If we call an action in a QA that doesn't exist we don't get any message back either from the api.post - just a HTTP 202. We can go to the called QA and have a look and see that it will complain in the log that there is no handler for that action. But the caller gets nada. If we with this api try to update a non.existent (or read only) property we get also an HTTP 202 back ...However, 202 is kind of "non-committal"... 202 Accepted The HyperText Transfer Protocol (HTTP) 202 Accepted response status code indicates that the request has been accepted for processing, but the processing has not been completed; in fact, processing may not have started yet. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. 202 is non-committal, meaning that there is no way for the HTTP to later send an asynchronous response indicating the outcome of processing the request. It is intended for cases where another process or server handles the request, or for batch processing. It sums up pretty good Fibaro's relationship with it's users - non-committal ...so I guess by reading the fine-print we see that they get away with this behaviour... ...but they could at least throw us an error if we try to access non existent devices? If there is to be a market for QAs we can't put all the burden on the users of the QA. Calling the QA wrongly is just met by silence and in best case they have to go into the log of the QA to see if there were any errors - or into the swagger interface to see if it was updated?
  12. directly replacing the code with the above throws this as soon as I press button3_1 line 55 is -- If type is not defined, QuickAppChild will be used. self:initChildDevices({ ["com.fibaro.binarySwitch"] = MyBinarySwitch, ---- <------- }) /usr/share/lua/5.3/json/util.lua:55: bad argument #1 to 'for iterator' (table expected, got number)
  13. I see. That would explain things. Seems like I have still something to learn about Triggers 😉 for future work.
  14. Yes, that's a very reasonable expectation . Unfortunately Fibaro made it easy for themselves but difficult for developers. (long rant here)
  15. OK. In a normal programing environment you would expect an error message if you tried something that is not possible. 🙄 Thanks for the help anyway.
  16. Yes, but that's why it failed originally. json.encode("Pressed") is not equal to "Pressed". json.encode("Pressed") includes the "" , i.e. "\"Pressed\"". In your hex encoding you include the \" around "Pressed" so there the comparison works. But with @tinman's advice it should work and be more readable. However, the hex encoding is a start of encrypted scenes I guess
  17. @tinman, Thanks for the tip. Well I did not know I could use it I learned with json.encode() so I used what I knew how to work with.
  18. Hi @janikjan, You can just change start time of the automatic watering cycle with H+, H-, M+ and M- buttons and then save it with 💾 save button. VD will take care of everything else, recalculate and set new watering start times for all zones and then start watering at this new cycle start time. What I mean is that with this VD you do not need to go to HC2 Sprinklers panel anymore since all settings can be done from VD. I trust this can't be easier as it is
  19. Don't know what gateway you are on (please update your profile), but in the parameter 75 you can change the Visual and audible alarms duration: "The user can silence the Flood Sensor. Because the Sensor’s alarm may last for a long time, it’s possible to turn off visual and audible alarm signaling to save battery." In parameter 2 you can also change the Acoustic and visual signals On / Off in case of flooding. "The parameter allows for LED indicator and acoustic alarm deactivation in case of flooding detection."
  20. @Sankotronic thanks for nice module :). I have tested it for a few days and I pretty like that. You did a great job! Anyway I have one point how it should be improved, if it is possible :). Is it possible to add functionality when I am able to start my cycle at anytime I want? That functionality I had on my classic Toro Evolution unit. E.g. I set that for cycle one my zone 1 is on for 15 min, zone 2 for 20 min, zone 3 for 10 min and it is set to time 20:30. But sometimes I want to start that cycle on different time (when I know that we will have some party on garden at time when usually my spprinklers are irrigating garden). Then it will be nice if I can just set irrigation of that cycle manual anytime. Is that possible? Or if this is too much complicated, is it possible to adjust behaviour of your module (or add some settings) that when I manually start all my zones at once, that they will not start all at once, but one ofter one as it is when I use cycle. Thanks!
  21. Hello, I dont have that sensor but as far as I can see what you want you cant do. + - you can connect external power (NO bat operation) 1,2,3,4,5,6>>>>> wire to connect on wired system. Remark: I dont think its smart to change the suppliers devices. Succes //Sjakie
  22. why don't you remove all the json.encode and string manipulations? if sourceTrigger.property == "centralSceneEvent" then if sourceTrigger.value.keyAttribute == "Pressed" and sourceTrigger.value.keyId == 1 then -- do something elseif sourceTrigger.value.keyAttribute == "HeldDown" and sourceTrigger.value.keyId == 1 then -- do something elseif sourceTrigger.value.keyAttribute == "Released" and sourceTrigger.value.keyId == 1 then -- do something end elseif sourceTrigger.property == "execute" then -- scene manually started end
  23. Well, my thinking was that if it was a class method this would work Auth:login(function() self[self.model][object](self[self.model],boolean) end) - self[self.model] is an object. - self[self.model][object] is a method of that object Because it's a class method you need to send self (the object instance of RTV1905VW) as the first parameter and the self is self[self.model] More verbose: Auth:login(function() local obj = self[self.model] local method = obj[object] method(obj,boolean) end)
  24. Is your HC up-to-date ? I had the same, when i updated the system it was oke.
  25. Yep, these values are controlled by the meter - I would expect "sensors" to have read-only properties - what would it mean to change it? - you don't agree to the value the meter has measured? It's like trying to update the 'value' property on a door sensor to true - forcing it to report open even if it's not. What you can do is to create 3 Energy meter QAs that gets the values (and power) from the real devices. Then hide the real devices. The QAs properties you can set,
  1. Load more activity
×
×
  • Create New...