Hello, congratulations, your project is really interesting, even if I have not yet had the opportunity to test on my HA platform. One question: after registering on the google maps platform API platform, how much does the service cost after the free trial period? Your script necessarily requires the use of a Google email. Quite right?
I just upgraded from 0.91.4 to 0.92.0. Now google_geocode isn’t working anymore. I get this error message when I restart HA. This comes from checking the config:
Integration google_geocode not found when trying to verify its sensor platform.
I don’t have any ideas.
There was a breaking change to custom components a few releases back. Did you change your folder location?
If you still have platforms in your
custom_components/directory in the old file format,sensor/my_platform.py, rename it tomy_platform/sensor.py. It still works but it will not be supported in a future release.
Not working either with that format are we missing the manifest.json ? I created one but still no luck
Yes, I corrected the breaking change to custom components when it was first changed. Something broke between 0.92 and 0.91.4.
Did you put the manifest in the google_geocode folder or the sensor folder? I have not updated my config yet so can’t test yet.
It looks like there is issues with other custom components moving to 0.92. Issue has not been fully resolved on this post
Yes I did, but not working other custom components are working fine …
have you tried adding an empty __init__.py file to the folder for the custom component
I’ve rolled back to 0.91.4. I’ll wait until they get the custom components fixed.
I have just updated to 0.92. I added the manifest.json file in my google geocode folder and everything worked as it should.
My file structure is custom_components>google_geocode
In that folder I have my hass generated pycache folder, manifest.json file and sensor.py file
My manifest.json file looks like this.
{
"domain": "google_geocode",
"name": "Google Geocode",
"documentation": "https://github.com/michaelmcarthur/GoogleGeocode-HASS",
"dependencies": [],
"codeowners": [],
"requirements": []
}
2 Likes
Does not work for me. Created a manifest file. But neither .yaml nor .json works.
What could be wrong?
try creating an empty __init__.py file in the same directory as the component
thats a double underscore before and after init
The name should be manifest.yaml or manifest.json?
It should be manifest.json. I’ll
Correct my previous post
Ok, correct…
Has anyone else managed to get the component to work?
If you are having issues can you post your error log? Thanks
All right here, after the manifest.jso file. Tks
1 Like
I added a manifest similar to yours and it works.
Thank you
1 Like
Ok, even I rolled back , I managed anyway to make the component work now.
Interesting thing: I got two warnings now after the restart:
Fri Apr 26 2019 17:01:06 GMT+0200 (Mitteleuropäische Sommerzeit)
You are using a custom component for google_geocode.sensor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant
and
Fri Apr 26 2019 17:01:06 GMT+0200 (Mitteleuropäische Sommerzeit)
You are using a custom component for google_geocode which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
The Google.geocode error is normal as it’s a custom component. The google.geocode.sensor looks like it think there is another custom component named google.geocode.sensor. That’s strange, I’m not sure why that’s happening.