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


olekenneth

Member
  • Posts

    47
  • Joined

  • Last visited

2 Followers

About olekenneth

Profile information

  • Gender
    Male
  • Country
    Norway
  • Gateway/s
    Home Center 3

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

olekenneth's Achievements

Learner

Learner (2/8)

7

Reputation

  1. Hi. I'm about to start getting Doorbird set up with HC3. The video setup as IP cam is fine. How far did you get with button press and door relay triggering?
  2. I reopen this thread. By now, I think we know that QuickApps are a real new powerful feature. Ref @Krikroff Sonos QuickApp. So, user plugins are here, in the form of QuickApps. What we still miss are user created templates to fully support z-wave devices that Fibaro themselves never will get around to support. Fibaro only really care about templates for their own Z-wave devices, which is of course somewhat understandable, but for the HC2 /HC3 users, doesn't help much. We need real templates for non-Fibaro Z-wave devices, created by users / developers / other Z-wave manufacturers. Hey, Fibaro, why don't you just make a Template creation tool?
  3. The Zigbee part is not worth waiting for. Zigbee vs Z-wave is a long discussion, but by including a Hue Bridge you get Zigbee if you absolutely want to. I've now returned to HC3 after some years on another system. As you, I was tired of slow and sometimes unreliable Z-wave response, something I did not experience on my old HC2 that died some years ago. My impression of the new HC3 so far. Impressive. Some limitations, but still. And the new approach to API / IP devices through QuickApps is very promising. Good luck with your home automation.
  4. I'm really glad to hear that! Thanks @Krikroff!! So, there's a great potential for HC3 becoming a much better platform than HC2 ever was, simply because of QuickApps integration with other devices. So, I'll try to contribute as well. Must try to get a group together to develop QA for the best door lock, IDLock. ? Optimistic then. Ole Kenneth
  5. Well, yes and no... So, in your opinion, QuickApps will not bring better integration with non-Z-wave devices? Unless each user makes it himself? If that's the case, I feel so sorry for Fibaro and the whole user community. Fibaro's integration with other devices sucks. Wake up and smell the roses! Go check the App store on homey.app for an Idea of what the Fibaro universe is missing. I was hoping that QuickApps would start to show up, providing drivers/plugins/apps for numerous smart devices. Not developed by Fibaro, but by advanced users/developers. I can certainly wrap my head around simple LUA scripting, but I nor most of us can make a proper Sonos integration. Just ask Krikroff how difficult it is... Instead of searching obscure french forum threads for tips and tricks on how to script things together, I would like to go to the Fibaro marketplace and browse through ready made plugins/QuickApps that actually work. If Fibaro is solely for the enthusiastic LUA scripting nerds, then we can just wrap it up and call it a day. I think Fibaro is hoping for exactly this development. I can't see how they can survive long without a steady stream of properly made plugins/drivers for other products. I don't mind paying for apps, in exactly the same way I happily pay for useful Mobile apps in App Store / Google Play. But of course, every end user don't make them all by themselves. I'm cheering on Fibaro. But I won't be so forever unless HC3 becomes a real smart home platform. 10 years ago Z-wave was a good shot at home automation. Today it's only a small fraction. HC3 must bring in the rest. If not through QuickApps, how?? Ole Kenneth
  6. Hi there! I'm just returning to Fibaro now, with the HC3 up and running for a few days. I used HC2 from 2012 to 2018 when it died. Using Homey since that. Now, I'm curious about HC3 and the new possibilities with QuickApps. No doubt, Fibaro HC is the best for controlling my 60+ mostly Fibaro z-wave devices. But in the past, integration with SONOS, HUE, Alarm systems, Door locks, Video door bells etc was poor. That integration is better elsewhere. Now, with QuickApps, can we expect to see better "plugins" for these kind of IP/API devices? I.e. better than the rudimentary version 1.0 plugins of the past, that's never maintained? I'd love to hear that smart speakers, be it Sonos or Google Home or Alexa, could fully intregrate audio output from my smart home system. Both TTS announcements and sound output from scenes. In a simple and usable way. (I know this has somewhat been possible for years through special VDs with much hassle, but I was never able to make it work properly.) Same goes for Hue, sensors and actors. Or IKEA smart products like blinds. And connecting Alarm systems with 2-way communication for sensor status etc. And a QuickApp for my ventilation system. What do you think? Am I too optimistic?? Regards, Ole Kenneth
  7. Hi! I am in a very similar situation. I've also located the RGBW controller close to the 24V LED transformer, but far from the regular switch. I have a dimmer with an unused S2 input, so I plan to associate the S2 to the RGBW module. Now, my problem is that it doesn't work! If I associate to another dimmer it works fine, but if I associate to the RGBW module nothing happens. I've tried to check if the problem has to do with multi-channel associations, but the RGBW manual does not list its multichannels... I'm not trying to control other units from the RGBW, but to control each channel of the RGBW from other units' S2 through associations. Any ideas anyone?
  8. Yes, indeed! But how to integrate this into HC2 is beyond my abilities... Anyone? Check it out here: https://github.com/mariusmotea/diyHue#diyhue
  9. Could someone please explain (briefly) the benefits / reasons for running an extra Sonos API from a Raspberry Pi? What exactly do you get from all the hassle?
  10. Oh, I didn't see that. That's a pity. We'll have to see then, when or if this will be a reality...
  11. Great job, @Sankotronic ! Just slightly off topic.... Did you know that IKEA has released a smart light system, also based upon ZigBee Light Link. Check out: http://www.ikea.com/gb/en/products/lighting/smart-lighting/ According to IKEA, it should adhere to open Zigbee standards and be compatible... http://www.ikea.com/gb/en/customer-service/smart-lighting-support/faq-smart-lighting/ It's really a lot cheaper than Phillips Hue. And knowing IKEA, they will expand the range and cut prices... I wonder if you or someone is able to make a plugin or VD for IKEAs Zigbee hub, so that it can be included in the Fibaro system? That would be a big step forward for whole-house total light control on a budget! Probably I should make an award of €100 for the first successful integration into Fibaro.... Cheers, Ole Kenneth
  12. Thanks a lot! Now, via the DoorBird app I can have video with 2-way audio, and then the "open door" button in the app sends an API call to run a scene in HC2 that can unlock the door. Video with 2-way audio is not possible through HC2 Video gate function, so that will be via the separate DoorBird app, but I can live with that. However, the Video gate function in HC2 works via DoorBirds camera, but I cannot have audio. So, this is as good as it gets for now. It works! I would appreciate though, if someone could enlighten me on the security issues mentioned in my previous post....
  13. Maybe I don't get this right.... I added DoorBird as a generic camera "other model" (not based on any specific model). On the General settings page: I filled in User: xxxxxx0001 and Password: as set in the DoorBird app. On the Advanced settings page: I simply put in the ip adress, eg 10.0.0.150. JPG path: bha-api/image.cgi MJPG stream path: bha-api/video.cgi To turn on the light, I simply put in the following in one of the move buttons: bha-api/light-on.cgi The "pause" or "stop movement" button can for instance be used to open the door, with the following: bha-api/open-door.cgi It works. But I wonder if I am misunderstanding something... I wonder why you guys encode the user:password into Base64? Is that just to make it more secure? If so, in what way is the above method insecure on my local LAN? I also wonder why you guys had to include user:password@DoorBird-IP-address instead of simply typing the IP-address in the IP-address field? As far as the Virtual device goes, I simply put the plain IP-address and port 80 in the General tab. Then it works as Guest suggested in the earlier post: So, what am I missing here? OleK
  14. Hi. Some time ago, this post, but still... What is your experience with this switch over time? Stability? Does it really work? I've had some issues with another similar wall switch... OleK
×
×
  • Create New...