wiserHomeAssistantPlatform
wiserHomeAssistantPlatform copied to clipboard
ZigBee network map shows smart plugs all connecting to Hub when they may connect to another smart plug
Love the new network map feature - really helpful. Only noticed one thing that wasn't quite right. All the smart plugs say they are connected directly to the hub but that isn't the case in my setup as most of mine are daisy chained.
The connections come from the parent node id the device is showing. I assume on the signal sensor for your plugs they also show connected to the hub directly in the attributes?
Are you able to provide a json output using the wiser output json service to export to files so i can see if it is just how the hub works or there is some bug in our api. Thx
The connections come from the parent node id the device is showing. I assume on the signal sensor for your plugs they also show connected to the hub directly in the attributes?
Are you able to provide a json output using the wiser output json service to export to files so i can see if it is just how the hub works or there is some bug in our api. Thx
Thinking back - yes, I believe the plugs have always shown up as being connected to the hub directly even though they aren't. Always made it difficult to establish where the weak point in the network was in the past as the smart plugs are in an environment with many 1m thick stone walls which can be very challenging.
JSONs attached
domain-20220710-201430.json.txt network-20220710-201430.json.txt schedules-20220710-201430.json.txt
I did look at mine before you sent this and smartplugs do not show a parent node id like other devices do, so we just set it to 0 in the api which is the node id for the hub. Im sure they used to have this and also used to show a signal strength % but not just show online. Sorry, not much we can do about this. Your json files show the same thing.
I will pick up with Angelo to see if we can get an understanding from Wiser why this was changed and if it could be changed back in a future hub firmware update.
No worries. Still love the network map though!
I was looking at this and alas I only have one plug.. I guess its still showing this?
@tombadog99 Is this still an issue? ok to close?
Yes, this is still an issue.
I'll do some more digging , ignore my ignorance but how do you know the plugs are daisy chained?
This needs raising with Jamie as it is the hub that no longer supplies this info
I'll do some more digging , ignore my ignorance but how do you know the plugs are daisy chained?
My hub is at one end of the house. Due to the construction of the house (nearly 1m thick stone walls), it is impossible that the smart plugs are all connected to the hub. The signal can barely get through one!
Email sent to Jaimee, . Unless the hub exposes the data we cant report on it.
hey @tombadog99
Just checking, if you disconnect the SP closest to the TRV, does the connection still work? or does it disappear off the network?
I have this setup and if I turn my middle SP off all my distant TRV go offline as they were connected to my end of the line SP. Hopefully that made sense!? 😁
yes, im speaking to Jamie about this. Alas given nothing is "broken" , its going to be difficult for him to get it prioritised. unlike the trvs not closing or the hub going off line etc.. Im hoping we can confirm that the metadata is missing and they can fix it whilst they fix something else.
Would agree that it isn't high priority. Would be useful but not vital. Other bugs you mention much more important.
On Fri, 9 Dec 2022, 08:58 Angelo Santagata, @.***> wrote:
yes, im speaking to Jamie about this. Alas given nothing is "broken" , its just a nice to have , i dont think we can give this high priority (unlike the trvs not closing or the hub going off line etc)..
— Reply to this email directly, view it on GitHub https://github.com/asantaga/wiserHomeAssistantPlatform/issues/274#issuecomment-1344028069, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQ4P2ZPZIRQLHOBMRHDARSTWMLYE3ANCNFSM53FH42YA . You are receiving this because you were mentioned.Message ID: @.***>
Ive not heard back from our wiser "friend", alas, this is what the hub is reporting so I think we're stuck with it..
No problem. It's still useful as it is.
Will close this issue as cannot resolve without Wiser making hub firmware change.