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


Slaves for HC3 1.0.0

   (5 reviews)

4 Screenshots

About This File

Those QuickApps intend to use as a slave devices on HC3 to emulate original devices on HC2/HCL or secondary HC3.

The main purpose is to emulate devices of HC2 controller to create same environment on HC3 before migrating the devices. You can use these devices as standard HC3 devices in Lua, block scenes and QuickApp (triggers and control). After migration you just need to delete slaves and change device IDs in code. To make it easy, recommended to use json Home Table.

In addition if you intend to keep HC2 or HCL as part of your Home Automation, these slaves provide an option to run your system on HC3 only.

You can expand your HCL usage by using Lua, block scenes and QA on HC3 to control and monitor devices on HCL.

Please use slaves according to device functionality. For sensors use SlaveSensor, for dimmers use SlaveDimmer, for RGBW dimmers use SlaveColor or SlaveColorW (option to change white level).

It's very important to use correct KeyFob slave (sceneActivation or central Scene)

After downloading the QA, open user_data file and enter credentials, IP and device ID. slaveRate value is in milliseconds and  determines the time rate to fetch the data from original device.

For example if device on HC2 turned ON, within 700 milliseconds the slave device on HC3 will be turned ON also

Spoiler

image.thumb.png.fb8f9ba1ea4ed32a9b962626d75af305.png

 

Every slave device has an option to stop/start emulation by pressing toggle button .

Spoiler

image.thumb.png.a6cc6d68cdff02635bf15f3d02cfc878.png

 


What's New in Version 1.0.0   See changelog

Released

Have added Slave Mulitlevel QA for level sensors (temperature, humidity, lux, ebergy and etc) emulation .

 

  • Like 1


User Feedback

You may only provide a review once you have downloaded the file.


michal85pl

   3 of 3 members found this review helpful 3 / 3 members

Great job, is there any chance to add QA for Motion Sensor?

Response from the author:

There is a QA for motion sensor

Please download SlaveSensor-v2.fqa

This QA works for all kind of sensors, like door, motion, smoke and others

Link to review
Rafal_ll

· Edited by Rafal_ll

   3 of 3 members found this review helpful 3 / 3 members

Very handy. Thanks

-------------------------------------

Is it possible to make a temperature sensor

  • Like 1
Link to review
AR27690

   2 of 2 members found this review helpful 2 / 2 members

An excellent piece of code to use HC2 devices on HC3 without transferring them.

Thanks.

Link to review
Sankotronic

   1 of 1 member found this review helpful 1 / 1 member

Very useful solution to help with gradually moving from HC2 to HC3. I have tested few of the QA and used them to test some of my new solutions on HC3 keeping HC2 still having main controll of our house. Thank you @cag014 for yet another excellent solution!

 

  • Like 1
Link to review
lux

  

SlaveRemote_centralScene-v2.fqa SlaveRemote_sceneActivation-v2.fqa not run!

Link to review
×
×
  • Create New...