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


emielstroeve

Member
  • Posts

    442
  • Joined

  • Last visited

About emielstroeve

Profile information

  • Country
    netherlands
  • Gateway/s
    Home Center 3

Recent Profile Visitors

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

emielstroeve's Achievements

Smart User

Smart User (3/8)

22

Reputation

  1. start from scratch: delete/exclude the rgbw module form HC3, reset the rgbw module to factory settings, than include again and hold the rgbw module within 1 m from HC3. if that doesn't work: call support
  2. data collections as in sql, I use MariaDB and also Grafana to display. Openhab does all the API interfacing to all sources like solar panels, climate/dust/weather sensors, heatpump, energie measurements and lots more.
  3. I'm using OpenHab, not only for home automation, but also for data collections
  4. unfortunately I don't use HC3 anymore.
  5. I have this working without any problem. I have 3 different white-only ledstrips in 3 rooms connected to 3 different colours of thr rgbw controller. Every room has an on/of switch connected to 3 different inputs and that all works fine. Parm 20-23 are set to 3, check other parms if they fit your setup
  6. you can do this in a block scene, something like when lightlevel of sensor == 0 and sensor == breached than turn on light.
  7. I didn't see any and I do see some other members also having the same problem.That is the risk of a one-person community solution.....
  8. did the previous owner transfer full admin rights?
  9. I do the same, but with OpenHab and the Hue bridge. The things you can set and read of a Hue motion sensor!
  10. no it doesn't. You can't see anything or change anything. Zigbee support in HC3 is terrible
  11. @jgaI did some extra testing: rule("$testVar=='thuis' & 09:19..09:45 => *some action* This one works fine, it doesn't run the action at 9:19 if $testVar <> 'thuis' so, works as expected rule("(@09:30 | $testVar=='thuis') & 09:19..09:45 => *some action* this one however, doesn't work as expected. It runs the action at 09:19 even when $testVar <> 'thuis' I guess the OR function messes things up? I do have other rules with the timing statement in an AND rule only, and that also works as expected.
  12. That's were it goes wrong, the action always runs at 15:30, even if $LuxNiveau1 <> 'schemer'. That's were the problem is. No, I want the action to run at latest at 20:00 or if it's 'schemer' but only in the timeframe 15:30-21:00. I know the timing conflicts between 20:00 and 21:00, I could set it to 15:30-20:00 no.
  13. So I have this rule: rule("(@20:00 | $LuxNiveau1=='schemer') & 15:30..21:01 => KippenLicht:value=30;hub.call(580,'Send_PushOver',json.encode({'Jachtlaan:','1','pushover','kippenhoklicht aan!'}))") the goal of this rule is that it checks the LuxNiveau1 level, or it's 20:00 hours, but it needs to be checked only between 15:30 and 21:01. In practice the rule is triggered at 15:30 without LuxNiveau1 == 'schemer', and obviously it's not 20:00 at 15:30. So I assume the trigger at 15:30 overrules the rule statements. Bug or as designed?
×
×
  • Create New...