Closed jstewart99 closed 2 years ago
I have one UAP-Pro, 2 x UAP-AC-Pro, and one UAP-AC-M. Those all work. I don't know if anyone ever tried an AC-Lite before.
Can you run the "Write Controller Data to Log" menu command, then put that in a zipped plain text file and attach it to this issue?
Turn on debug level logging and try to change the type of the device again.
Also, is '786171553' the Device ID of the Indigo device for the AC-Lite?
Unless you're in a huge hurry, give me a few days to dig into that data.
Zero rush, and you owe me nothing for this fine free plugin so take your time sir! :)
Hold up, just reloaded the plugin and everything seems to have resolved. I swear I thought I'd already done that but I guess not. Ugh...sorry for the time waste (aside from the "About" menu item going to the wrong forum page, haha). Deleting my data file post for privacy reasons.
One other unrelated thing, I just noticed my MiniUnifi plugin Log folder is like 14GB (has the last 5 days at nearly 3GB each file. Is that normal? Bit of a disk space hog. I'm pretty sure I just had the logging set to Warning Messages (not sure if that's related as to what writes to the main Log file).
Yeah, you can delete that. I probably put too much in there.
Tried to change some old "Unifi Device" APs to the updated "Access Point". A few worked fine, but I noticed the two AC-Lite's that I have did not update and started throwing errors in the Log. I'd suspect the older UAP-LR might also run into a similar problem (I'd already updated it a while ago through so I'm not sure). AC-Pro and AC-LR updated fine. Log error for the Lites:
Traceback (most recent call last): File "plugin.py", line 122, in runConcurrentThread KeyError: 'key id 786171553 not found in database'
I can delete and recreate I'm sure, it's just a hassle since I have some Control Page stuff set up that requires retooling if I go that route, so the ability to update the device type would be handy.