February 12, 2019 at 6:03 pm #1429
It seems that when I set the OG with a static ip address, the time in the log becomes invalid. I think I first noticed this in 1.0.9 and it’s still there in 1.1.0
It works fine using DHCP.
Just an FYI.
Thanks, aFebruary 15, 2019 at 2:38 pm #1431
OK, I will check. I don’t think it should have anything to do with static ip vs. DHCP — the only reason for time being invalid would be NTP time sync fails.
By the way, even with DHCP, you can still set a fixed IP, by going to your router’s configuration page, and set a DHCP reservation for the device (basically binding a fixed IP to its MAC address). This is effectively static IP, but managed using the router.February 19, 2019 at 3:51 pm #1434
Thanks, Ray. That is, in fact, how I created the new static ip. I only noticed it because in trying to reset the device, the default is DHCP and suddenly the time was right in the log. I then set a static ip address and the time stamps were all wrong. Initially I did not use DHCP because I use a different sub-net to isolate all my IOT devices, JIFC. I’d like to go back to that policy, so please let me know if you find the problem. Again, thanks.March 29, 2019 at 9:11 pm #1522
I noticed the same thing after setting a static IP. Not a big deal for me since I’m using Home Assistant and that’s my source of truth for logging, but I still decided to manage my IP reservation through the router to remedy this.April 18, 2019 at 8:53 am #1568
I found the same issue.
On top of this, it also seems if the date/time is wrong, blynk doesn’t see the board online. As soon as you use DHCP and date/time is correct, blynk says the board is online.
You must be logged in to reply to this topic.