iotplay / homedig2 Goto Github PK

Think the answer is the device must still send changes in attribute statusses.

https://github.com/IoTPlay/homedig2/blob/master/docs/1_homedig2_how.md

• Download template from NR for node
• Study it, Build

• Seperate NR flow for all test data & invoctions
• Doc how to use

now.

To handle the intra-NR containers communications, which will allow modularisation of the functions, plus changes can then be made only in the module, plus it will be reusable to others.

• Structure current 'one-flow' into multiple NR instances (and sep. containers)cwhich will interact via mqtt:

• 1. Prime : (homedig2)

• 2. Test : (homedig2Test)

• 3. R&D : (homedig2RD) New features not in production yet (like RF bridge, etc.)

• 4. ClientSpecific

• Retest all flows.

And diff ones for different applications

Use the GitHub wiki.

• mqtt
• HomeBridge
• homedig2 in Docker
• Other flows in own flow/s

• On flow - 3. On how it works - http endpoint is done.
• Document the effects & where to set cfg_vars
• A1c and 4b is the same thing - fix to 4b.
• Reference to HomeKit standard:
• http://auto.caitken.com/posts/2018/09/09/nodered-homekit-reference
• http://auto.caitken.com/posts/2018/09/09/nodered-homekit-characteristics-reference
• Spelling on README.md - 'iitiating'

https://github.com/IoTPlay/homedig2/blob/master/docs/1_homedig2_how.md