-
Notifications
You must be signed in to change notification settings - Fork 43
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
Comments
Good idea
Helps in knowing if extender is helping Should this be applied to plug extender as well so you know if extender is getting data via another extender ?
Sent from Yahoo Mail on Android
On Mon, 17 Feb 2020 at 10:37, Angelo Santagata<notifications@github.com> wrote:
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..
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
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
How does this sound ? Only for TRVs BTW With this you can easily create an alert / notification :-) :-) LOVE Automation |
Seams a good ideaI have a lovelace page showing battery status
Maybe a bit high for RoomStat
Might be good idea to have a defaulted config value one for trv battery minimum level and one for roomstat
Sent from Yahoo Mail on Android
On Mon, 17 Feb 2020 at 11:58, Angelo Santagata<notifications@github.com> wrote:
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
Sound?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
The battery levels might different depending on the battery type so a config level would be good for that as well
Sent from Yahoo Mail on Android
On Mon, 17 Feb 2020 at 11:58, Angelo Santagata<notifications@github.com> wrote:
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
Sound?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
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! https://support.metageek.com/hc/en-us/articles/203845040-ZigBee-and-WiFi-Coexistence |
Cool, I'll be implementing this either tonight or tomorrow and I want to get R1.9 out soon. SoI plan to expose :
Two config variables
Are the defaults about right? |
Should the node Id be exposed on all devices so can workout who is the parent Id related to
Would be very nice to have 1.9 out so many changes have happened
Sent from Yahoo Mail on Android
On Wed, 19 Feb 2020 at 11:57, Angelo Santagata<notifications@github.com> wrote:
Cool,
I'll be implementing this either tonight or tomorrow and I want to get R1.9 out soon.
SoI plan to expose :
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}
I wont make the zigbee value read/write, too intrusive..
Will do this tonight, shouldnt take more than 1hr..
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
yes the node_id will be exposed, it was in the text but I had a markdown error.. so it wasnt showing, fixed that. |
Done, commit 92f7d68 Added the zigbee channel data to the heathub sensor DID NOT add the battery threshold figures because I noticed there was a field called I also noticed that not all iTRVs have battery data in the raw payload.. dont know why.. may be it appears after a while.. |
Within the devices payload there are two elements
NodeId and ParentNodeId
For TRVs and RoomStats
Adding this to the iTRV and RoomStat data payloads as rawdata
Also adding a computed attribute called "HubConnection" which will be either
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..
The text was updated successfully, but these errors were encountered: