Hello,
Here is an external integration for vigieau:
It should be available soon on the store
Don’t hesitate to give me your feedback regarding this external integration.
Edit: It’s available 
Great, very useful with all these repeated heatwaves.
Yes, that’s normal regarding the current restrictions. For now, we display it here, but we could later have it displayed in a text feature.
As for the rest, what do you have in the logs?
And if you can give me your INSEE code in a private message, I can do some tests this afternoon
I have a connection issue with VigiEau. Error: VigiEau HTTP 409
[2026-08-05T09:46:06.428Z] [INFO] Starting the VigiEau integration...
[2026-08-05T09:46:06.922Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80)
[2026-08-05T09:46:06.935Z] [WARN] No INSEE commune code configured yet: nothing to discover
[2026-08-05T09:59:04.360Z] [INFO] onConfigUpdated -> new configuration received
[2026-08-05T09:59:04.369Z] [INFO] Published 1 device(s) to the Discovery screen
[2026-08-05T09:59:04.369Z] [INFO] [drought-zone] Refreshing VigiEau every 3600 s
[2026-08-05T09:59:04.370Z] [INFO] [drought-zone] Polling VigiEau for Maison...
[2026-08-05T09:59:04.513Z] [ERROR] [drought-zone] VigiEau refresh failed Error: VigiEau HTTP 409
at fetchZones (file:///app/src/vigieau.js:131:11)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async Object.onPoll (file:///app/src/devices/droughtZone.js:148:19)
at async Object.refresh (file:///app/src/devices/droughtZone.js:213:7)
[2026-08-05T09:59:08.702Z] [INFO] Action rechercher_commune <- Thouars 79100
[2026-08-05T09:59:08.980Z] [INFO] Published 1 device(s) to the Discovery screen
[2026-08-05T09:59:08.981Z] [INFO] [drought-zone] Refreshing VigiEau every 3600 s
[2026-08-05T09:59:08.981Z] [INFO] [drought-zone] Polling VigiEau for Maison...
[2026-08-05T09:59:09.071Z] [ERROR] [drought-zone] VigiEau refresh failed Error: VigiEau HTTP 409
at fetchZones (file:///app/src/vigieau.js:131:11)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async Object.onPoll (file:///app/src/devices/droughtZone.js:148:19)
at async Object.refresh (file:///app/src/devices/droughtZone.js:213:7)
[2026-08-05T09:59:18.111Z] [INFO] [drought-zone] Action test_vigieau -> live request to the VigiEau API
[2026-08-05T09:59:24.670Z] [INFO] [drought-zone] Action show_restrictions -> live request to the VigiEau API
[2026-08-05T09:59:44.389Z] [INFO] onDeviceCreated -> ext:ext-prohand-gladys-vigieau:drought-zone:commune-79329, refreshing right away
[2026-08-05T09:59:44.389Z] [INFO] [drought-zone] Polling VigiEau for Maison...
[2026-08-05T09:59:44.471Z] [ERROR] [drought-zone] VigiEau refresh failed Error: VigiEau HTTP 409
at fetchZones (file:///app/src/vigieau.js:131:11)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async Object.onPoll (file:///app/src/devices/droughtZone.js:148:19)
at async Object.refresh (file:///app/src/devices/droughtZone.js:213:7)
at async Promise.all (index 0)
at async refreshNow (file:///app/index.js:102:3)
at async file:///app/index.js:122:3
at async GladysIntegration._runHandler (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1166:7)
at async GladysIntegration._handleMessage (/app/node_modules/@gladysassistant/integration-sdk/lib/gladys-integration.js:1026:9)
[2026-08-05T10:01:27.277Z] [INFO] [drought-zone] Action test_vigieau -> live request to the VigiEau API
[2026-08-05T10:01:31.712Z] [INFO] [drought-zone] Action test_vigieau -> live request to the VigiEau API
[2026-08-05T10:01:33.119Z] [INFO] [drought-zone] Action show_restrictions -> live request to the VigiEau API
[2026-08-05T10:05:18.859Z] [INFO] onConfigUpdated -> new configuration received
[2026-08-05T10:05:18.869Z] [INFO] Published 1 device(s) to the Discovery screen
[2026-08-05T10:05:18.869Z] [INFO] [drought-zone] Refreshing VigiEau every 3600 s
[2026-08-05T10:05:18.869Z] [INFO] [drought-zone] Polling VigiEau for Maison...
[2026-08-05T10:05:18.967Z] [ERROR] [drought-zone] VigiEau refresh failed Error: VigiEau HTTP 409
at fetchZones (file:///app/src/vigieau.js:131:11)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async Object.onPoll (file:///app/src/devices/droughtZone.js:148:19)
at async Object.refresh (file:///app/src/devices/droughtZone.js:213:7)
Can you take a screenshot of the config section for me, please?
Ok thanks for your reply.
My logs:
[2026-08-05T10:00:42.577Z] [INFO] Starting the VigiEau integration...
[2026-08-05T10:00:42.827Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80)
[2026-08-05T10:00:42.878Z] [WARN] No INSEE commune code configured yet: nothing to discover
[2026-08-05T10:01:30.137Z] [INFO] onConfigUpdated -> new configuration received
[2026-08-05T10:01:30.156Z] [INFO] Published 1 device(s) to the Discovery screen
[2026-08-05T10:01:30.157Z] [INFO] [drought-zone] Refreshing VigiEau every 3600 s
[2026-08-05T10:01:30.158Z] [INFO] [drought-zone] Polling VigiEau for Maison...
[2026-08-05T10:01:30.308Z] [INFO] [drought-zone] Read: level=4 (SUP=4 SOU=4 AEP=2), 19 restricted usage(s)
[2026-08-05T10:01:38.206Z] [INFO] Action rechercher_commune <- ma-commune
[2026-08-05T10:01:42.151Z] [INFO] [drought-zone] Action test_vigieau -> live request to the VigiEau API
[2026-08-05T10:01:44.636Z] [INFO] [drought-zone] Action show_restrictions -> live request to the VigiEau API
[2026-08-05T10:01:54.895Z] [INFO] onDeviceCreated -> ext:ext-prohand-gladys-vigieau:drought-zone:commune-82005, refreshing right away
[2026-08-05T10:01:54.896Z] [INFO] [drought-zone] Polling VigiEau for Maison...
[2026-08-05T10:01:54.965Z] [INFO] [drought-zone] Read: level=4 (SUP=4 SOU=4 AEP=2), 19 restricted usage(s)
[2026-08-05T10:03:16.292Z] [INFO] [drought-zone] Action show_restrictions -> live request to the VigiEau API
[2026-08-05T11:01:30.193Z] [INFO] [drought-zone] Polling VigiEau for Maison...
[2026-08-05T11:01:30.291Z] [INFO] [drought-zone] Read: level=4 (SUP=4 SOU=4 AEP=2), 19 restricted usage(s)
It’s a cool integration, and easy to set up, thanks for the work!
I looked on the vigieau website and apparently there is no alert other than drinking water for your INSEE code, you can check directly on the vigieau website so by default it goes to unknown:
Perhaps it would be more relevant to display « No risk »
I’ll get claude to work on the subject
When we look on the vigieau website, we get this message when trying to view alerts for your commune:
I’ll also get claude to work on the subject 
And it’s in progress
I’ll keep you posted when the new version can be released
I published a version that fixes the 409 error
Basically, you no longer need to enter the INSEE code but the address
The latitude and longitude are automatically filled in
To get the correct alerts, I recommend entering at least the name of your street + postal code + city
If you only enter your city, it will take the city center and the alerts may be incorrect.
Note: Version 1.1.0 is breaking:
This is a breaking change. The device’s external_id becomes latlon-… instead of commune-… : after updating, run the address search, then add the new discovered device and delete the old one.
I will also look into displaying the last entered address for information
@guim31 For your issue, claude is still working on it
Version 1.1.0 should be available in less than an hour
Version 1.1.1 is published and fixes your bug @guim31
It should be available within 1 hour
Let me know when you’ve been able to update
Hello,
Try using a comma instead of a period
Edit: I will ask claude to correct the example that shows dots and is therefore confusing
I will push a new version this evening with this correction.
Even better, can the app understand whether it’s a period or a comma?
I’ll ask him
My next token reset is around 7 p.m., so I’ll do it then
When I tried earlier, it didn’t work, neither with a period nor with a comma.
I confirm, colon or semicolon doesn’t work 
Do you have logs?
Because when you enter the address below, the GPS coordinates are automatically added with a comma
Edit: I see the bug, it changes the comma to a dot
I’ll keep you posted when it’s fixed
