DVF smart home integration, free and open source
Property sales near your home in France and median prices per m², from open DVF data.
Published by guim31
- Devices
- Version 1.1.0
- Requires Gladys >=5.3.0
- ★ 0
Brings into Gladys the property sales published around your home in France and the median prices per m² of flats and houses, from Demandes de valeurs foncières (DVF): the sales recorded by the DGFiP (French tax administration), geolocated and published as open data by Etalab. No account, no key.
It is information, not a valuation of your home. DVF only publishes the price, the date, the type and the surface of a property sold: not its condition, floor or works. A median over few sales varies a lot. Integration not affiliated with the DGFiP nor Etalab.
Tested on the real DVF files (Toulouse, Vigoulet-Auzil, Paris) and on the SDK's fake Gladys, not yet on a real Gladys instance: feedback welcome.
What you get
- A "Property sales" device per followed zone, with:
- the median price per m² of flats and houses over the last 12 published months, and over the 12 months before (to compare year on year);
- the number of sales of dwellings over both periods;
- the date of the latest sale published and the month the data reach.
- A scene trigger "New property sales published", with their number, at every new DVF release.
- A scene action "Property sales summary": a sentence ready to send in a message ("Within 1 km of Maison: 225 sales in the 12 months published up to December 2025; median prices: flats 4,866 €/m².").
- A dashboard widget: the median prices and the latest sales of the zone (1 to 10, 10 by default: number and street, type, surface, price, date, distance from the house).
- A "Check now" button in the configuration, giving that summary for each zone.
Requirements
- Gladys Assistant 5.3.0 or later.
- Internet access from Gladys: the integration reads
files.data.gouv.fr(the DVF files) andgeo.api.gouv.fr(the commune of a location). - A house in France, outside Alsace-Moselle (Bas-Rhin, Haut-Rhin, Moselle) and Mayotte, where DVF does not exist (own land register).
- For the default option, the location of your house in Gladys (Settings, Houses). The integration asks for it at installation (the "location" permission). It is only used to find the communes of the zone and the distance of the sales; it is neither stored nor written to the logs.
Configuration
Settings
| Setting | What it does |
|---|---|
| Location | My house in Gladys (default), All my houses in Gladys or A commune (INSEE code). |
| House | Empty (default): every house of Gladys that has a location, one device each. A house: that one only. |
| Zone around the house | 100 m, 200 m, 300 m, 500 m, 1 km (default), 2 km, or Its whole commune. A circle may cover several communes: their sales are read. |
| INSEE code of the commune | 5 characters, not the postcode: 31555 for Toulouse, 2A004 for Ajaccio. |
| Language of the feature names | Names of the features of a new device, language of the dates, of the summary and of the trigger variables. French by default. |
Save, then open the Discover tab of the integration and add the device. The first download takes from a few seconds (small commune) to a minute (Paris).
Paris, Lyon, Marseille
DVF is published there by district (arrondissement). Around a house, the integration reads
the districts the zone touches; with "Its whole commune", the district of the house; with the
INSEE code of the city (75056, 69123, 13055), all its districts.
Check it: "Check now"
The button reads the houses, the zone and the data again, then shows a summary per zone. A clear error message shows at the top of the configuration when something is missing (no location, unknown INSEE code, commune without DVF, service unreachable).
Device
| Feature | Value |
|---|---|
| Flats, median €/m² (12 months) | Median price per m² of the sales of a single flat, last 12 published months. |
| Houses, median €/m² (12 months) | The same for houses. |
| Flats / Houses, median €/m² (year before) | The same medians over the 12 months before. |
| Sales (12 months), Sales (year before) | Number of sales of dwellings (flats and houses) over each period. |
| Latest sale published | Date of the most recent sale of the zone. |
| Data published up to | The month the current DVF release reaches ("December 2025"). |
A median is only published from 3 sales: below that, the feature stays without a value. The "last 12 months" are those of the release, not of today: DVF comes months after the sales.
Widget
Add the Property sales widget to the dashboard. Settings: the zone (empty: the first one), switches to hide the median prices, the latest sales or their addresses, and the number of sales shown (1, 3, 5 or 10, 10 by default: Gladys shows 10 rows at most in a widget list). It shows three tiles (flats, houses, number of sales; next to each median, in brackets, the number of sales it rests on), then the latest sales, and the source with the name given to the device in Gladys. A sale shows its number and street when the DVF file gives them, never the postcode, the commune nor anyone's name; otherwise its type, rooms and surface.
With a 100 m or 200 m zone, a city centre gives a few dozen sales a year, often fewer: a median resting on 3 to 10 sales moves a lot from one release to the next. Look at the number in brackets before drawing conclusions.
Scene trigger and action
- New property sales published: fires when a new DVF release brings sales more recent than the latest known in the zone. Filter: the zone (empty: every zone). Variables: number of new sales, zone, release month, sales over 12 months, flat and house medians, summary sentence. The first release seen (or a changed zone) fires nothing: it is the baseline.
- Property sales summary: returns the summary sentence and the figures of a zone, for the next action (send a message, for example). The sentence of the scene action and of the trigger ends with the latest sale of the zone ("Latest sale: 12B RUE DE L EXEMPLE, flat 52 m², 250,000 €, on 31/12/2025."), its number and street included when the file gives them; the "Check now" button leaves it out.
Scene examples
- "When new sales are published around Maison, send me the summary on Telegram."
- "On the first of the month at 9 am, send me the summary of the sales of my commune."
Data, licence and quotas
- Source: "Demandes de valeurs foncières géolocalisées", DGFiP and Etalab, under the Licence
Ouverte 2.0, on
files.data.gouv.fr/geo-dvf. Five years of sales, updated twice a year (around April and October), months after the sales. - Sales kept: sales, off-plan sales and auctions including at least one flat or house. Exchanges, building plots and expropriations are left out. The price per m² only comes from the sales of a single dwelling (outbuildings included, no shop or office), outliers excluded (under 200 or over 50,000 €/m²).
- Downloads: a small index page once a day to see whether a new release is out; the
files (one per commune and year) only when it is, kept in
/data. No quota is published for these services; the integration stays far below any reasonable one. - DVF reuse terms: trying to re-identify people (sellers, buyers) is forbidden. The files hold no name and no personal data is published by the integration: it keeps and shows the number and street of a sale as Etalab publishes them (never the postcode, the commune, the parcel nor a name), the type, the surface, the price, the date and a distance.
Troubleshooting
| Symptom | What to do |
|---|---|
| "No house of Gladys has a location" | Place the house on the map in Settings → Houses, or choose "A commune (INSEE code)". |
| "no DVF data in Alsace-Moselle and Mayotte" | DVF does not exist in these departments: the integration cannot show anything there. |
| "files.data.gouv.fr cannot be reached" | Check the Internet access of Gladys. The integration retries every hour and keeps its data. |
| A median stays empty | Fewer than 3 sales of that type in the zone: make it larger (2 km, or the whole commune). |
| The sales are months old | Normal: DVF is published twice a year, several months late. |
Detailed logs: environment variable LOG_LEVEL=debug.
Limits
- The data are 4 to 10 months behind the sales, and a sale may only appear in a later release.
- A 2 km zone reads the communes found at the centre and at 12 points of the circle: a commune touched only between two points may be missed.
- The sales without coordinates in DVF (rare) only count with "Its whole commune" or an INSEE code.
- The feature names are frozen when the device is created.
Configuration settings
These are the settings DVF asks for in its configuration screen in Gladys.
| Setting | Type | Required | Description |
|---|---|---|---|
| Your zone | section | No | Choose where the sales are read: around your house in Gladys (default) or in a commune by its INSEE code. Save, then create the device in the Discover tab. The data are checked once a day. |
| Sources and limits | section | No | Demandes de valeurs foncières (DVF), DGFiP, geolocated by Etalab, read without an account. Published twice a year, months after the sale; none in Alsace-Moselle and Mayotte. Not affiliated with the DGFiP nor Etalab. |
| Location | select | No | My house: the house chosen below (empty: every house). All my houses: every house of Gladys that has a location, one device each. Commune: the INSEE code below. |
| House | select | No | Used when Location is "My house in Gladys". Empty: every house of Gladys that has a location. To go back to every house, choose "All my houses in Gladys" above. |
| Zone around the house | select | No | The sales within this distance of the house (its location in Gladys), or every sale of its commune. |
| INSEE code of the commune | string | No | 5 characters, not the postcode: 31555 for Toulouse, 2A004 for Ajaccio. Used when Location is "A commune". |
| Language of the feature names | select | No | Names given to the features of a new device, and language of its texts (dates, summary, trigger variables). |
How to install DVF in Gladys
- In Gladys, open Integrations: DVF appears in the catalog, next to the native integrations, with a community badge.
- Click Install. Gladys pulls the Docker image (
ghcr.io/guim31/gladys-dvf:1.1.0), starts it in a sandbox isolated from the core, and generates the integration's interface (devices, discovery and configuration). - Open the Configuration screen of the integration, fill in the settings, and save.
- You can also install it directly from its repository URL: https://github.com/guim31/gladys-dvf.
DVF requires Gladys >=5.3.0. The catalog inside Gladys refreshes every hour, so a new version becomes available at most one hour after its release.
Not running Gladys yet? It is free and open source: follow the installation guide to get started.
About external integrations
DVF is an external integration: a community integration packaged as a Docker container and published on GitHub, that Gladys installs in one click and runs in a sandbox isolated from its core. It is published and maintained by guim31, not by the Gladys core team.
- Browse all integrations, native and community
- Build and publish your own external integration
- Source code on GitHub — source of this documentation