-
Notifications
You must be signed in to change notification settings - Fork 38
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
3.0.4 KeyError Traceback on startup: setts["evc_ip_address"]=evcList[1][0] #327
Comments
Ok, something is amiss here. I’ll need to make you a special dev version with some extra debugging added. I’ll dm you |
So really strangely GivTCP started working ok on my test VM so I restarted HA a few times and it carried on working. So I then decided to try and reproduce the whole thing by wiping the GivTCP folder. Second time around it now just gives me the traceback error on every start of GivTCP for the evcList. Really annoying because I can't find a consistency in its behaviour, but 99% of the time it failed with the same error on startup so at least I'm guaranteed to reproduce the error once you have a debug version available. |
My feeling is that this is driven by networking/subnets etc... Will try and get you a dev test version in the next day or so. |
Actually, I've just seen what I think the the issue is... evclist is a collection of found EVCs, I want to check the first item in the list and get details, but in your example above the first item in the list is numbered 2. I bet this is a python indexing thing. I might need to index an enumerated list... let me try a fix and let you know. Could you post the same log as above with the working test VM (which i suspect finds the evc on the first listed subnet!) |
Sounds promising thank you :) Unfortunately I didn't snapshot the VM before wiping the GivTCP config so now I can't get it to work. I'll try several more times this evening and if it eventually decides to work I'll grab the log. |
Ok, so I've managed to get it running again after many dozens of startup attempts. So firstly, this is a failed startup log:
It started once and allowed me to run the web config, but then failed again a lot after that. But then after many more attempts it suddenly burst into life! No mention of the EVC in the working startup though (.187) so I'm wondering if it just didn't notice it in the scan on this occasion which is why it worked?
|
Having a similar issue here.
|
This issue has been present for a while but I had multiple issues and wasn't certain which ones were related or not. I'm now certain that this issue is unique and related to detecting the EVC. I am running v3.0.4 in a test virtual machine (VirtualBox) for the moment, I haven't moved from 2.4.9 on my 'production' installation yet due to this issue.
The text was updated successfully, but these errors were encountered: