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


Search the Community

Showing results for tags 'alexa'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

Categories

  • Scenes
  • Virtual Devices
  • Quick Apps
  • Icons

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Facebook


Google+


Skype


Website URL


WhatsApp


Country


Gateway/s


Interests

  1. Hey Is any one has solution for controlling QA with alexa voice command i build quick apps for my devices as binary switch so i can control them from alexa to turn on/off only but nothing else i want to be able to control and set all option and buttons i created in QA, I can't find any solutions
  2. Has anyone successfully sent commands to alexa? Basically i want fibaro to trigger a command to alexa to tell it to turn on/off my delta faucet. or has anyone directly integrated their delta faucet directly to fibaro?
  3. Version 1.0.0

    186 downloads

    Several icons to visualize the online status of devices alexa, pc, tablet, laptop, smartphone, tv
  4. Which Voice control should I go for? Amazon Alexa, Google Assistant or something else? I have a home based on z-wave+ components (see profile) controlled by HC2. Currently I have no voice control setup. If home control is the primary purpose, which one should I go for? And Why?
  5. Note. The first ~2000 posts of this thread is mainly about EventRunner3 that is for the HC2. EventRunner3 is not developed further, but bugs are fixed as they are reported. For HC3, the version is EventRunner4, and is a QuickApp,. Here is a post introducing EventRunner4. Most of the 'Event Script" syntax and commands are still valid and old posts can be of use for new HC3 owners. Here is an example of how to code in a "single instance / event" style. A style I'm using today for all of my scenes. The idea is that instead of having to deal with a new instance being spawned with every scene trigger, all triggers are dealt with from within a single scene instance that is continuously running. It becomes something close to a traditional event loop model found in most modern GUI frameworks. The advantages with coding scenes in this style are: Scene can keep state in local lua variables between scene invocations/triggers Easy to keep different rules/logic in the same scene without causing conflicts, e.g. combining continuous running loops/schedules with immediate reaction on incoming triggers Easy to distribute different rules/logic between different scenes and allow them to communicate Easy to schedule actions to do in the future - that can be easily cancelled if new information is gained. Because the scene is continuously running it doesn't matter if there is a heavy initialisation when the scene starts up (parsing HomeTables etc.) as it is only done once... The framework has extensive support to run and debug the scene offline on a PC/Mac to get things right before deploying the scene on the HC2 (uses HC2 emulator). Offline it is easy to simulate trigger/events to understand if the logic is correct, something that is not always easy to detect in a asynchronous environment. It has publish/subscribe mechanism allowing scenes to exchange events without having to know each other's names or IDs or rely on global variables. It has proven to be easy to integrate with external event/msg based systems like Node-red, where scenes can both send and receive events to node-red and thus extend functionality with Alexa, Google home, Hue etc etc. The framework is available in two version, a 'light' version and a full blow version with a lot of bells and whistles. The latter also supports writing rules in EventScript, a "simple", but very flexible and efficient approach to writing rules that need to trigger things at various times of the day, or trigger on sensors or switches changing states. The implementation of EventScript is built on-top of the single instance framework and the event model and would have been impossible to do in a traditional scene model. Ex of EventScript rules. --[[ %% properties 54 value 55 value 56 value 57 value 66 value 77 value 78 sceneActivation 88 ui.Slider1.value 88 ui.Label1.value %% events 100 CentralSceneEvent 120 AccessControlEvent %% globals Home %% autostart --]] myLightSensor1 = 54 -- do not declare local, script will not find them(!) myLightSensor2 = 55 myMotionSensor1 = 56 myMotionSensor2 = 57 myLight1 = 66 myLight2 = 67 myDoorSensor = 77 mySwitch = 78 myVD=88 myKeyFob = 100 myLock = 120 function main() -- Trigger rules Rule.eval("myLightSensor1:lux > 200 => myLight1:on") -- Turn on light1 if lux value goes above 200 Rule.eval("myLight1:isOn => myLight2:on") -- Turn on light2 if light1 is turned on Rule.eval("myDoorSensor:breached => myLight1:on") -- Turn on light1 if door sensor is breached Rule.eval("mySwitch:scene == S2.click => myLight1:on") -- Turn on light1 if S2 is clicked once Rule.eval("slider(myVD,'Slider1') == 50 => myLight1:on") -- Turn on light1 if slider is set to 50 Rule.eval("label(myVD,'Label1') == 'ON' => myLight1:on") -- Turn on light1 if label is set to 'ON' Rule.eval("myKeyFob:central.keyId==4 => myLight1:on") -- Turn on light1 if key 4 is pressed on keyFob Rule.eval("myLock:access.status=='Unlock' => log('Door unlocked by %s',myLock:access.name)") -- Door unlocked Rule.eval("$Home == 'AWAY' => myLight1:on") -- Turn on light1 if fibaro global variable 'Home' is set to 'AWAY' Rule.eval("#AccessControlEvent{data={name='$name',slotId='$slot',status='Unlock',id=myLock}} => log('Door unlocked by %s',name)") -- more rules -- Turn on lamp at 15min before sunset Rule.eval("@sunset-00:15 => myLight1:on") -- Turn on 2 lamps 15min past sunrise on weekdays Rule.eval("@sunrise+00:15 & wday('mon-fri') => {myLight1,myLight2}:on") -- Turn on lamp if sensor breached Rule.eval("myMotionSensor1:breached => myLight1:on") -- Turn off lamp if sensor safe for 5min Rule.eval("trueFor(00:05,myMotionSensor1:safe) => myLight1:off") -- Turn on lamp if doubleclick on switch S2 Rule.eval("mySwitch:scene==S2.double => myLight1:on") -- Toggle lamp if key '1' pressed on keyfob Rule.eval("myKeyfob:central.keyId=='1' => myLight1:toggle") -- Turn on lamp if average lux is less than 200 Rule.eval("sum({myLightSensor1,myLightSensor2}:lux)/2<200 => myLight1:on") -- Turn on lamp if any of motion sensor myMotionSensor1,myMotionSensor2 are breached Rule.eval("{myMotionSensor1,myMotionSensor2}:breached => lamp:on") -- ..and turn off lamp all motion sensors are safe for 10min Rule.eval("trueFor(00:10,{myMotionSensor1,myMotionSensor2}:safe) => lamp:off") -- Turn on lamp if any of motion sensor myMotionSensor1,myMotionSensor2 is breached -- but not if it's daytime, and only at dimmed level during night Rule.eval([[{myMotionSensor1,myMotionSensor2}:breached => || 24:00..sunrise >> myLight1:value=30 || sunset-00:30..24:00 >> myLight1:on ]]) end More on EventScript and the full blown version is available in the posts listed below: Here is a post on setting up the framework (works for EventRunnerLite too) Here is a post on the EventRunnerLite version - a bare bone version of the framework Here is a post on writing schedulers using EventScript. Here is a post on writing trigger rules using EventScript. Here is a post on EventScript syntax and rules (here is a new version under development) Here is a post on writing Lua event handlers Here is a post on debugging the framework Here is a post on the publish/subscribe mechanism Here is a post on enabling Hue support - mapping of Hue devices to standards z-wave/fibaro:* calls Here is a post on integrating the event model with Node-red - sending/receiving events from node-red, with extendable, example flow. Gives support for Sonos TTS and Alexa input...Updated flow <here>. (and here is another thread, 1,2,.) Here is a thread on the HC2 emulator used to debug EventRunner offline Here is a post on creating VDs from an ER scene and handle the VD logic with EventScript rules (and a calculator example) There will also be some services based on the EventFramework posted iOSLocator - a service that checks with iClod for people at places and sends events to other EventFramework services iCalendar - a service that fetches evens from Apple's iCloud calendar or Google calendar and post them to scenes. (latest iCalendar) Logger service - part of Supervisor Alarm service - TBD CronRunner - a UNIX like crontab service other scenes can register call-backs with Supervisor - A scene that pings EventRunner scenes and makes sure they stay alive. Best practices rules - TBD Implementation notes Notes on the basic EventRunner framework Notes on the EventScript implementation - TBD ChangeLog for the EventRunner framework. The lastest version of the code is kept in my GitHub. The background of this framework and a thread discussing it can be found here, however the code has evolved a bit from when originally posted there. If you are new to EventRunner I don't encourage you to read the posts in the thread chronological, as it contains a lot of outdated information. Instead, the best way to get an understanding of the capabilities of EventRunner is to browse the links in the list above.
  6. I have about 40 active devices, all of which were working last night. This morning one of them has disappeared from the Alexa app. It still appears in the Fibaro interface where it works perfectly. Running discovery on Alexa doesn’t find it again, and I’ve done the custom skill “list homecenter devices” thing too. How can I force Alexa to find it again? Any idea why it would have disappeared? Things I have tried: * soft reconfigure missing device * rename missing device * restore working back up on Fibaro * list homecenter devices before discovery In all cases Alexa finds no devices. so frustrating - why would one dimmer just disappear? thanks,
  7. Hi team, Amazon launched Alexa in India on Nov 2017 but still Fibaro skill is not yet available in Alexa India platform. If you buy Amazon Alexa from India and choose language as English(India) and then go to Skills section, you will not find Fibaro when you search for this skill. As a workaround, all Indian Fibaro users have to create and Amazon.com (not Amazon.in) account and then select English (US) as Language and after doing this, you can enable Fibaro skill but you will not be able to access other Indian skills. @Fibaro please enable English (IN) language in your skills. It is just 10 minutes job for your developers. Here are the steps: https://developer.amazon.com/blogs/alexa/post/f89ae457-9538-4b57-b3f6-dbef2f600412/how-to-update-your-skills-for-india India is big market for Fibaro and I wonder why @Fibaro doesnt have focus on delivering services in India. @Fibar Looking forward to your support.
  8. First- I couldnt find Fibaro in Alexa skills (In India). Neither i could find Google also. Is there any regional restrictions? I configured ha-bridge and it was configured and the webpage is opened : https://github.com/bwssytems/ha-bridge However i couldnt find any devices - neither z-wave or wifi equipments were not visible. Both Z-wave and Wifi network (+Alexa) is working . How can i trouble shoot. Is it because data/group.db is empty . Sorry for being dumb.
  9. Hi, tired of Fibaro's poor skill at Amazon Alexa (never connect, it's slow) and the HABridge (we must pray for Alexa to find the devices, it is very random, it works when it wants, it duplicates devices). For all that I decided to try and do tests with Node-RED. And now I can say that it is fantastic, there are no limits to create. If you are interested I leave more info. Now I can control the lights, turn on and off, change the intensity, change the color, execute scenes of Fibaro and many things, all without depending on the official skill or any third party Bridge. I used: * https://nodered.org (Installed in Raspberry) * https://www.amazon.com/Ben-Hardill-Node-RED/dp/B01N0D97FZ (Node-RED alexa skill) * https://alexa-node-red.bm.hardill.me.uk (You have to create user and then create all the devices and scenes) * "HomeTable" global variables in HC2
  10. Hi with the current alexa options most of us have been stuck with Turn on and Turn off This doesn't make sense for gates and garage doors and has other limits as well such as being able to say "Alexa I'm home" or "Alexa, Start my day" If you have the latest version of the ios or android app you'll see routines in the menu options IT IS NOT AN OPTION IN THE WEB SITE /BROWSER VERSION These are three of the routines I added Create A new routine gives the folowing The first part is what you say and the second option is what this voice command does There appears be be no limitation to what you can add to the first part In the Add Action , click Smart Home to see a list of your devices Select the device Choose 100% brightness (but maybe 1% will also work) (brightness appears for me as I use the HA Bridge and my devices are an Hue bridge Emulation Click Next and you're done I also added another action to get alexa to say something back besides the usual 'okay' and that's it !! It may take 30 second functional but it works a dream f(for me anyway) _af
  11. Hi - what is the most popular and reliable home automation bridge for connecting Amazon Echo and Google Home (at the same time) to Fibaro & Vera - in a residential setup... It should be easy and designed well for customer to integrate into their setup in a good way. regards , Sanjaya [email protected] (SBS Dimensions - India)
  12. Hi guys, I have used the Sonos VD before with the SONOS play:1 speakers and the Fibaro HC2, however I am planning to buy a Sonos One (with built-in Alexa), has anyone tried using the VD with this? Thanks, Prankit
  13. Hi, both me and my friend has a problem that Alexa don`t discover NEO plugs?
  14. Hello community, I’m trying to connect an echo dot to HC2. As the dot belongs to one of my kids I’d like to give him access to the devices in his room only. therefore i’ve setup a user with limited access to specific modules in HC2. How can I now add the limited user to the Alexa Skill? I have to use a Fibaro ID user in the skill. But there I only have the main admin connected to my hc2. It’s not possible to connect multiple Fibaro IDs with the same HC2. So is Alexa an all or nothing option only? br Kro
  15. Hi, I have amazon echo and Home Center Light ,when i add Fibaro skill to it and open my Fibaro ID, echo not discover any device from Fibaro. I tried to delete home center light and add it to Fibaro ID but still the same problem, I had open another account that has home center 2 , it works and devices discovered . What could be the problem ? and what should i do ? Thanks ...
  16. Witam. Czy w związku z aktualizacją w której FIBARO rezygnuje z LILI, można przyjąć że Alexa lub Asystent Google działają w języku polskim? I czy mógłby mi ktoś wytłumaczyć jak zintegrować Asystenta Google z Fibaro? Robiłem wg zaleceń...Zainstalowałem Google Home...Ale tam asystent nie reaguje... mam jeszcze aplikacje Google i tam asystent reaguje ale wyświetla mi linki do stron fibaro, ale nie "fibaro id".. Co robię źle?
  17. jarheg

    Alexa and HC2

    Hi i have problems with discovering scenes and devices. I have found my Sonos but no other devices. is there something i miss here?
  18. Hi, I have multiple devices hooked up to Alexa via the smart home skill. It seems Alexa now supports getting the status of a device: "Alexa, are Kitchen Lights on?" Is there a way to enable this for Fibaro devices as well? It would be extremely helpful to be able to ask Alexa for the device status. Right now we get a reply "Kitchen Lights does not support that" while other (non-Fibaro) Alexa integrated binary switches reply with the correct status.
  19. Scenes are avaible throught the smart home part, but not in routines? why?
  20. Is it possible to link multiple Alexa devices to 1 fibaro ID? For example I have 1 Alexa in every room in my house. Thank You!
  21. Hi I moved my Amazon hardware to Australia now that it is supported here. When I went to install the two Fibaro Skills it said that they are unavailable for Australia. That just doesn't make any sense unless I'm missing something. Fibaro, surely the skills should just be dependant on where Amazon decide to support Alexa products?
  22. I am really happy with Alexa's Fibaro skills. Unfortunately, there seems to be limitations to take advantage of LUA scenes and virtual devices. What would be your recommendation to have workaround for this? Should I forget Alexa's Fibaro skills and use Raspberry PI and HA Bridge instead or what? Does it matter what PI version to use? What would be the best tutorial to make it work? Thanks in advance for your support!
  23. Hello, I want to know that which Amazon echo device is fully compatible with fibaro? Which Version has to be selected and which model ? It is stable or not ? Does it work well or not ? Thankyou
  24. Fiabro Alexa has suddenly become a bit politer in my house. I am guessing a revamp of the server end. Not sure if there is a general improvement but certainly tries to be a bit more helpful. Keep it up @Fibaro
  25. Witam czy ktoś miał taki problem a mianowicie alexa niewykrywa urządzeń, obydwie umiejętności zainstalowane, hasło do id podane a mimo tego niewykrywa urządzeń co może być przyczyną ?
×
×
  • Create New...