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 'bug?'.

  • 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 4 results

  1. I was playing around with the LUA command I only recently noticed: fibaro:callGroupAction. Would be quite handy to e.g. turnon/turnoff all lights in a room with a single command. However, when I try to use it, it does not seem to work. See the script below: local data = { interfaces = { "light", }, properties = { dead = false, }, enabled = true, visible = true, roomID = 4, } ids = fibaro:getDevicesId(data) fibaro:debug("devices reported by fibaro:getDevicesId: "..json.encode(ids)) ids=fibaro:callGroupAction("turnOff",data) fibaro:debug("devices reported by fibaro:callGroupAction: "..json.encode(ids)) Running this scene provides the following output: [DEBUG] 23:47:48: devices reported by fibaro:getDevicesId: [90,92,94] [DEBUG] 23:47:49: devices reported by fibaro:callGroupAction: [3,4,5,6,7,8,9,10,11,12,13,18,19,20,21,22,23,24,25,26,27,35,36,37,38,39,40,41,42,43,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,83,84,85,86,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,107,108,109,110,111,112,113,114,115,116,117,118,119,121,122,123,141,142,143,146,147,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,168,171,172,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,223,229,230,231,232,233,234,235,236,237,238,239,242,246,247,248,249,250,251,252,253,257,258,259] It seems that the filter is not applied to the groupaction as it returns all my devices and switches off all the lights/devices in my house (instead of only the ones in room 4 as I defined in the filter <data>. Anything I missed/doing wrong, or is this a bug? I'm running 4.110. Thx, Rene.
  2. The icons have never worked for me since getting the HC3. We can actually upload our own now, but they dont actually do anything as you can see from the attached image. My uploaded icon shows as a box with a question mark. I have tried deleting it, restarting the HC3, re-adding it and still no joy. And even those that do seem to show in the web dashboard still show a question mark in the app on my phone.
  3. Hello! I know this has already been posted in another thread, and been there for three years, but since there see to be no official response or solutions available, I am posting another thread. I have ~ 10 Fibaro Wall Plugs at home, connected to a Home Center 3. Regularly these wall plugs just seem to go dead. (Basically they stop responding to any commands.) I just have one that has done this, and I am testing to disconnect and reconnect it. The ring glows green for a sec and then goes white (on), so it seems it's still connected to Home Center (?) That said, sending commands to it just doesn't work. It's not being reported as disconnected in Home Center? See movie attached how one is currently "dead" (Device 314 is the dead plug, while showing how 318 still works fine) Also, I tried a soft reconfiguration on the plug, which seems to work.. (See image showing part of trace log) the device does still not respond after reconfiguration.. It's worth mentioning I have had similar problems with Telldus-plugs. I decided to buy Fibaro ones to hopefully solve the issue (even though they are 2x as expensive), but I get similar problems with these ones.. it's very disappointing.. It's worth mentioning I have ~30 other ZWave Devices working in my home. Only these plugs keep stopping to work.. I don't understand what is the problem? If I completely reset the plug and remove it and re-connect it to Home Center I am rather sure it will instantly work (for a while).. I'll wait doing that til I have had some response here.. FibaroWallPlugDead.mp4
  4. Hello, Recently I bought a Homecenter Lite and I'm experimenting with scenes. Now I discovered something I believe is a bug in Fibaro scenes. Hope you can confirm or tell me what I'm doing wrong here. First, let me explain how I work: I have some lights outside which I want to switch on and off depending on the time of the day with different timestamps depending on the day of the week. Also I use a variable "daypart" (dagdeel in Dutch) which switches in scenes from morning to afternoon to evening depending on the time of the day. The variable "daypart" is set to night in the scene which switches of the lights late in the evening. Now in the morning, at exact time 07:00 I have a scene which checks if "daypart" is still night (it will switch in another scene to morning at sunrise) and if so it switches the lights outside to on. Now the problem, the last scene described should check if time is exact 07:00 and then check if daypart is still night. Only if that's the case it should switch on the lights. Now, what's really happening, when my scene which switches off the lights late in the evening and sets daypart to night (mostly around 23.30) the lights switch to on again after 4 seconds. The lights only stay off if I disable the scene which should only work at 07:00. Now, anyone knows what's going wrong here? I suppose the scene is triggered only by change of the variable instead of variable combined with exact time as stated in the scene. See also both scenes as sample
  • Create New...