Child devices

[Neo Andersson 179]

Hello everyone

 

May I have some questions regarding Child devices.

I have read JGAB's tutorial on this scope, and its very useful, but there are some questions still arising in my mind, what i couldn't get answered.

Question1:

What is the purpose of a child devices? Why do we use them? I can't explain to myself why would I mess around with all those initializations and 

definitions if it seems to me that everything can be solved right within the parent QA.

Question 2:

On other hand i can see some situations when it might become handy if it worked. Like the picture attached, It is a thermostat with linked devices..

Now the first thing is, i don't know if these devices are child devices, or are linked devices, or are both of them?

Question 3:

If in the picture atteched we see child devices. Are they the same "CHILD" devices as you are describing in your tutorial ? If so, how can we make an existing

device become a child device of our QA? Or am I completely misunderstood this topic? 

Can we add an existing real device as a child to a QA, or a CHILD device can be only a QA made child device, kinda virtual one?

 

Thanks

Please login or register to see this attachment.

[10der 830]

i have device. for example this device is old android 5.0 device with Zipatile FW.

i do not use Zipato and Zipatile software at all but this device can pass to me 

(1)* the current temp

(2)* the current hum

(3)* the current lux

(4)* the current noice

(5)* the current motion

(6)* Power On state

 

so. now for you. 

you like when you develop 6 (six) separated QA's instead on develop all code in one single QA what can create and control all 6 (six) child devices

Please login or register to see this attachment.

 

PS:

after screenshot i forgot about but

Please login or register to see this attachment.

ton keys, cuz device can pass to me pressing on the screen some buttons

 

 

 

Edited January 9, 2022 by 10der

[Neo Andersson 179]

Thanks for your answer, 

I understand what you say..ofcourse its better to handle all those 6 fetures in one QA..but i asked, why you need child devices for this..Why not jsut a normal QA.?  You can easily get all 6 features from 1 QA without having any child device..

And there is my major question..How can you make an exisiting device become a child device of a QA..this is what is far beyond my current comprehension..

[10der 830]

57 minutes ago, Neo Andersson said:

Can we add an existing real device as a child to a QA, or a CHILD device can be only a QA made child device, kinda virtual one?

no u can't. but you can wrap exists real device to QA

2 minutes ago, Neo Andersson said:

Why not jsut a normal QA.?

still do not catch your question.

 

again. if you hate child  please crate 6 (six) QA with temp hum etc etc so on so on 

another trying to catch your question 

how i can draw temp hum etc etc so on so on on single title of QA? you can draw only temp / hum / lux  etc

yes you can draw anything on expanded panel but... i wanna to see all and at once

 

[10der 830]

Please login or register to see this attachment.

[Neo Andersson 179]

All those 22C°, 2 C°, 46 °C etc etc are coming from that one device right?

And it is a real device Zipato right?

Then how did you make CHILD of them..You said its not possible...

Man i can't get it...

I have made a zone controller QA which can user use in YUBII for PLAN adjusting and for extended time selection for ovveride..but i never used any child device context...

In your example, you are using your Zipato as child device of a QA ??? You said its not possible...

Please login or register to see this attachment.

[Neo Andersson 179]

Here above forexample the Current temperature is coming from device 789. The panel operation mode (Auto Off Cool Heat) is coming from a Panel Climate Zone with ID 32...so these are two different devices in my QA.

How can I make forexample a child device from my Temperature sensor 789 ? 

Is this a good example where i could use Child device or this is not the case ?

[10der 830]

1 hour ago, Neo Andersson said:

Can we add an existing real device as a child to a QA

no u can't

 

dixi

24 minutes ago, Neo Andersson said:

In your example, you are using your Zipato as child device of a QA ??? You said its not possible...

it's NOT real Zwave device!

[Neo Andersson 179]

So you created a QA, where you are getting all these data from some other real device by using API calls i guess ?

Then you cretated separate child devices for all these data types inside that QA ?

 

 

[10der 830]

1 hour ago, Neo Andersson said:

API calls i guess

mqtt but it do not care right now

answer = yes

[petrkl12 208]

3 hours ago, Neo Andersson said:

Hello everyone

 

May I have some questions regarding Child devices.

I have read JGAB's tutorial on this scope, and its very useful, but there are some questions still arising in my mind, what i couldn't get answered.

Question1:

What is the purpose of a child devices? Why do we use them? I can't explain to myself why would I mess around with all those initializations and 

definitions if it seems to me that everything can be solved right within the parent QA.

Question 2:

On other hand i can see some situations when it might become handy if it worked. Like the picture attached, It is a thermostat with linked devices..

Now the first thing is, i don't know if these devices are child devices, or are linked devices, or are both of them?

Question 3:

If in the picture atteched we see child devices. Are they the same "CHILD" devices as you are describing in your tutorial ? If so, how can we make an existing

device become a child device of our QA? Or am I completely misunderstood this topic? 

Can we add an existing real device as a child to a QA, or a CHILD device can be only a QA made child device, kinda virtual one?

 

Thanks

 

Q1:

to have source code in one place, less memory consumption, you don't need to create mechanism how to exchange data between your QAs, ...

Q2: example of QA child devices - how it looks (my Evohome QA)

Please login or register to see this attachment.

Q3:

it's not possible to change existing QA to child device. You have to create them from your parent QA device (example is in jgab code or in fibaro's tutorials)

example of parent QA device - you have to write logic how to create child devices, how to refresh them etc.

Please login or register to see this attachment.

 

 

Edited January 9, 2022 by petrkl12

[Speedo67 1]

Hello Neo Andersson,

i can't make a contribution to your child-questions, but i would ask you to share your zone-controller QA.
It looks good, i am searching for such QA.

Thank you in advance.