-
Notifications
You must be signed in to change notification settings - Fork 5
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
Installation in HassOS image #19
Comments
I'm sure it can be made to work and am happy to accept well-tested pull-requests. There should be plenty of folks who can answer questions about how to install a custom component on whatever commonly-supported approaches there are. |
Thanks, I will look for some help on this and get back to you. Thanks again, I am looking forward to life with Vantage again. |
@gjbadros @colohan I am trying to look at this again. I have the newest HASS image running, and have tried to interpret the installation instructions the best I can. I am expecting the IU to populate with the Vantage components. ( as it did when I added my Wyze stuff ). Something has connected, as I see a file called "/config/192.168.2.101_config.txt" that is the xml of my Vantage. |
Look at the 192.168.2.101_config.txt as it's probably not well-formed XML and may hold clues to the problem. |
That file parses fine for me. I'm guessing it's from a prior run because I think the error you point at comes from earlier code before the XML config is written out to a file. It's related to this gjbadros/pyvantage@6e7e08e Which is from a PR from @filmackay: You can either add some debugging code yourself to make the problem obvious to us or work with him: https://github.com/gjbadros/pyvantage/commits?author=filmackay My guess is that that PR assumes a more recent version of the vantage controller that perhaps responds to GetFile requests with a correct XML response. You could also just try reverting that part of that commit (just go back to the old code that I previously wrote for lines 1371-1377). |
I am sorry I am not a developer, I am just trying to install this and get it working on my simple system. Can you help me at a more consumer level? It seems that this could be deployed in the HACS system and be available to any level of HA enthusiast. |
I feel for you -- I don't have the time to make this end-user friendly but
am always happy to look at contributions if you want to pay a python
developer to help you out.
…On Fri, May 26, 2023 at 11:15 AM Steve Spaw ***@***.***> wrote:
I am sorry I am not a developer, I am just trying to install this and get
it working on my simple system. Can you help me at a more consumer level?
It seems that this could be deployed in the HACS system and be available to
any level of HA enthusiast.
I would even to pay to make this work.
—
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALOHTP3UDHQMM37VE2QC3DXIDXNJANCNFSM6AAAAAAWUCXCFM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@stevespaw your DC version is very old (?) are you on an older version for a reason? The .txt file looks fine - can you delete it, re-run and see if it generates something different (XML invalid)? I don't think the old version of DC is an issue - as the .txt file parses OK there must be something else in play. I loaded the .xml file and parsed it with the exact same XML library/runtime, and as expected it parsed just fine. So that tells you that what is being parsed in your HA, is not what is in the .txt file. Don't worry, we'll sort this out.. |
Looking at the code, if you bring up Diagnostics (via DC) and make a GetFile call to retrieve the file It is possible that upgrading the s/w in your controller (with DC 4.x) could (in theory) change/fix the behaviour here? |
@gjbadros Progress has been made! Many Thanks to @filmackay for his help in diagnosing. It seems that the minimum DC may be 3.9. |
Glad to hear it. Your mental model re the config file is wrong -- it is retrieved from your controller not generated. If the newly retrieved config.txt does not have the new VID in it, then your controller is not serving that new file to hass-vantage. Be sure you're saving the config to the memory card when you do a program. |
Yes I understand that it is getting it from the controller, but I may not have saved to the memory card - Checking now. |
HMMM I am at a loss, So I may have been just doing "updates" instead of the full "program". But I did a full "Program" and wrote to the memory card, and even deleted the config .txt. After an HA restart - same thing, the VID with the new variable id not in the config.txt, nor shows up in HA. So, it is copying the XML from the Controller's memory card? Is it being cached somewhere maybe? |
It definitely is in the dc file saved locally. ??? |
More strangeness - I just noticed that the config.txt that is loading is from my old DC version 3.7 I am now using 3.9 (and that is what my local saved DC file is). Where can this be coming from? I am doing an F7 save to memory card from my 3.9 - no errors. |
The memory card seems to be write protected. I have the project.dc in the memory card diags, but it is months old and I cannot delete it. Any ideas? |
OK, The memory card was the issue, I put in another one and it works fine as described a simple HA restart and it loaded the new one fine. Now I have to figure out my Equinox bad card..... Will I need Equinox? - That is the question :-) |
@gjbadros
I am also running this in the newest prebuilt container. Can the install script be tweaked for this?
It runs from the root folder and there are no homeassistant directories.
I am a former Vantage dealer with it in my home. I am new to Home Assistant and am so excited that this could possibly work.
I am happy to help diagnose this in any way. If the only way to make it work is in a Linux install I will do that, but this HassOS image is a pretty slick and easy method.
I am currently running on Virtualbox, but will migrate this to a dedicated box if I can get this Vantage integration to work.
Thanks for the work on this, it could be a lifesaver for many Vantage people.
Steve
The text was updated successfully, but these errors were encountered: