I just did an upgrade to latest FW (Vera Edge/ 1.7.1142) and after this “success” upgrade (the upgrade itself went fine) the UI is constantly displaying Configuring Z-Wave devices in your system. in the status message. When I checked my luapnp.log it’s flooded with: 01 05/24/15 9:40:32.437 JobHandler_LuaUPnP::GetDayNight BAD DATE now 1432453232 9:40 sunrise -79200 sunset -79200 night 0 long 17.437000 lat 68.435997 <0x76cc5520>
01 05/24/15 9:40:32.437 AlarmManager::Run callback for alarm 0x8a1b68 entry 0x8bb740 type 20 id 94798 param=(nil) entry->when: 1800 time: 1432453232 tnum: 1 slow 0 tardy 1432451432 <0x76cc5520>
02 05/24/15 9:40:32.441 GetSunriseSunset error#1 sunrise: 1432336014/2015-05-23 01:06:54 sunset: 4294888096/<Invalid date -79200> midnight: 1432418400/9187108 <0x76cc5520>
Since these messages are repeated constantly it doesn’t take many minutes before the device reboots.
The problem only disappears if I reset to factory defaults. I’ve tried all of my backups, including reverting back to the old firmware and then restore backup config!
I did have some plugins (pleg/vera alert etc.) installed a couple of months ago but the system has been “clean” of plugins since then. (I’m using openHAB).
I really hope I can avoid having to re-include all my Z devices since that would have a big effect on the so far successful WAF (time to reconfigure everything and reaching the hard-to-get devices) :-[
Has anyone seen this error or similar? ???
First, don’t forget that Vera support will always be your best answer to such issues.
Based on the error messages, it says that you are close to Narvik. If this is not true, double check your city and Lon/Lat location settings.
Next it says invalid date with a calculated sunset time sunset: 4294888096. That’s 6 February 2106, 91 years into the future. Since there is a realistic sunrise date/time it appears to be a calculation error with something affecting the sunset date that is not affecting the sunrise date.
Verify location and timezone settings. Then restart Vera and make sure that the clock/time is being set correctly.
There should be no need to re-include anything. This is a Vera calculation issue, not a Z-wave device issue.
Thanks for replying! Lon/Lat is indeed correct. I’ve opened a support ticket but thought I would try my luck on the forums as well while waiting
I’ve double checked timezone settings, even tried to setting other zones, rebooting etc. just to see if the problem disappeared however it didn’t resolve anything.
I tried a complete factory reset and configure it from scratch but the errors came right back after configuring my timezone settings
Guess I’ll just have to wait for support to figure out something
02 05/28/15 11:49:29.489 GetSunriseSunset error#1 sunrise: 4294888096/<Invalid date -79200> sunset: 4294888096/<Invalid date -79200> midnight: 1432764000/7558508 <0x779a4520>
01 05/28/15 11:49:29.491 JobHandler_LuaUPnP::GetDayNight BAD DATE now 1432806569 11:49 sunrise -79200 sunset -79200 night 0 long 17.437000 lat 68.435997 <0x779a4520>
01 05/28/15 11:49:29.492 AlarmManager::Run callback for alarm 0x71eb68 entry 0x7e7c30 type 20 id 591703 param=(nil) entry->when: 1800 time: 1432806569 tnum: 1 slow 0 tardy 1432804769 <0x779a4520>
