Well, once again, thank you @VonOx! Indeed, I was on an old page that was not modifiable ^^ Apparently, it’s okay to modify, but apparently, it’s not now:
So I don’t really understand how to start the documentation regarding the previous quote:
The Airtable list is just a source (easier than writing in JSON files) that needs to be imported into the JSON files for the website page to be up to date. I tried to do an import at the beginning of the year, but the site literally exploded after that, and I haven’t had time to look into it since
That’s the main thing and I’m really glad everything went well We took the time to test to have that exactly
For the evolutions:
The camera view is not related to Netatmo. We use the same view as the « standard » cameras, you need to create an issue on GitHub for all cameras
The refresh rate is a bit complicated, to be validated with @Terdious but if we make too many requests we get 403 (not authorized). However, Netatmo cameras detect presence I think, so it sends an event that we can retrieve
The display order is the same, it’s more for all services not just Netatmo, you can also create an issue
And the next step is indeed the set temperature / events (events when you change the temperature via the application or automatically).
Yes, once the PR is merged, this will be the first evolution we will bring. But as @damalgos says, we will need thorough testing to avoid falling back into this 403 error.
For the operation, the image sent by Netatmo when there is no detection is only recorded every minute. So even if we set it to 10s, if there is no detection, the image remains the same. However, we can use the events to retrieve it more frequently. It’s an extra piece of code to be developed on the side.
In the future, there will be no need for this as we will operate with webhooks. But we need to look into it as we don’t know about it at the moment.
Yes, why wouldn’t it be?
You have a camera, whether it’s from Netatmo or any other manufacturer. You just want an image, so it’s best to have a single dashboard for all images. That way, if you want to improve the camera view, you only improve one dashboard and not all the services.
Yes, this is not related to Netatmo but to Gladys in general But you’re right, it can be useful.
So for that, yes of course, for the moment you can manage otherwise. You delete the features of your box and you select them in the desired order. It works for me.
Ok, I just tested it, on the test and the prod… my bad, I was misled by the fact that I separated them into different boxes ^^ Indeed, you are right, we will have to go through an issue, sorry ^^
One more small request if you can, could you download the PR I made for the Netatmo documentation, and check in English and French if it seems good to you based on your experience?
If it’s a hassle for you, I can try to make some screenshots.
Thank you so much for your feedback and for your time.
Yes, I am currently finishing the editing part (especially for the weather station/anemometer where you can change the wind angle in degrees or cardinal points)