Securifi Community Forum
Securifi Products => Almond+ => Topic started by: Ethan on January 31, 2015, 04:04:20 am
-
Is there any way to do it? :o
-
Hard reset... :-\
You won't lose any sensors or any automation rules doing this.
http://wiki.securifi.com/index.php?title=Hardware_reset_button_-_Almond%2B_2014
-
Seriously? Hard reset for that?
Put it in the danm settings page.... gah.
-
It's a security feature, the same goes for most things.
That said, I guess you have a point, this isn't a phone so...
I'll bring it up with the software team.
-
If you're already logged into the router settings where you can change everything else, not being able to see the screen pin is an annoyance, not a feature.
-
If you have authenticated with more secure credentials (i.e. a potentially long password), you should be able to reset less secure credentials. This way, people like me who use password managers and long, randomized passwords can easily reset the screen PIN without having to record it somewhere.
Of course, what I would really love to see is a command line with SSH key authentication and a good configuration system like Junos. Mmm. Maybe support for client-side certificates for web UI authentication. That tends to be bizarrely difficult to set up in a lot of modern browsers, though.
-
Something along these lines? http://wiki.securifi.com/index.php?title=SSH_Access_-_Almond%2B_2014
-
Huh! Sure enough. I didn't think Dropbear had support for key-based authentication.
Of course, that still leaves the Junos-style CLI, but that should be easy, right? ;)
Somewhat more seriously, I will have to experiment with the CLI some time. My Trapeze system works well enough, but configuration changes are a headache. That part is off-topic, though I wonder where the screen PIN is stored. Surely it could be overwritten with SSH access.
-
Huh! Sure enough. I didn't think Dropbear had support for key-based authentication.
Of course, that still leaves the Junos-style CLI, but that should be easy, right? ;)
Somewhat more seriously, I will have to experiment with the CLI some time. My Trapeze system works well enough, but configuration changes are a headache. That part is off-topic, though I wonder where the screen PIN is stored. Surely it could be overwritten with SSH access.
Not sure if you can overwrite it, but if you can SSH in, have you tried /etc/config/memory ?
-
I don't remember ever setting or using a pin and after randomly hitting the lock in the R070 clock app I seem to be locked out. Default pin does not seem to work.
-
Reboot leaves me at a pin entry screen I have never seen before. I guess I will have to look at the hard reset but still no idea how a non-default pin was set.
I do still have webUI access but I don't see any of the dropbear config. Under the management tile I get Router Passwrod and SSH-Access Keys and thats it.
-
OK solved. After ssh'ing in and looking at /etc/config/memory (thanks for that) I can see my pin is '0'. And that works. Still no idea how I would not have the default pin.
-
Thanks for this. I don't remember ever setting a screen PIN and similarly got locked out when I hit the lock icon on the clock screen. Using pin '0' worked for me too.
-
The firmware update post needs to be fixed to indicate the default pin code is 0, not 1234. I had the same issue.
-
The default pin is 1234, I've confirmed this with the software team. As to why some of you are ending up with it being 0, I don't know and I've informed them about this.
We're going to be adding an option to turn on/off the LCD password from the web UI, but please note that you still need to know the web UI password to be able to disable the LCD UI password from the web UI.
-
1234 worked for me (thank god) - freaked when i was testing the thermometer/time thingy.
So don't change the wiki because 1234 worked for me... and maybe others...
-
Got the same problem. Default pin did not work. Great to find this post to (FINALLY!) being able to get out of the clock app! :-)
Seems kind of a widespread bug that sets the PIN to 0 instead. The release notes should be updated to reflect this (if it is not already). I went from 066->069cb->070 with keeping settings with each update.
-
I just had this happen to me as well hit lock instead of settings and locked my screen. default pin was NOT set to '1234' like everything states, but it was set to '0' like btosch found. Not sure why its not getting set to 1234 like you think it should. If it makes any difference I was running all the beta firmware then upgraded to 70.
-
Got the same problem. Default pin did not work. Great to find this post to (FINALLY!) being able to get out of the clock app! :-)
Seems kind of a widespread bug that sets the PIN to 0 instead. The release notes should be updated to reflect this (if it is not already). I went from 066->069cb->070 with keeping settings with each update.
Thanks! Same issue here.
-
In R070as there's an option to change/disable this from the web UI, although you need to remember what the password is to the web UI to be able to do it. I can't remember where they added it and I'm not in front of an Almond+ right now, so I can't check, but it's there.
-
0 worked for me when I locked the clock screen by accident too. Default on this seems to be 0