Yes I do!
I found a clue in the following conversation thread:
[RELEASE] Zooz Power Strip VER 2.0
The relevant post is:
[[RELEASE] Zooz Power Strip VER 2.0 - #118 by krlaframboise
Wherein the author of the Zooz DTH on which the Greenwave PowerNode 6 DTH is based can be seen to have written
Nope…
I believe the issue is that you joined the device prior to 8/16/2020 and the only way you’re going to solve the problem with the child devices not working in the new mobile app is to delete them and save the settings so that when they’re re-created they won’t have a componentName or componentLabel.
Update: That’s based on the assumption that you’re getting a network error when you attempt to control the child devices in the new mobile app…
in response to a user witnessing nearly the identical problem with his Zooz as we are with our GreenWaves.
So in an aha! moment, I went to the IDE Device Handler page, edited GreenWave PowerNode 6 Zooz Frankenstein VER 2.0
(not sure if this link will work for non-me users, but in either case it’s the Greenwave/Frankenstein DTH parent, NOT the child)
searched for lines containing componentName or componentLabel, and commented them out, as thus:
Blockquote>
[
completedSetup: true,
isComponent: false,
label: “${device.displayName}-CH${endPoint}”
// componentLabel: “CH ${endPoint}”,
// componentName: “CH${endPoint}”
]
Then, I had to Exclude and re-Include the GreenWave device, but once that was done the master device plus all the individual outlets all appeared and once again were controllable, and accurately indicated status, from both the overview and the details screens.