Investigate whether there is an open and free Geocoding API for this, but it would greatly simplify the Gladys installation process:
Edit: I have the impression that this API ( https://geocode.maps.co/ ) does the job without an API key:
https://geocode.maps.co/search?q=66%20avenue%20des%20champs%20%C3%A9lys%C3%A9es%2075008%20Paris
I use this one to retrieve past Tesla data. But there is an API key: Openroute service
It must work without an API key — we’re not going to ask the user to enter an API key while they’re installing Gladys
guim31
March 24, 2025, 8:56pm
4
I use geocode in one of my web projects, it works pretty well but, like all services with postal addresses, it’s sometimes not updated quickly (cadastral changes etc…)
Yes, I figured ^^
I originally thought of a generic API key to begin with ^^
But there’s also the On-Premise version — the bundle is light enough just for localization. (HeiGIT Account )
Otherwise Teslamate uses OpenStreetMap
So your topic gave me a crazy idea:
05:30 coffee
06:00 hot shower
06:30 warm car and route on the car’s dashboard (the best route for that time will be chosen by the car) incorporating the stop at the bakery.
The official service of OpenStreetMap is Nominatim, which is free and has no API key.
I quickly integrated it, here are some images:
If still interested, I can generate an image for testing
I’ll put the PR up tonight with a test image.
Here is the PR
master ← William-De71:features/house-address-search
ouvert 06:10PM - 13 Jul 26 UTC
Pull Request check-list
To ensure your Pull Request can be accepted as fast a… s possible, make sure to review and check all of these items:
- [ ] If your changes affect the code, did you write the tests?
- [x] Are server tests passing with coverage? (cd server && npm run coverage) — Codecov requires 100% coverage on lines changed in this PR (front-end only change, no server code touched)
- [ ] Did Cypress E2E tests pass? (npm run cypress:run from repo root, if UI changed)
- [ ] Is the linter passing? (npm run eslint on both front/server)
- [ ] Did you run prettier? (npm run prettier on both front/server)
- [x] If you are adding a new feature/service, did you run the integration comparator? (npm run compare-translations on front) (translations added in en/fr/de)
- [x] Did you test this pull request in real life? With real devices?
- [x] If your changes modify the API (REST or Node.js), did you modify the API documentation? (no API change)
- [ ] If you are adding a new features/services which needs explanation, did you modify the user documentation?
- [x] Did you add fake requests data for the demo mode (front/src/config/demo.js)? (not needed: Nominatim is called directly from the browser, no Gladys backend request involved)
Description of change
Currently, setting the home address requires manually panning/zooming the map and clicking on the exact location, which is tedious — especially on the world-level default view during signup.
This PR adds a text search field above the map to find the home address by typing it:
- The typed address is geocoded with Nominatim (the OpenStreetMap geocoding service): free, no API key required.
- Up to 5 results are displayed; clicking one centers the map on the selected address.
- The map stays clickable to fine-tune the position afterwards.
- The search is only triggered on an explicit user action (button click or Enter key), to comply with the Nominatim usage policy (max 1 request/second — no search-as-you-type).
- Available in both places where the house location is set:
- House settings (Settings → House)
- Signup, house configuration step
- Error and "no results" states are handled with dedicated translated messages (en/fr/de).
No backend change: the Nominatim API is called directly from the browser.
[Screenshots:](https://community.gladysassistant.com/t/pouvoir-taper-ladresse-de-sa-maison-au-lieu-de-selectionner-sur-la-carte/9450)
The image is being built: docker pull willde71/gladys-test:house_adress_search
