All Activity

Witam, dziękuję za reakcję. Przeinstalowałem urządzenie i zaczęło reagować na przyciski. Musiał być problem na etapie konfiguracji.

I did iterate, but over the wrong resource🙃... fixed in v0.2.74

Masz włączoną ochronę lokalną co odłącza klawisze od wyjścia, wyłącz ją a klawisze będą sterowały wyjściami

Generalnie implant obsługuje klawisze mono i bistabilne do sterowania wyjściem ale dla eventów scen tylko monostabilne: Stan binary switcha powinien się zmienić dla obu typów klawiszy o ile nie jest aktywne local protection (odcięcie wejść od wyjść).

I looks like your are using the Classic app. The Classic app are currently being phased out and no longer works probably. Please start using the official Danalock app. You can find the app for app_store Danalock lifestyle. You will also always be able to run the calibration via click commands. You can find a guide on how to run a semi-automatic calibration with click commands . If you have the hold-back-latch feature enabled in the Danalock app you need to follow https://www.youtube.com/watch?v=uzzygexpcb8.

Witajcie, poddalem się. Stąd zwracam się do was o pomoc. Chciałem zbudować prosty układ. Za zwarciu masy (niebieski kabel) z żółtym - in1- powinna się wyzwalać scena. Natomiast nie ma żadnej reakcji po stronie SmartImplant kombinowałem z `wejściem 1 jako binarne i bistabilny. Nie działa. pytania: In1 ustawione jako Bistabilny: czy zwierając wspomniane przewody- powinien się zmieniać status binarny switch ? No i dlaczego temperatura wynosi grubo ponad 10 stopni od rzeczywistej ?

Hi Jan, Effects are now working as expected on single light, but still not working on grouped lights. Clicking on effect buttons does nothing. As I mentioned before, grouped lights does not support effects, so if button for effect is pressed on grouped lights QA then code must loop through lights that are members of the group and send to each individual light command for effect activation.

Hi @jgab, referring to my assistance requested, because of the problem attempt to index a nil value (global 'api')The problem was solved... ; just for your info.... i found the launch json as follows... { "version": "0.2.0", "configurations": [ { "name": "PLua: Current File", "type": "luaMobDebug", "request": "launch", "workingDirectory": "${workspaceFolder}", "sourceBasePath": "${workspaceFolder}", "listenPort": 8172, "stopOnEntry": false, "sourceEncoding": "UTF-8", "interpreter": "plua", "arguments": [ "${relativeFile}" ], "listenPublicly": true }, { "name": "PLua: Current File with Fibaro SDK", "type": "luaMobDebug", "request": "launch", "workingDirectory": "${workspaceFolder}", "sourceBasePath": "${workspaceFolder}", "listenPort": 8172, "stopOnEntry": false, "sourceEncoding": "UTF-8", "interpreter": "plua", "arguments": [ "--fibaro", "--run-for", "60", "${relativeFile}" ], "listenPublicly": true } ] } I donever open config files... ad I do not know when/why such modify occurred, however deleting that area, the system resumed normal working conditions... many thanks Ciao Giovanni

Dear Jan, great work on EventRunner7 🙏🙏🙏 , just started moving all my rules from 5 & 6 to a single instance on Eventrunner7... Looks like the nr.post() does not (yet) work in 7. rule("noderedURL='http://192.168.0.242:1880/endpoint/ER_HC3'") rule("nr.post(#echo1)") rule("nr.post_as(#echo2)") If it is not me doing something wrong, could you include when you roll out a new version? Thxs Jeroen

Setting the log level is slightly different: function QuickApp:onInit() LOG_LEVEL = ERROR self:debug("this debug should not be visible in console") self:error("this error should be visible in console") end

Yes, please continue the discussion in the plua forum thread. You are probably using the wrong vscode launch task. You need to use the "Plua: Current Fibaro File" when running/debuging. That will add the --fibaro flag that loads the fibaro libraries like api.* { "name": "Plua: Current Fibaro File", "type": "luaMobDebug", "request": "launch", "workingDirectory": "${workspaceFolder}", "sourceBasePath": "${workspaceFolder}", "listenPort": 8172, "stopOnEntry": false, "sourceEncoding": "UTF-8", "interpreter": "./run.sh", "arguments": [ "--fibaro", "--run-for", "0", "${relativeFile}" ], "listenPublicly": true }

Cześć, mam problem przy podłączeniu implanta do silnika Hormann SupraMatic4. Podłączyłem wg schematu z manuala, dodałem do HC3 --> sterowanie działa ale tylko przez aplikacje. Mam przycisk dzwonkowy, który również jest wpięty w implant ale niestety on nie działa. Zdjęcie jak wygląda podłączenie - kable złączone prowizorycznie to właśnie kable do przycisku dzwonkowego. W jaki sposób podłączyć to tak aby działało? Dodatkowo jak wpiąć w ten układ kontaktron ? Ponizej wklejam dodatkowo ustawienia ze Smarta:

Better place your post in the Plua tread:

Hello, I have managed to use an HC3 as main controller for an already installed KNX network. I was able to create a lot of quickapp to controll HVAC, A/C, lights, allarm, sensors and so on. My problem is that every quickapp on init create a listener, every listener even if not doing actions in that quickapp create logs for every knx telegram. So I have my HC3 logs/history that is full of KNXCallback logs instead of action logs. Is there a way to disable KNXCallback ? Thanks, Renato

Hi @jgab the system was working fine, suddenly today I've got this error , attempt to index a nil value (global 'api'). The *.lua is a very simple one to get informations from devices, but the problem is with any file/qa/scene using API... i tested already with " plua --diagnostic", no probelm access to hc3 and no warning provided... I tried to uninstall/reinstall PLUA, but no results.... maybe you have somesuggestion, Many thanks Best regrads Giovanni

Ok, fixed both in v0.2.71.

Yes during the night one out of 14 devices suddenly beeps about 5 times. No idea which one. (it stopped until I came close enough to listen which one it was). The might have a malfunction or do signal that something is wrong, but why not sending a message to the controller?

Hi Jan, I finally had a chance to test latest version 2.70 and it does look pretty god except that effects on grouped lights does not work. Note that effects can be activated only on single lights and so in case of a grouped light Yahue must loop through individual lights of the group and send effect command. On my HUE Festavia light effects are working, but need first to turn it on and then use effect button. If effect button is pressed while light is off then nothing happens.

I'm playing arround with MCP server and have it connected to my Hermes Agent now. I had to updated the server code with the updated sugested in the fix(mcp): echo client protocolVersion in handleInitialize (compat 2024-11-05+) PR on github to get it to work. I managed to get some devices turned off/on and it worked as expected. Next I tried to get my agent to find the device that has to highest energy consumption in the last month, and it failed with the following response I encountered an error when trying to fetch energy data for the last two weeks using mcp__hc3_smart_home__get_energy_data. The system returned a generic "HTTP 500: Internal Server Error", which means I could not retrieve the consumption metrics. The tool only supports fetching energy data based on predefined intervals (hour, day, week, month, year) but appears to be unavailable or restricted when trying to pull complex historical comparisons like a precise "last 2 weeks" analysis. Then i looked into the code behind and notice the following defenition for get_energy_data // Energy Management { name: 'get_energy_data', description: 'Get energy consumption data for devices or the entire system', inputSchema: { type: 'object', properties: { deviceId: { type: 'number', description: 'Optional: Specific device ID to get energy data for', }, interval: { type: 'string', description: 'Time interval (hour, day, week, month, year)', enum: ['hour', 'day', 'week', 'month', 'year'], }, }, }, }, And calling my HC3 API with this // Energy Management Methods private async getEnergyData(args: { deviceId?: number; interval?: string }): Promise<any> { if (args?.deviceId) { return await this.makeApiRequest(`/api/energy/${args.deviceId}`); } else { return await this.makeApiRequest('/api/energy'); } } When looked into the API Swagger there are no API responding to /api/energy/${args.deviceId} So my question is from which HC3 version is these defenitions constructed? Also looking at the energy.json, downloaded from API swagger, there is some detailed defintions for each enpoint/calls, and the one for the energy endpoint (/energy/consumption/device/{deviceId}/detail) looks like this "/energy/consumption/detail": { "get": { "tags": ["energy"], "summary": "Details of energy production/consumption", "operationId": "getConsumptionDetail", "parameters": [ { "name": "period", "in": "query", "description": "Array of time periods for which data is returned", "required": true, "style": "form", "explode": false, "schema": { "type": "array", "items": { "$ref": "#/components/schemas/DateTimeUnitDto" } } } ], I guees this would be the endpoint that comes closest to /api/energy/${args.deviceId}?

I have many recommendation for Mitsubishi Electric AC, so I decided to go with it. Is it possible to integrate it into the Yubii, like Daikin?

Hello, I have noticed many things regarding quick apps that might be improved in the new view for mobile app: Height of the buttons label text is reduced in one of the previous updates and now top of emojis is cut on both web GUI and Yubii app. While in web GUI label text of the button is properly shown: "🔊 Scene" with capital letter regardless of the emoji, Yubii app removes big letters of all words except of the first one if there is no emoji first: "🔊 scene ✔︎/✘". Another example, button label text in GUI "Get User Key" in Yubii app is shown as "Get user key". Can this "feature" be removed in future? If row with 3 buttons is added and then first and last buttons are hidden, then the middle button stretches over entire quick app and looks like one button is added instead that button keeps its size with empty space on both sides where hidden buttons are, just like it is shown in classic view. Same happens on both web GUI and Yubii app. Can this be corrected in the future? SWITCH type button looks same as just button, so what is the use of the SWITCH type button? I expected it to look like switch then with the label text on the left side? Text on labels is justified to the left on web GUI, but on Yubii app is centered. Why is that different? Can be unified? Drop down menu label text is capitalized on both web GUI and Yubii app, why? Why just not display user text as it is? Sliders have label text property, but unfortunately it is not available in the quick app builder and can be changed only from LUA code. Is there a plan to add this option to the builder? There is much more since there is plenty inconsistencies and differences that are confusing and annoying for all of users. It seems like this part was developed by several developers that didn't really communicate with each other when new view in mobile app option was in making, or it was rushed by managers that understand only numbers

If I remember well, any approved Smoke Alarm device must have a life time; usely 10 years.. Yours may have reached it and to inform user, start a siren?

@Support FIBARO take a look please. Seems like our function for limiting the logs does not work properly for limiting trace messeges.

I can confirm. It doesn't work for TRACE messages.

bonjour a tous! je suis a la recherche de l information suivante: peut t on integrer une camera TAPO C 200 C ? merci pour la reponse apportee