-
Notifications
You must be signed in to change notification settings - Fork 25
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
[USAGE] #102
Comments
@stockreign Thanx for reporting. Could you post the code you are using? |
#include <ESP8266WiFi.h> const int led = LED_BUILTIN; String dateTime = ""; ESP8266WebServer server(80); void handleRoot() { void getDateFromNtp() {
} void handleNotFound(){ void setup(void){ // Wait for connection if (MDNS.begin("esp8266")) { server.on("/", handleRoot); server.onNotFound(handleNotFound); server.begin(); void loop(void){
}else{ } |
@stockreign Thanx. I see. Your using https://github.com/alexstocker/sensordata/blob/master/sensordata.ino |
Thank you for reply. I had it with IP address, i got to have device ID name on the device list in nextcloud, but no data is showing and i am still getting HTTTP response error. |
@stockreign you should try to send some random data from your PC first using a cron job / PHP script / curl in a loop. I had to configure https on my side for which I am using the WiFiClientBearSSL library There are various ways to verify the certificate chain of your Let's Encrypt certificate chain too. @alexstocker are there plans to provide an example for getting LoRaWAN messages from The Things Network / The Things Stack into sensorlogger too ? |
Here is the routine I use from Earle's library https://github.com/earlephilhower/bearssl-esp8266
You may need or want to adjust for the timezone setting depending on your location and the ntp servers used. |
@stockreign You may also look into the example https://github.com/alexstocker/sensordata/ and the proposed fix by @christoschronopoulos in alexstocker/sensordata#6 |
Platform you are using
Sensors/Hardware
Your Goals
Your Question
The text was updated successfully, but these errors were encountered: