-
-
Notifications
You must be signed in to change notification settings - Fork 514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please insert a timestamp in the restful API #1199
Comments
I know, that there is a possibility to access the /api/ntp/time , but this is a second access and i use a slow 8266 to read the values, so if I read the /api/ntp/time for time and then read /api/livedata/status for the data, I have a delay due to 2 accesses (my Wifi is rather bad and the 8266 is also slow). |
@Frogowitsch I understand and second your request for a timestamp in several of the API endpoints. This would need to be considered in our REST API documentation #378. I have also seen that the dusk / dawn times have to be queried under Info > NTP whereas the setting for which type of sunset / dawn can be set under Settings > NTP only. Settings > NTP NTP Settings
Why is the list not sorted by degrees ° and the IMHO Civil dawn (96°) marked as default ? Settings > NTP NTP Information |
Allows to connect to SBS Unipower batteries using a CAN bus.
@tbnobody I would add to the request that we add a Leaflet Geosearch address entry field to the Settings > NTP Settings. Look at this Stackoverflow for some example implementations using Leaflet and pure Java Script: get latitude & longitude as per address given for leaflet I have updated the example with the latest Leaflet library and css 1.9.4 references and hashes, |
Is your feature request related to a problem? Please describe.
Its hard to synchronize with other devices. It would also be nice to have the ability to set a delta time for ntp sync.
Describe the solution you'd like
A unix timestamp in the restful api would be rather easy to implement and help a lot.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: