All Activity

solved today

Firstly, try refreshing the Alexa app to see if the new scenarios appear. Sometimes, it can take a bit of time for changes to sync across different platforms. If that doesn't work, you might need to manually re-enable the Yubii Alexa Skill or unlink and relink your Yubii account with Alexa. This can sometimes kickstart the syncing process and ensure that all your scenarios are up to date in the Alexa app. If you've tried all of the above and the issue persists, it could be a compatibility or integration problem between Yubii and Alexa. In that case, reaching out to Yubii's customer support team for assistance would be a good next step. They might have specific troubleshooting steps or be able to provide further guidance based on your setup.

Thanks @Neo Andersson for this solution. I really appreciate the time you take for me. Sorry for my bad English, i am French

Hello, looks like an issue in the system. We will check it out.

If you want to send live data to that screen, so it is updated every time the temperature sensor changes its values you need to listen for that event. You can do it by a simple loop, or if you are more advanced you can use refreshStateSubscriber or other tools, like fibaroExtra or ER5, that have built in methods for event listening. As you say you are a newcomer, i propose to use a simple loop. First wrap your HTTP call that sends the text to the screen into a function , than create a loop that listens to temperature changes. When termperature changes, call the HTTP function with an argument of the temperature coming from the sensor. --create a globaly accesible value to avoid http calls when sensor value is the same oldValue = hub.getValue(81,"value") function httpToScreen(sensValue) net.HTTPClient():request("http://192.168.1.221/api/notify", { options = { method = 'POST', timeout = 5000, headers= {['Content-Type'] = 'application/json'}, data = '{"text": "Temp ext:"..sensValue,"textCase": 0,"topText": false,"textOffset": 0,"center": false,"color": "#FF0000","background": "#FFFFFF","rainbow": false,"duration": 5}' }, success = function(response) hub.debug ("Scene1", response.status .. " " .. response.data) end, error = function(message) hub.debug("Scene1", "HTTPClient error: " .. message) end }) end function listenToSensor() local function loop() local newValue = hub.getValue(81,"value") --check if value is changed if oldValue~= newValue then httpToScreen(newValue) end end --change 1000 to whatever intervall you want to listen to the sensor hub.setTimeout(1000, function() loop() end) end --now just call the listener wherever you want to start listening listenToSensor() I have never tested it, but should work.

Hi All! Today installed 3 pcs Roller Shutter 4 into a HC3L system. The module is good, the installation went perfect with the new push-in connectors. BUT! The module parameters show all of two buttons send the 1x,2x,3x press and the hold and release scenes to the scene controller. When I try to create a block scene I can select 3 (!!!) buttons of the scene controller and every buttons have only the 1x press, held, release events which I can select from the list. What is wrong? I updated the latest firmware of the modules (8.1) and the latest firmware of the HC3L. I use the Zwave Engine 2. Has anyone same issue with this module? Thank you!

You should not treat the sliders as "variables" you can read. Instead every time the slider change, update a table with the slider=value that you then store away (in a quickVar or GV) Then you can at any time read the table for the latest values. At startup you initialise the sliders and table to your start values.

When it came to choose the engine, you have to read few words about two engines and make a choice (no revert, visible only once). Text is very confusing for someone "green". Something like this: when you choose z2 please be informed that's obsolete and receive no support (sic!). I don't remember exactly the text about z3, but my choice to z3 was made after reading those short info. I also know what's beta, but z3 was "less terrifying" in this short description.

Thanks, i know the term and meaning of BETA. I was asking about others experiences. I have some customers that are opened to take the risk, but i wanted to know the depth of the risk we are going to take. From these answers it is clear to me to not go for it. Thanks for the help

Hi, how did you manage to add the "thermostatFanMode" interface? And did you find some documentation regarding the available interfaces? 🙏

What is beta version? Google: beta version (plural beta versions) (computing) An early version of a program or application that contains most of the major features, but is not yet complete. Sometimes these versions are released only to a select group of people, or to the general public, for testing and feedback. I think it is not advisable to install anything marked as beta to clients except if they are aware of possible failures and agree to be test subjects. Same goes for HC3 zigbee. As long it is in beta, users can test it, but not expect that will work reliably since as above description says it is not yet complete.

Hello, In a Quick App UI, using several Slider Bars, I need to obtain the values of all Slider Bars to process the information, but I am not able to do so if it is not done one by one, through the onChanged event. Would there be any way to access the values of the slider bars? I've done a lot of research on the forum, I've done a lot of tests, but at best I managed not to generate an error and return an empty result 😁

podbijam temat? ktoś coś? Żeby roomby nie było w fibaro? eeee

Yes, I have an extensive experience. And it's very poor experience. Being completely new to Fibaro and have no help from others I turn Zwave 3 when configuring the central. First disturbing thing is problem with adding devices, mainly battery. It's worse when you turn on the encryption: you can try ten times with no result. Other device - it will succeed at first time. But this is not the worst. Soon appears the problems with communication device-central. The problem increases with number of devices with no particular repeating pattern. This winter when it was -15 C here, the heating based on nine Fibaro Heat Controllers completely stop working. HC does not react to command sent from central, smart implant turn on and off the gas oven with no reason, horror. All (almost all) problems void when I go back to older zwave. This forces me to set up ~60 devices from scratch. Do not do it to yourself. Zv 3 must be early beta.

Hi, I am totaly newby. I am trying to send some data to an external led screen. I have make this script to send a simple text and it works: net.HTTPClient():request("http://192.168.1.221/api/notify", { options = { method = 'POST', timeout = 5000, headers= {['Content-Type'] = 'application/json'}, data = '{"text": "Temp ext: XXX","textCase": 0,"topText": false,"textOffset": 0,"center": false,"color": "#FF0000","background": "#FFFFFF","rainbow": false,"duration": 5}' }, success = function(response) hub.debug ("Scene1", response.status .. " " .. response.data) end, error = function(message) hub.debug("Scene1", "HTTPClient error: " .. message) end }) Now, I want to send the Temperature value that I receive from OpenWeather in my HC3, instead of "Temp ext: XXX" in my previous exemple to "Temp ext: 8,24°C" 8,24°C is the value from the data that I have in HC3 device 81): { "id": 81, "name": "Temperature", "roomID": 220, "view": [ { "assetsPath": "dynamic-plugins/com.fibaro.multilevelSensor", "name": "com.fibaro.multilevelSensor", "translatesPath": "/assets/i18n", "type": "ts" } ], "type": "com.fibaro.temperatureSensor", "baseType": "com.fibaro.multilevelSensor", "enabled": true, "visible": true, "isPlugin": true, "parentId": 80, "viewXml": false, "hasUIView": false, "configXml": false, "interfaces": [ "quickAppChild" ], "properties": { "categories": [ "climate" ], "dead": false, "deadReason": "", "deviceControlType": 1, "deviceIcon": 317, "deviceRole": "TemperatureSensor", "icon": { }, "lastChanged": 1713810871, "log": "", "logTemp": "", "manufacturer": "OpenWeather", "model": "Temperature sensor", "offset": 0, "quickAppVariables": [ { "name": "name", "value": "openweather-temperature" } ], "saveLogs": true, "showFireAlarm": true, "showFreezeAlarm": false, "supportedDeviceRoles": [ "Other", "TemperatureSensor", "DeviceTemperature" ], "unit": "C", "useEmbeddedView": true, "userDescription": "", "value": 8.24 }, "actions": { }, "created": 1713648871, "modified": 1713810930, "sortOrder": 59 } I just have now idea how to do that. Thanks for your help

I think you need a kWh meter to measure that. Unless all of your appliances measure consumption.

You can only see if you are consuming from the network or exporting to the network, but in no case know the consumption of your home (lighting, appliances...etc) in general.

Hello guys I want to try Zwave engine 3 in one of my instalations. I know, it is in beta, but maybe some of you have more experiences with it. The system will have Heltun wall switches, Fibaro RGBW moduls, Heltun thermostats and Aeotec 7 motions sensors. Does anyone tried these devices with engine 3? Shall we try, or is it still unreliable? Thanks in advance

Inspire by above I made small test: local xx = 0 function QuickApp:onInit() self.xx = 0 local starttime = os.clock() for i = 1, 30000000 do xx = xx + 1 end local endtime = os.clock() print("Local var access:", endtime-starttime) starttime = os.clock() for i = 1, 30000000 do self.xx = self.xx + 1 end endtime = os.clock() print("Access via self:", endtime-starttime) end And the results (on the HC3): [22.04.2024] [14:46:15] [DEBUG] [QUICKAPP443]: Local var access: 4.119311 [22.04.2024] [14:47:15] [DEBUG] [QUICKAPP443]: Access via self: 59.719072 14x slower. Worth remembered. Tested the same with VSC and emulator on 9 years old mac gives result of ~15 sec, similar for both type of variables.

At what situation Aerotec should play a sound? When someone touch the ring on Doorbird (I hope so)? If correct, I think you do not need https call to activate. Instead you have to define an event called DBManualEvent and use it as a trigger to start any scene you wish (to use in in quickapps require little bit more knowledge). Events are defined via the webpage UI: configuration/general/events (I guess the names, my interface is in polish).

ow, fast like a rocket again

I remember when I switched to a new budgeting app, and I couldn't find where they hid my spending breakdown. It was frustrating! But after a bit of poking around and maybe a few colorful words, I finally found it tucked away in a menu I hadn't explored yet. Maybe there's a similar hidden gem in the Yubii app? Have you tried checking different tabs or digging into the settings? Sometimes, it's just a matter of playing detective until you uncover what you're looking for. Oh, and speaking of uncovering hidden gems, I recently stumbled upon this article on Smarter Business that had some neat tips for optimizing energy usage in smart homes.

I don't quit understand your question, but I don't use the Solax Inverter myself, so I don't have any reference. Maybe other Solax users can give an answer?

I have a paired a Aeotec siren 6 in HC2. I now have a couple of generic Z-wave device boxes representing different sounds, which I can play in the HC2. I want my Doorbird intercom to make a remote http call to this url to play a scene that will play a sound (when doorbell is pressed) in this format http://user:password@ipaddresshc2/api/scenes/48/execute I have made the user in hc2 for the doorbird to login with, but don't know what trigger to start the scene with in order to make the choosen sound play please help

One more remark: when importing a "switch" item of UI, the result in VSC seems to be wrong. One of the switches import like that ("button" part is OK): --%%u={{button="readNowButton",text="Wymuś odczytanie",onReleased="readNowButtonPressed"},{text="Tabela odczytów",value="false",switch="dataBase"}} and switch part should be: switch="dataBase", text="Tabela odczytów", onReleased="PrintDataEnable"