Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.49
Python release (python3 --version):
3.6.1
Component/platform:
device_tracker.luci
Description of problem:
After upgrading lede to master, device tracker stops working.
error message: 403 invalid token
Expected:
device tracker working
Additional info:
I'm using official docker image. I'm compiling LEDE for my Mikrotik hAP AC on every Friday.
device_tracker.luci just stops working from this Friday. Upgrading HA from 0.48.1 to 0.49 doesn't solve the problem
Changing it to ubus solves the issue, but I'd like to use device_tracker.luci
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
this is still an issue in .80 *I cannot install .81without issues
Not working - issue not resolved
@djm300 and @TDWhbp and @dh-harald is this still an issue? If it is, can you provide any more documentation? If it's not an easy, can this issue be closed?
@JudgeDreddKLC This issue mainly on openwrt/lede side...
I've opened an issue for them: https://github.com/openwrt/luci/issues/1300
There's two problems:
Currently I've a dirty patch for cookie authentication method (I don't want to share it, because I'm not proud for it, but it's working :) ), but currently I've not other solution for net.arptable, than I'm patching back that command into luci every time, when I'm refreshing luci
Hello!
jsonrpc is not working any more again with auth GET parameter
dh-harald pasted pa patch 6 month ago at https://github.com/openwrt/luci/issues/1300 , but it doesn work any more..
Again getting error 403
@dh-harald: did you figured out, what is the problem with GET auth this time?
Regards
Here are the news:
So in this moment, every issue has been solved on luci side (thanks for @jow-)
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:
I upgraded to OpenWRT 18.06 and have been working on a fix for the luci device_tracker to work with the newer methods. It is working for me. I will do some final testing and open a PR tomorrow hopefully.
Anyone have experience with PIP ? It would be great if someone can bundle the Pull request so we can have this feature without hacks.
@fbradyirl I made dev_tracker based on luci but instead of scan arp table it uses iw command wifi.getiwinfo to get associated station list. Added extra attr: signal strength and inactive time. Works on openwrt v17.x with updated (fixed auth issue receiving http 403) luci-mod-rpc package. If someone interesting...
@fbradyirl I made dev_tracker based on luci but instead of scan arp table it uses iw command
wifi.getiwinfoto get associated station list. Added extra attr: signal strength and inactive time. Works on openwrt v17.x with updated (fixed auth issue receiving http 403) luci-mod-rpc package. If someone interesting...
That would work, but for me it is not an option as I do not use wifi on my OpenWRT router. It does many things but wifi is not one of them.
@fbradyirl I made dev_tracker based on luci but instead of scan arp table it uses iw command
wifi.getiwinfoto get associated station list. Added extra attr: signal strength and inactive time. Works on openwrt v17.x with updated (fixed auth issue receiving http 403) luci-mod-rpc package. If someone interesting...
Same here... I'm using present detection for wired devices as well
@fbradyirl I made dev_tracker based on luci but instead of scan arp table it uses iw command
wifi.getiwinfoto get associated station list. Added extra attr: signal strength and inactive time. Works on openwrt v17.x with updated (fixed auth issue receiving http 403) luci-mod-rpc package. If someone interesting...
Is it in your fork or as separate library for Home Assistant ?
I made separate lib called luci_ap. It is primary based on luci.py
Added new option device to define wifi device - default is wlan0-1 but when using multiple AP on openWrt could be different. Maybe it can accept list instead od single value.
Imho for present detection it is more precise then scan arp table on router. Using now with consider_home: 300. Works quite well.
Your modded script working like a charm @rds76. Many thanks for this.
I鈥檓 working on this at present. Should have a PR opened on HA this week hopefully. This will work for non wifi devices.
@rds76 i took a look at your luci_ap script and I could integrate your wifi rpc calls into my module.
https://github.com/fbradyirl/openwrt-luci-rpc
So that it prefers wifi devices and also falls back to use arp. Might ask you to code review or test it when done? Then I could use open PR on HA.
@fbradyirl I'm afraid your version wont work for me. I'm on openwrt 17.26 with updated rpc lua (fixed auth). If I remember, rcp command neighbors is not available there and as I use openwrt as just AP, there is not possible to use arp as well. My moded HA luci version uses wifi.getiwinfo rpc call.
@rds76 No, that will be OK but I am already detecting the the version in my module, so when I detect version 17 I simply won't use the neighbours ip api. See here
@fbradyirl I saw it, but when neighbours fails, you gonna use arp table lookup, what does not suit my needs, cause my openwrt do not act as router.
@fbradyirl I saw it, but when
neighboursfails, you gonna use arp table lookup, what does not suit my needs, cause my openwrt do not act as router.
But I will make it silently return an empty list in that case, instead of bombing out. So if either the router is used in only AP mode, router mode, or both, I will make it work for all those cases.
Understand but it is not solution for me. Will stay with my moded version. After using it for 3months I can say it works very well - no issue so far
Most helpful comment
I upgraded to OpenWRT 18.06 and have been working on a fix for the luci device_tracker to work with the newer methods. It is working for me. I will do some final testing and open a PR tomorrow hopefully.