tonyapuzzo/home-assistant-config

Home Assistant Configuration

home-assistant-config's Issues

make it an integration?

Hi Tony
I have been using your openevse setup for a while, have you ever considered making it a proper HACS component?
it would be great to ave it available with the notifications for updates etc.

Config errors with input_select after hass.io upgrade to 0.92

Config checker produces the following message after upgrading HASS.IO to 0.92.0

Integration not found: introduction
Invalid config for [input_select]: [values] is an invalid option for [input_select]. Check: input_select->input_select->openevse_service_level->values. (See ?, line ?). Please check the docs at https://home-assistant.io/components/input_select/

OpenEVSE charge current setting changing randomly

Hello,

I'm experiencing odd behavior since a recent update of the OpenEVSE.yaml where the charge current (as by the pilot signal) will change to a different value, seemingly on its own, and is all over the place as to the value - Today it was 19 amps. My default is 40A, the change occurs at unknown times, maybe 4-5 times a week, so not every day, but I'm only noticing because I'm checking. I've turned off the Set OpenEVSE Charge Current automation to see if the updates still happen, which has disabled the slider, and will report, but I'm wondering if this behavior is the result of something intentional or if anybody else has experienced it.

I do not have logging to SQL enabled since a recent SD card death, presumably due to over-use, so I realize that I could probably be a lot more helpful.

Thank you.

Package openevse setup failed.

Followed everything but I am getting this error when trying to reboot HA
rest_cmd folder is in custom_components

Package openevse setup failed. Component rest_cmd Integration 'rest_cmd' not found.
Invalid config for [input_select]: [values] is an invalid option for [input_select]. Check: input_select->input_select->openevse_service_level->values. (See ?, line ?).

Latest Upload of openevse.yaml Doesn't Work/Missing Config

Looks like the last upload of the openevse.yaml file doesn't work correctly.
There are three failures with the build in Configuration Validation routine built in to HA.

The first failure is the file is using automations old, which has been replaced with automations_old. Easily fixed.

The second failure is that the sample secrets.yaml content at the top of the file is missing:

OPENEVSE_REST_GET_CURRENT_CAPACITY_RANGE: "openevse/rapi/in/$GC"

Again easily fixed, by adding the line in and then finding the correct RAPI code required.

However the third failure I cannot find the cause. The validation test fails with:

"expected a dictionary for dictionary value @ data['packages']['sensor']"

In my experience that error usually means a bad character, but I cannot find it.
I did try removing various parts of the file to see whether I could pin down the line with the error, but I kept getting the same error referencing different parts of the file. I only got no errors when everything above the automations was removed, so the error is in that section somewhere, but I can't find it.

Steps to reproduce.

1. Add the packages definition to the HA configuration and reboot.
2. Download the YAML file directly by right click on the RAW button on the page and save it to the packages directory.
3. Create the secrets file.
4. Go in to Server controls and choose Check Configuration under Configuration Validation. Corrections as above.

I used the built in File editor to modify the file.
It looks like a good package, so thank you for the work you have put in.

still working

Hi tony,
can I ask you if this project is still alive?
I have installed it to integrate my openEVSE on HA but some features show issues, not sure if due to latest change in HA.