Welcome to Smart Home Forum by FIBARO
Search the Community
Showing results for tags 'skill'.
Hi, I have multiple HomeCenters (2x HC3 and one HC2) in 3 different homes. Two of these homes are mine, but are in different geographical locations. I've created two seperate amazon accounts, both of which use alexa. The problem I'm facing is that when setting up the Yubii integration on Alexa, I don't have the opportunity to chose which HomeCenter I wish to use. This results in the devices of my main home being all added to my 2nd home (as these devices were previously added to the Alexa over there) and no way at all to ad the new HC3 and al of it's connected devices. This is particularly annoying as Fibaro (or Yubii now, idk) give you acces to multiple HomeCenters from home.fibaro.com/... . But I have no way to select any of these devices when setting up alexa with Yubii. Is there any way to specify WHICH home center to use when connecting Yubii to Alexa with the skill? Thanks for any help.
Hi, I have 142 HCL's in my project and 142 Echo dots 3, with 16 devices and 59 scenes. Some I managed to find all devices and scenes perfectly, but I'm having trouble in the vast majority. The HCL that worked is exactly the same as the HCL that doesn't work, I've seen that this is an old and recurring problem, my project can stop due to this. Has anyone managed to resolve this? Thanks
Between the years I had some few seconds to learn about NodeJS, Alexa Skills and Fibaro API. I was able to create a Skill for Alexa to communicate with Fibaro HC2 (HCL should work also). For now it is written and configured for German language but can easily adopted to any other language. Disadvantages so far: The Fibaro Box must be available via internet by any port forwarded to HTTP port 80 only (unless you are creating a proxy in between). Dyndns and IPv4 are useful... The skill cannot get certificated and set up easily. For using it an Alexa Skill must be created manually and the code and all other options (like intents list, custom slots and utterances) must be pasted manually. Some smaller changes in the code is needed too (abbreviations, url, port, authentication). Also Alexa is responding only after asking for the keyword (like fibaro, house ore something like this). While using the Alexa Smart Home Skill it is not possible to have more usage than other already existing skills (like HABridge). Advantages/Possibilities (just some examples): - You are able to set temperature for a special period of time - You can get and set status of global variables - You can change up to two lights at once or all lights in one or two rooms at once - You can call scenes - You can get status information about open/closed doors, open/closed windows, bot at once, turned on lights - Status information about wall plugs (turned on or off and power consumption) - Change roller shutters status (with proper words like shut down instead of shut off). If anybody might be interested he can ask me for the code. I am going to publish it somewhere (maybe Github) in the next days if anybody else might get interested in this. Also code is still not perfect. There might be a couple of bugs and it might get written better. But it was my first time I was writing anything for Alexa and with Nodejs (don't know why I have chosen this language). Also I would like to know some more ideas what could be done additional. Also I am interested if anybody has some improvements (like communicating via home.fibaro.com).