Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enh : Add Mesh details showing nodeId and parentNodeId #67

Closed
asantaga opened this issue Feb 17, 2020 · 9 comments
Closed

Enh : Add Mesh details showing nodeId and parentNodeId #67

asantaga opened this issue Feb 17, 2020 · 9 comments

Comments

@asantaga
Copy link
Owner

Within the devices payload there are two elements
NodeId and ParentNodeId

For TRVs and RoomStats

  • If parentNodeId == 0 then the connection to the hub is direct
  • If parentNodeId !=0 then the connection to the hub is via a SmartPlug/Range Extender whos Id is parentNodeId

Adding this to the iTRV and RoomStat data payloads as rawdata
Also adding a computed attribute called "HubConnection" which will be either

  • Direct

This is really useful to know when diagnosing/mapping how you trvs are communicating to the wiser hub..

Fab, really well thought out system this wiser stuff is..

@scooper1
Copy link

scooper1 commented Feb 17, 2020 via email

@asantaga
Copy link
Owner Author

asantaga commented Feb 17, 2020

Precisely what I wanted to find out :-)

I also found out if the battery level is <26 then its time to replace the batteries.. Whilst they show as "good" on a battery tester , there isnt enough juice to turn the actuator in the valve...

I may add that as an additional attribute

how does

 attribute name : replace_batteries : true or false 

How does this sound ? Only for TRVs BTW

With this you can easily create an alert / notification :-) :-)

LOVE Automation

@scooper1
Copy link

scooper1 commented Feb 17, 2020 via email

@scooper1
Copy link

scooper1 commented Feb 17, 2020 via email

@Fulch
Copy link

Fulch commented Feb 18, 2020

"Zigbee": { "NetworkChannel": 25,

Could be a useful attribute to display under WiserHub data? It might help people with connectivity problems to at least know what Zigbee channel is being used and maybe then change their Wifi channel or any other Zigbee devices to minimise potential interference.

I don't know if the NetworkChannel is read only and have not been brave enough to try changing it!
The link below explains about Zigbee and Wifi channel overlap.

https://support.metageek.com/hc/en-us/articles/203845040-ZigBee-and-WiFi-Coexistence

@asantaga
Copy link
Owner Author

asantaga commented Feb 19, 2020

Cool,

I'll be implementing this either tonight or tomorrow and I want to get R1.9 out soon.

SoI plan to expose :

node_id : {number}
parent_node_id : {number}
zigbee_network_channel : {number}
replace_batteries  : {true | false}   , will be based on a config variable (default of 26) value<config then returns true

Two config variables

replace_roomstat_batteries_threshold: {number default 20}

Are the defaults about right?
Will do this tonight, shouldnt take more than 1hr..

@scooper1
Copy link

scooper1 commented Feb 19, 2020 via email

@asantaga
Copy link
Owner Author

yes the node_id will be exposed, it was in the text but I had a markdown error.. so it wasnt showing, fixed that.

@asantaga
Copy link
Owner Author

Done, commit 92f7d68

Added the zigbee channel data to the heathub sensor
Added Zigbee nodeId,parentNodeId and calculated field hub_route to iTRV and RoomStats

DID NOT add the battery threshold figures because I noticed there was a field called BatteryLevel which when goes to OneThird pretty much says the same thing..

I also noticed that not all iTRVs have battery data in the raw payload.. dont know why.. may be it appears after a while..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants