@Razr In my opinion it shows that the webserver is in place - the step to exposing data there is almost trivial, and we need to make sure they know there is enough interest there to give us access to this data.

One can but hope.

Tor

@Razr I never raised a support ticket - the only contact I have had with them until the call was set up was through this forum. It may have been because I supplied opinions underpinned by facts? I have set up my own continous latency monitoring as a good example, making it easier to describe the problme and find the cause of the problem than just a vague complaint?

All my postings are available on the forums here - so I guess that there was something there that caught supports interest.

Tor

I think it would be useful to be able to manually specify and lock down which node connects to which other node, for both the powerline and wireless backhauls.Displaying RSSI, or some other signal quality indicator, for both backhauls between nodes would help.

@bds_  And the information is readily available in the OS - from one of my nodes (sorry about the bad formatting)

wlanconfig ath13 list

ADDR               AID CHAN TXRATE RXRATE RSSI MINRSSI MAXRSSI IDLE  TXSEQ  RXSEQ  CAPS        ACAPS     ERP    STATE MAXRATE(DOT11) HTCAPS ASSOCTIME    IEs   MODE PSMODE

b6:be:76:e1:ff:f3    3   48 390M      6M   24       0      24    6      0   65535   EPs         1         4b              0          AWPSM 139:21:24 TP IEEE80211_MODE_11AC_VHT80  0

as far as I can see this is the powerline interface (I may be wrong (-;) - and you can see the link running at 48 Mbit/s down and 6 Mbit/s down. And the RSSI is also there.

So from my point of view there is little work that needs to be done to expose this in the web interface.

And some network structure data that would also be helpful when you place your nodes :

~[ main ] 168: get network info success!~
~[ main ] 169: The number of remote devices in the network is 5~
~[ main ] 174: host: C4:71:54:BE:0C:xx     avgRx is 77     avgTx is 85~
~[ main ] 174: host: 34:E8:94:40:05:xx     avgRx is 182    avgTx is 156~
~[ main ] 174: host: 34:E8:94:13:27:xx     avgRx is 150    avgTx is 171~
~[ main ] 174: host: C4:71:54:BE:11:xx     avgRx is 11     avgTx is 11~
~[ main ] 174: host: 34:E8:94:40:09:xx     avgRx is 317    avgTx is 241~

If I had this available when I placed my nodes I would have avoided a lot of frustrations.

So a question for TP-Link - what about giving us access to all this data - my ADSL router is a Fritzbox, and I can ssh into the OS of the box, and they give me lots of good data available in there web-based user interface as well, making me a very happy customer, and has solved a lot of issues with our ADSL line without having to call support?

Could you please follow up their example - I bet this could sell a lot more P7's. Or at the very least answer questions easier.

Tor
 

@Tor-Arne Very interesting. It would indeed be very helpful to have this data available when setting up the network.

Do you know if the network config is setup once, then saved, continuously dynamically adjusted, or reconfigured after every power cycle?

@bds_ It's dynamic - it will have to be in a mesh network. In my case changing the RSSI values made all the difference in connecting to the stringes signal, not anything else.

Tor

@Kevin_Z 

What are the updates from TP link on getting the access to change settings and monitor powerline as the last few posts on this chain noted helped resolve some (all?) of the P7 connectivity issues?

Can you reach out to your managers and update us? Thanks.

@Kevin_Z 

Hi, I wanted to follow up as it has been a week since I posted the last message and it has been without updates from customer support. Here it is submitted again:

What are the updates from TP link on getting the access to change settings and monitor powerline as the last few posts on this chain noted helped resolve some (all?) of the P7 connectivity issues?

Can you reach out to your managers and update us? Thanks.