Thank you Michael, it works now.
just so I am clear on things : my HSB devices are currently configured as below which is no longer working;
this is essientially the " color picker as the parent and the sliders as grouped children" . Correct ?
and this wouldn't be compatible with HS4.
So the new standard is this
which is a "group under the xxxxx topic/parent " And I must keep the parent (3511) ;
Other than keeping parent/children in sync, It's essentially just a "placeholder/nametag", right?
I also can't build on my current HSB devices which must be deleted and created fresh, correct? no big deal but just want to make sure I'm not generating extra work if not needed.
Since mcsMQTT started creating parent devices, I deleted all of them without impact since they didn't have any known dependancies/children. Except for HSB.
Would this be an issue when I upgrade to HS4? will the parent devices be "re-enabled" automatically or will I have to delete all devices and start over?
Can I "re-enable" the parent devices now in HS3 if needed?
Last question, for the scenario below; could I safely delete 2484/2631 or do they act as Parent for all "message:id" and "message:unit" topics (lower in screenshot)?
At one point I remember having to click the "Check to treat JSON key" checkbox to parse the data which no longer seem to be the case, so I assume you have "automated" the parsing for such devices?
Thanks,
just so I am clear on things : my HSB devices are currently configured as below which is no longer working;
this is essientially the " color picker as the parent and the sliders as grouped children" . Correct ?
and this wouldn't be compatible with HS4.
So the new standard is this
which is a "group under the xxxxx topic/parent " And I must keep the parent (3511) ;
Other than keeping parent/children in sync, It's essentially just a "placeholder/nametag", right?
I also can't build on my current HSB devices which must be deleted and created fresh, correct? no big deal but just want to make sure I'm not generating extra work if not needed.
Since mcsMQTT started creating parent devices, I deleted all of them without impact since they didn't have any known dependancies/children. Except for HSB.
Would this be an issue when I upgrade to HS4? will the parent devices be "re-enabled" automatically or will I have to delete all devices and start over?
Can I "re-enable" the parent devices now in HS3 if needed?
Last question, for the scenario below; could I safely delete 2484/2631 or do they act as Parent for all "message:id" and "message:unit" topics (lower in screenshot)?
At one point I remember having to click the "Check to treat JSON key" checkbox to parse the data which no longer seem to be the case, so I assume you have "automated" the parsing for such devices?
Thanks,
Comment