Hello everyone,
I had two surprises this morning: the good one is that my raspi updated itself to 0.10, the bad one is that all times in rules have been resetted to NAN:NAN or null, resulting in strange rules behaviour (smart plugs went into some kind of “always on” state).
Luckily I didn’t have many of them and it took just a couple of minutes to fix, but it’s quite weird…
Update: also weird things (like missing addons) happened until I rebooted
Also on the new Localization setting there seems to be no way of updating the values, so country is always Afghanistan (which is the first country on the list); timezone and language seem to be ok but I set them through shell commands, so I am not sure it will work through the GUI
Thanks for reporting.
There’s a blog post going out today which explains the new timezone feature and that you may need to set your timezone and adjust your rules as a one-off.
Since the gateway is configured to use Greenwich Mean Time by default, your rules may show times you didn’t expect at first. To fix this, you’ll need to set your time zone appropriately and adjust your rule times.
The NAN thing and the missing add-ons issue are a bit odd. Does a hard reload of the page fix any of that?
Which localization settings can’t you set? They should all be writable if you’re using our Raspberry Pi build, though if you’ve previously changed things on the command line it’s possible that may be causing problems. Do you see anything in the browser logs or the gateway logs which indicates an error?
No reload fixed the weirdness, just a gateway restart (it took about 30 seconds after reboot to have the addons page populated).
I can’t change the Country value; it always displays Afghanistan. I also noticed that, while all other fields cause a reload of the page when you change them (and they work as intended), Country does not.
The problem is that the PUT on /settings/localization/country fails with a 500 error (but nothing about it results in the log - is there anywhere else I can look for more info on the error?).
The payload of the call is:
{“country”:“Italy”}
(but I tried with different countries and got the same error)
Can you try doing the following on the command line?
sudo raspi-config nonint do_wifi_country IT
echo $?
The command should return a 0 exit status.
it returned 1; I guess this happened because I am using a Raspberry Pi 2 and thus I have no wifi (and don’t need it for the foreseeable future).
The same happens if I call it with ‘US’ for example.
But if that settings is only used to set valid regional wifi settings, I am ok with leaving Afghanistan 
Ah! That would be the issue. This feature is really only used for setting the Wi-Fi country code, which is used to configure channels and such.
ok thanks, maybe you could think about removing that voice for no wifi hardware; I thought it had to do with something like “get news from your country”
Well, if you had a wi-fi dongle plugged in, it would still be valid for that RPi.