Securifi Community Forum

Securifi Products => Almond+ => Topic started by: SecureComp on June 08, 2015, 07:23:12 pm

Title: R80 Feedback / Issues
Post by: SecureComp on June 08, 2015, 07:23:12 pm
R80 Feedback and issues.

Multilevel On/Off - works for some lights, not others. (GE Link A19 good, CREE some problems) See thread below
http://forum.securifi.com/index.php/topic,3393.0.html

First Alert Smoke Detector SMOKE DETECTED Status Incorrect - IOS App
The First Alert ZCombo Smoke Detector reports correct status to web interface, cloud interface and android app. It incorrectly reports SMOKE DETECTED to IOS App. R80, IOS 8.3, 1.5 (1808)

Title: Re: R80 Feedback / Issues
Post by: d.kiran on June 08, 2015, 08:29:13 pm
Looks like the ios app is buggy. I cannot believe that someone published the update without checking. The locks also show an incorrect status.

Also, can the rules now go beyond 11:59 or do we still need a workaround ?
Title: Re: R80 Feedback / Issues
Post by: Ohiomedic on June 08, 2015, 10:31:31 pm
I think they mentioned the next iOS update will fix the first alert.
Title: Re: R80 Feedback / Issues
Post by: BikerBob on June 11, 2015, 08:14:18 am
Just upgraded from R072 to R080 via LCD and experienced no problems... but my setup is pretty basic:
- Gigabit LAN/ Ethernet throughout house.
- 2.4GHz Wi-Fi.  Haven't tried 5GHz... I don't normally use 5GHz due to poor penetration through walls & floors.
- Peanut Plug "On/Off" control via Android App works fine... including proper reporting of Power/Voltage/Current.
- Peanut Plug "On/Off at Time" simple Rules also work ok.
- SmartThings Hub to control some Leviton and Linear Z-wave wall dimmers & switches

I didn't have to re-power or reset anything... not cable modem, not router, not Peanut Plug, not the SmartThings Hub... everything just worked.... so far.

Bob
Title: Re: R80 Feedback / Issues
Post by: rldreams on June 11, 2015, 08:32:43 am
GE and Cree bulbs are still hit/miss reporting across all platforms. Everything else seems to be working as of this morning. Router/ wifi is still hit/miss and getting worse.
Speedtest results: 
Desktop cat6 directly to modem 68 Mbps
Desktop cat6 to A+ 48 Mbps
Phone 75 Mb wifi on 2.4 Ghz to A+ 18Mbps
Phone 433Mb wifi on  5Ghz to A+  22Mbps
All tests performed over about a 2 minute time period ( amount of time it took me to swap cat6 cable or switch wifi network on phone) to the same server.
Title: Re: R80 Feedback / Issues/Kwikset910
Post by: xtbs26 on June 11, 2015, 09:37:29 am
My Kwikset 910 Z wave lock does not report status if the lock is locked/unlocked manually. To see if I could rectify this, I attempted to remove/re-pair the lock. When I brought it up on the Almond LCD, the screen froze. There was also no option there to edit. I had to reboot the Almond to get the screen back. I tried it again, same result. Changed the lock batteries, still the same (and battery status reported "low" on Almond after changing). So I am unable to remove this sensor.
Title: Re: R80 Feedback / Issues
Post by: d.kiran on June 11, 2015, 11:57:33 am
I have a kwikset 910 z-wave . After I removed it and paired it again, it actually works like a charm. The only problem is that the status change takes about 6-8 seconds. I.e. if you click on the lock button, it locks it within 2 seconds, but send the notification that it is locked 6 seconds after that.

What I would suggest, is rather than go to the lock and remove it, go to add sensors on the main page on the LCD, and hit remove. Then press the button the lock. That should unpair it. To be sure, even after it says removed, repeat it one more time and it will say "Unknown Sensor removed".

Now you should be able to add it. I noticed that the lock is very sensitive to distance when pairing. Make sure the almond is within 3ft of the lock.
Title: Re: R80 Feedback / Issues
Post by: xtbs26 on June 11, 2015, 01:15:59 pm
d. kiran - Thank you very much. I was able to get things back up with your instructions and now the status does change with manual use of the lock! Thanks again.
Title: Re: R80 Feedback / Issues
Post by: spooky123 on June 11, 2015, 09:31:44 pm
GD00Z-4 garage door opens and closes via LCD but tilt sensor but opened/closed state is not working correctly or consistently. Also still unsupported in the app.
Title: Re: R80 Feedback / Issues
Post by: Ashok on June 12, 2015, 08:24:04 am
@ spooky123,

We have seen few cases where if the physical setup of the Garage Door sensor is not right, it was not working consistently and on the app we are yet to add the support for that device type.
Title: Re: R80 Feedback / Issues
Post by: spooky123 on June 13, 2015, 10:10:25 am
Ahsok, the sensor is installed correctly and when the Almond+ updates it does have the correct state, but when/how the Almond+ updates status seems inconsistent and unreliable.... seems to need one to trick it into having the right status (ie, if it says closed and the door is actually opened, then click open again on the Almond and status is correct) and then when the lcd is used to open/close it has the right status.... but interject a manual open/close and the Almond+ never updates. It seems like the Almond+ is handling the open/closed status via what was last pressed on the Almond+ rather than the tilt sensors actual state.
Title: Re: R80 Feedback / Issues
Post by: Ashok on June 13, 2015, 11:09:14 am
@ spooky123,

Could you please send the log files by mentioning the issue, so that I could check with my team and get back to you with some inputs.
Title: Re: R80 Feedback / Issues
Post by: cranecj on June 18, 2015, 01:44:15 pm
Updated to R80, and most of my devices won't connect to Wifi.  I tried a factory reset, and I keep having an issue with the assigned IPs.  Devices are getting a 10.10.1.xx IP and I cannot connect to/ping anything - even the Almond+. Somehow after a strange combination of resetting my Almond+ and my laptop, I was able to get a 10.10.10.xx IP and everything worked from that device.  When I updated my Wireless password on the device, I suddenly lost all connectivity with my laptop IP reverting back to 10.10.1.xx.  I have never had any Wifi issues with my Almond before this update.  The issue started as soon as I finished the update.

I tried connecting with several android phones, a Macbook Air 2013, and a Lenovo on Win8.1. 
Title: Re: R80 Feedback / Issues
Post by: Ashok on June 18, 2015, 06:33:49 pm
@ cranecj,

If you have not tried yet, could you please try a factory reset and let us know the status.
Title: Re: R80 Feedback / Issues
Post by: Tam-Lin on June 19, 2015, 09:52:13 am
I'm having a similar problem, with no IP addresses being passed out with R80 in AP mode. 

I'm trying a factory reset (and I'll point out that the earlier person said he did already), but I'm not expecting much.  I've opened a problem, but haven't gotten much assistance.  I'm ordering a different router, at this point.  There are others in my household that need a reliable Internet connection, and right now, the Almond+ isn't delivering that..  The promise of the Almond+ is great, but if it can't handle the basic wireless functionality, everything else is irrelevant.
Title: Re: R80 Feedback / Issues
Post by: cranecj on June 19, 2015, 10:04:26 am
@ cranecj,

If you have not tried yet, could you please try a factory reset and let us know the status.

I tried 2 factory resets and had the same problem. I will try again.
Title: Re: R80 Feedback / Issues
Post by: Ashok on June 19, 2015, 10:40:08 am
@ crancej,

Sorry it was my bad, we could try factory reset only once and as you are still facing the same issue please get in touch with our support team support@securifi.com who can diagnose the issue real time and take care of it for you.

@ Tam-Lin,

Technically, in AP mode DHCP is by default disabled and main router would provide the IP addresses to the client devices which are connected to the Almond+. We have installed R80 to some good number of users and they are not facing any issues with wireless or with IP Address assigning. However, just for the confirmation could you please try setting up the Almond+ in Router mode and then check if client devices are receiving the IP Address. Also let us know what happened after performing a factory reset.
Title: Re: R80 Feedback / Issues
Post by: habeatgenmoint on June 22, 2015, 09:49:45 am
I'm having my share of Wi-Fi problems too, but it seems to have been there since maybe R079. My 5GHz Wi-Fi just somehow silently gets broken.

Also, the Web UI bugs out when I'm trying to save a static lease, which may or may not have caused the Wi-Fi problems. Neither the Almond+ version nor the OpenWRT version worked. I restored to an old configuration and the Wi-Fi issue is gone (for now). Can't be bothered to reproduce that on R080 as this is my friggin home router which shouldn't have had these serious bugs in the first place!  I've had fewer problems with even D-Link and TPLink >:(

Title: Re: R80 Feedback / Issues
Post by: SecureComp on June 22, 2015, 02:33:39 pm
When using the SDK and the HADevices::genericCallback, I often get the message listed below.

I'm guessing this is the whole clean socket close problem and the LCD App binding to the same IP

Code: [Select]
Address already in use: End Client binding failed
This was happening with early firmware releases and is still happening with R80.
Title: Re: R80 Feedback / Issues
Post by: Tam-Lin on June 22, 2015, 05:05:20 pm
Technically, in AP mode DHCP is by default disabled and main router would provide the IP addresses to the client devices which are connected to the Almond+. We have installed R80 to some good number of users and they are not facing any issues with wireless or with IP Address assigning. However, just for the confirmation could you please try setting up the Almond+ in Router mode and then check if client devices are receiving the IP Address. Also let us know what happened after performing a factory reset.

I'm fully aware of that, and that's my point:  I have devices that connect to the network, but that aren't able to get a DHCP request answered, so they never get an IP address assigned.  I don't have this problem with wired devices, and I don't have the problem with other routers.
Title: Re: R80 Feedback / Issues
Post by: Ashok on June 22, 2015, 07:20:42 pm
@ Tam-Lin,

I am yet to check with my team regarding this, however, I have personally got confirmation from two users that a proper factory reset has taken care of this issue. Hence, if you  have not tried it yet then please do try that which may solve the issue for you. And also let us know the status by setting the Almond+ in Router mode.
Title: Re: R80 Feedback / Issues
Post by: d.kiran on June 25, 2015, 10:23:51 am
Has the issue of requiring two rules beyond 11:59 PM been addressed yet? Is that likely to be solved in the future?
Title: Re: R80 Feedback / Issues
Post by: SecureComp on June 25, 2015, 10:50:19 am
Has the issue of requiring two rules beyond 11:59 PM been addressed yet? Is that likely to be solved in the future?

The Rules use Crontab, so yes it can be solved. It will add to the complexity of the Rules App, needing to specify Day/Start time and Day/finish time. But sure it's doable.

Maybe it will be in the next firmware update with Scenes!
Title: Re: R80 Feedback / Issues
Post by: d.kiran on June 25, 2015, 12:28:58 pm
I thought crontab was the reason why we had this issue. AFAIK crontab does not have a way of overnight schedule apart from having two triggers.
Title: Re: R80 Feedback / Issues
Post by: SecureComp on June 25, 2015, 02:19:06 pm
I thought crontab was the reason why we had this issue. AFAIK crontab does not have a way of overnight schedule apart from having two triggers.

Yes and No.

The app can be modified to create multiple crontab entries to accomplish the goal. The user would just see the App side, Start Mon at 9PM, Finish Tuesday at 3PM, you could even gate date specific, though that would be a bit tedious.  There would in fact be multiple crontab entries to accomplish this but the App Rule would be one Rule.

There are of course other ways to solve the problem that involve more server side coding.
Title: Re: R80 Feedback / Issues
Post by: Ashok on June 26, 2015, 09:01:06 am
Has the issue of requiring two rules beyond 11:59 PM been addressed yet? Is that likely to be solved in the future?

We are working on this and soon it would be taken care off.
Title: Re: R80 Feedback / Issues
Post by: czyzczyz on June 27, 2015, 02:01:32 pm
My Almond+, running R072, fails to update via the LCD. I've tried several times over a couple of days.

I'm going to download R80 and install it via the web interface.
Title: Re: R80 Feedback / Issues
Post by: Ashok on June 27, 2015, 05:16:54 pm
@ czyzczyz,

You can try running the Diagnostics app and then try to update it via LCD UI, if that fails try to synchronize the time using Time app that should allow to update the software via LCD UI.
Title: Re: R80 Feedback / Issues
Post by: revoman on June 28, 2015, 10:37:53 pm
Unable to get to the Dynamic DNS page in OpenWRT with R80. 

I did a factory reset once it was installed because my Xbox360 wouldn't connect to the internet.  Settings were added manually instead of from a backup.
Title: Re: R80 Feedback / Issues
Post by: smitch019 on June 28, 2015, 10:46:35 pm
I cannot get my Schlage lock to function using the IOS app any longer.  It seems to time out and say "unable to update sensor."
Title: Re: R80 Feedback / Issues
Post by: revoman on June 28, 2015, 10:54:12 pm
I was able to SSH into the router and modify /etc/config/ddns by adding a 2nd entry, now the webpage configuration works.

Unable to get to the Dynamic DNS page in OpenWRT with R80. 

I did a factory reset once it was installed because my Xbox360 wouldn't connect to the internet.  Settings were added manually instead of from a backup.
Title: Re: R80 Feedback / Issues
Post by: Jacq on July 04, 2015, 09:16:18 am
Hi. This is a great product and I really enjoy it.

I have been having trouble with:

Kwikset 909/910 doesn't update locked/unlocked status when manually set
AEON Multisensor DSB05: Not supported
2.3 Ghz WiFi: suddenly dropping connection on several devices
5.0 Ghz WiFi: extremely weak. Can't connect from one room to another
FTP/SAMBA: no support for international characters (, , , etc.)

JCanal
Title: Re: R80 Feedback / Issues
Post by: SecureComp on July 04, 2015, 11:26:09 am
Check your 5Ghz and 2.4Ghz settings. Perhaps adjusting the bandwidth will help. I am getting good range with the R80, could be better but certainly works from room to room and more.
Title: Re: R80 Feedback / Issues
Post by: Ohiomedic on July 04, 2015, 12:02:07 pm
I haven't had any drops or weak signal on wifi on R80. Might also try changing the wifi channels if you have others near you that also have wifi.
Title: Re: R80 Feedback / Issues
Post by: nVidia on July 07, 2015, 02:43:32 am
having trouble with the almond+ working with the fibaro FGSD-002 EU and Aeon Labs Multisensor Gen 5 ZW074-C

help!
Title: Re: R80 Feedback / Issues
Post by: Jacq on July 07, 2015, 07:11:17 am
I haven't had any drops or weak signal on wifi on R80. Might also try changing the wifi channels if you have others near you that also have wifi.

Ha, that actually did work! I just set the channel to AUTO and haven't had a dropping issue in days.

Any clue on international character support for the SAMBA server?

Thank you Ohiomedic!
Title: Re: R80 Feedback / Issues
Post by: TheLostSwede on July 08, 2015, 06:19:12 am
The Samba server should have full extended character support.
Title: Re: R80 Feedback / Issues
Post by: Ashok on July 08, 2015, 10:00:48 am
@ nVidia,

Let us know what exactly is the issue you with those sensors and if possible send logs by mentioning the description. So that I could check and get back to you with a proper update/solution.
Title: Re: R80 Feedback / Issues
Post by: nVidia on July 08, 2015, 01:04:39 pm
hi ashok,

had previously fedback to Zafar and sent 2 logs via almond+ tagged to case #271317

no resolution to date

cheers
Title: Re: R80 Feedback / Issues
Post by: Ashok on July 08, 2015, 03:08:32 pm
@ nVidia,

Thank you for the clarification and yes as per the case details, it seems like our team is still working on adding the support.
Title: Re: R80 Feedback / Issues
Post by: nVidia on July 08, 2015, 08:36:45 pm
hi ashok,

alrighty thanks

another issue i have with the almond+ on R80 is difficulty connecting to it (sensors and router) via the android app (through internet), mostly in the morning and some evenings

the message "could not retrieve wireless data" will show even though the almond+ in extender mode is connected to the internet and "everything is okay"

what could be the problem?

Sometimes, there is also a 10 minute lag updating the status of the sensors, it isn't instantaneous

it's like the almond+ needs to "Wake up" every morning or evening to be working properly

cheers



Title: Re: R80 Feedback / Issues
Post by: Ashok on July 08, 2015, 09:15:59 pm
@ nVidia,

As long as Almond+ is connected to the internet, it should be instantaneous. Try to access the sensors from LCD UI and Web UI and check how the response time is. Also try to check the internet connection with Almond+ properly to see if it is working at all the time.
Title: Re: R80 Feedback / Issues
Post by: obmd1 on July 08, 2015, 11:42:00 pm
when can we expect a firmware update that addresses the issues with R80?
Title: Re: R80 Feedback / Issues
Post by: rf134a on July 09, 2015, 12:56:08 am
The routing performance seems to be a little slower. A 2.76GB file averages 27.4MB/s.

The iOS app doesn't show my sensors. The android app shows both sensors, my HEM v2 as unknown and my Everspring ST12. Unfortunately, the android app doesn't seem to be able to schedule anything. Reading the logs on the android app only works 10% of the time. It keeps on showing "cloud server offline". The A+ web rules interface is useless. All it does is switch the router from home to away mode. What's the point of that?

Peer to peer performance is severely lacking. Once connections hits 500, the router loses the ability to do any kind of DNS lookup. This causes all other devices to fail to connect. My Asus RT-N66U could handle 10,000+ connections without any issues.
Title: Re: R80 Feedback / Issues
Post by: spooky123 on July 09, 2015, 08:05:23 am
Ashok, sorry for the delay. I uploaded logs called Linear Garage.

Example from this morning with the Linear Garage and the new Android app.....

Apps says door is closed, LCD says door is closed. Door is closed.

I use the App to open door and door and lcd report door as "opening", The door opens but the status never updates.

With the App and lcd in status of "opening", I "close" the door then both app and lcd say status is "open" but the door is closed.

It seems like the sensor isn't polling and it is determining status by last action via the almond. For example, if almond reports the door is either open/closed and I manually open/close the door then the almond status never changes until I use the almond to actuate but then status is out of sync.
Title: Re: R80 Feedback / Issues
Post by: Ashok on July 09, 2015, 10:50:19 am
@ spooky123,

We received the log files, let me work on it and get back to you.
Title: Re: R80 Feedback / Issues
Post by: Ashok on July 10, 2015, 08:14:15 am
@ spooky123,

I just worked on the Garage Door Sensor and it is working fine through LCD and Andriod App. However, even we faced the same issue like yours when the tilt sensor was connected opposite. Hence, could you please recheck if the tilt sensor is connected properly and also verify the performance only through LCD UI first and then check with Andriod app.
Title: Re: R80 Feedback / Issues
Post by: spooky123 on July 10, 2015, 12:29:29 pm
Arrow on plate and sensor both pointing up and mounted on top panel of door as indicated in instructions.
Title: Re: R80 Feedback / Issues
Post by: nVidia on July 12, 2015, 11:40:14 am
Hi Ashok,

I have an issue with the Fibaro FGMS-001

Almond+ recognizes it as a multi-sensor with lux, temperature and motion sensors and shows on the LCD correctly

However, the android app is unable to support the temperature and lux readings

Please advise

Cheers
Title: Re: R80 Feedback / Issues
Post by: Ashok on July 13, 2015, 08:01:00 am
@ spooky123,

The tilt sensor arrow if it is slanting back horizontally that means it is open and if the arrow is pointing up vertically then it is closed. May be it would be more helpful to understand if you could send at least 1-2 pictures on how the setup is. Thank you!
Title: Re: R80 Feedback / Issues
Post by: Ashok on July 13, 2015, 08:08:02 am
@ nVidia,

We have not added support for Fibaro FGMS-001 on Apps (Andriod or iOS).
Title: Re: R80 Feedback / Issues
Post by: nVidia on July 13, 2015, 10:30:06 am
alrighty thanks

hope you guys patch support for FGMS-001 in the next firmware update

hopefully too, almond+ will be updated to allow us to create rules with the Fibaro FGSS-001 smoke sensor

cheers
Title: Re: R80 Feedback / Issues
Post by: spooky123 on July 14, 2015, 04:53:53 pm
Ashok, it is installed exactly like page 4 of this....

https://www.adt.com/content/dam/adt/downloads/manuals/GDC-Installation-Instructions-EN-Final.pdf

Title: Re: R80 Feedback / Issues
Post by: spooky123 on July 14, 2015, 05:08:07 pm
Ashok, Here are some details that hopefully helps you. This repeatable.

Using LCD after manually getting garage door and Almond to show same status...

Actual status of door: Closed
Status reported on LCD: Closed
Action taken: Opened door from LCD
Action response: Door opens
Actual status of door: Opened
Status reported on LCD: Closed
Action taken: Actuate door from LCD
Action response: Door closes
Actual status of door: Closed
Status reported on LCD: Opened

After getting the door/LCD back in sync by manually changing the door....
Note that when I manually actuate the door - regardless of the status reported on the LCD - the LCD status NEVER updates.

Actual status of door: Closed
Status reported in app: Closed
Action taken: Opened door from app
Action Response: Door opens, App says Opening, APP FLASHES MESSAGE CANNOT UPDATE STATUS
Actual status of door: Opened
Status reported in app: OPENING
Action taken: Actuate door from app
Action response: Door closes, App says Open, APP FLASHES MESSAGE CANNOT UPDATE STATUS
Actual status of door: Closed
Status reported in App: Open

Again note, that if I manually open or close the garage door.... neither the LCD nor the APP ever changes status.


Title: Re: R80 Feedback / Issues
Post by: Ashok on July 15, 2015, 09:25:38 am
@ spooky123,

We are still suspecting that the issue could be related to the setup. However, is it possible for you get in touch with our support team at (support@securifi.com), who could assist you on this.
Title: Re: R80 Feedback / Issues
Post by: smitch019 on July 15, 2015, 11:57:25 am
@Spooky123 My LCD does the same thing.  ALWAYS states the door is closed even after I open it from the LCD.
Title: Re: R80 Feedback / Issues
Post by: nVidia on July 15, 2015, 10:02:15 pm
Hi Ashok,

Please advise how we are able to extract notification logs/ sensor history from the almond+

These data is important to us for record

Appreciate your early reply

cheers
Title: Re: R80 Feedback / Issues
Post by: dmwyatt on July 17, 2015, 10:14:58 am
Is there a release date for the next version of firmware?
Title: Re: R80 Feedback / Issues
Post by: Ashok on July 17, 2015, 10:22:37 am
@ dmwyatt,

We are still working on the next release and no ETA yet from our team.
Title: Re: R80 Feedback / Issues
Post by: Fire69 on July 17, 2015, 02:10:36 pm
Do you have any idea if there will be some major improvements? Or will it just be device updates and bug fixes?
Title: Re: R80 Feedback / Issues
Post by: Ashok on July 17, 2015, 10:03:55 pm
@ Fire69,

I am sorry, there is no information yet about what major improvements would be coming up with the next release. To my best knowledge, it depends upon the outcome of testing, only then I would get a confirmation. Hence, I can't provide much information for now. Meanwhile, the moment I receive any new update would be happy to post it.
Title: Re: R80 Feedback / Issues
Post by: mr23 on July 18, 2015, 01:00:05 pm
@ Fire69,

I am sorry, there is no information yet about what major improvements would be coming up with the next release. To my best knowledge, it depends upon the outcome of testing, only then I would get a confirmation. Hence, I can't provide much information for now. Meanwhile, the moment I receive any new update would be happy to post it.

Is there some reason Securifi can't share a roadmap with Backers ? Do you need to set up a section of the forum only Backers can see?
I doubt anyone would be crass enough to complain about *what* you've chosen to work on, but it would be great to see the planned feature list, the yet to be added device list, the bug list, and the current sprints/iterations/whatever.

That would be in the spirit of Kickstarter, too.
Thanks,
-Chris
Title: Re: R80 Feedback / Issues
Post by: Fire69 on July 18, 2015, 05:16:09 pm
They don't have a road map. Support doesn't know what the development team is doing and vice versa.
Title: Re: R80 Feedback / Issues
Post by: nVidia on July 19, 2015, 12:27:44 am
Hi Ashok,

any updates on this?

Hi Ashok,

Please advise how we are able to extract notification logs/ sensor history from the almond+

These data is important to us for record

Appreciate your early reply

cheers
Title: Re: R80 Feedback / Issues
Post by: Ashok on July 20, 2015, 07:53:37 am
@ nVidia,

In the latest Andriod app, we can tap on any one of the sensor and hit view logs which would have the complete history from the day it joined to the Almond+ and cloud.

On the other hand, we can pull up the logs from tmp directory, however, it won't be specific to one sensor and there won't be any particular stage all the communication between the sensors and Almond+ would be stored.
Title: Re: R80 Feedback / Issues
Post by: spooky123 on July 22, 2015, 07:21:20 am
@Ashok., the Linear garage door opener works flawlessly with the SmartThings hub.... open/close status update is dead on and updates correctly with it.
Title: Re: R80 Feedback / Issues
Post by: hkmax721 on July 22, 2015, 10:35:13 am
Updated to R80, and most of my devices won't connect to Wifi.  I tried a factory reset, and I keep having an issue with the assigned IPs.  Devices are getting a 10.10.1.xx IP and I cannot connect to/ping anything - even the Almond+. Somehow after a strange combination of resetting my Almond+ and my laptop, I was able to get a 10.10.10.xx IP and everything worked from that device.  When I updated my Wireless password on the device, I suddenly lost all connectivity with my laptop IP reverting back to 10.10.1.xx.  I have never had any Wifi issues with my Almond before this update.  The issue started as soon as I finished the update.

I tried connecting with several android phones, a Macbook Air 2013, and a Lenovo on Win8.1.

Same issue happen to me as well. It was worked for a while after updated to R80. Then suddenly happen tonight. Two of my desktop cannot obtain IP address via DHCP. None of the wireless devices can connect to the router. The NAS, only device with static IP address, cannot see in Web interface either. Tried reboot, reset, almost everything i can try, but no luck. Please address this issue and release the new firmware to fix this problem. So annoying, and it makes the Almond+ useless. It's not a router any more!! Q :'(
Title: Re: R80 Feedback / Issues
Post by: Ashok on July 22, 2015, 03:12:09 pm
@ hkmax721,

We are already working with one user on this, and please note that this happened even with old firmware, its not specific to R080. It would be helpful if you could reach our support team at (support@securifi.com) when this is happening.
Title: Re: R80 Feedback / Issues
Post by: nVidia on August 03, 2015, 10:40:07 pm
Hi Ashok,

I tried to add \\10.10.10.254\tmp as a network location to gain access to the tmp logs in almond+ but it doesnt work

the error message kept prompting the folder doesnt appear to be valid and that's an error

i see /tmp as a mount point under Mount Points -> Mounted File System but somehow i am unable to access and add it as a network location

is there any other way i can pull the data out directly from almond+ via USB or RJ45  etc?

the app doesnt allow us to export sensor history to an email so there is no point one can see the notifications/ logs on the app but cant export nor analyse the data

@ nVidia,

In the latest Andriod app, we can tap on any one of the sensor and hit view logs which would have the complete history from the day it joined to the Almond+ and cloud.

On the other hand, we can pull up the logs from tmp directory, however, it won't be specific to one sensor and there won't be any particular stage all the communication between the sensors and Almond+ would be stored.
Title: Re: R80 Feedback / Issues
Post by: sergio91pt on August 06, 2015, 06:21:47 am
What dropbear (sshd) version does R80 have? I think I'm still using R72, which has 0.52 (from 2008).
0.52 has 2 known vulns CVE-2012-0920 (allows to bypass command restrictions - remote execution) and CVE-2013-4421 (DOS) that are specially relevant when using ssh as a socks proxy.
Title: Re: R80 Feedback / Issues
Post by: nVidia on August 10, 2015, 10:40:28 am
Hi ashok,

please advise

alternatively, can we pull the sensor history via USB to the almond+?

Hi Ashok,

I tried to add \\10.10.10.254\tmp as a network location to gain access to the tmp logs in almond+ but it doesnt work

the error message kept prompting the folder doesnt appear to be valid and that's an error

i see /tmp as a mount point under Mount Points -> Mounted File System but somehow i am unable to access and add it as a network location

is there any other way i can pull the data out directly from almond+ via USB or RJ45  etc?

the app doesnt allow us to export sensor history to an email so there is no point one can see the notifications/ logs on the app but cant export nor analyse the data
Title: Re: R80 Feedback / Issues
Post by: apu2009 on August 11, 2015, 01:49:06 am
Has VPN access with IPSec and PSK been fixed? I tried setting it up back in R69 and it wasn't working. I've upgraded to R80 and it's still not working. I'm not sure if there's anything else that needs to be done other than configure a user/pass along with the PSK
Title: Re: R80 Feedback / Issues - Can't remove forwarding entry
Post by: czyzczyz on August 20, 2015, 11:38:30 pm
I've got a port forwarding route I'd like to remove.

I go to the "Firewall - Port Forwards" page in the Almond+ interface (not the openwrt interface), and hit the delete button to the right of the entry I'd like to remove.

The next page loads a little slowly, and it's an error page (screenshot at link):
http://drif.tt/1JlQ72U

I'm running R80 firmware.

Anyone else run into this problem?
Title: Re: R80 Feedback / Issues
Post by: johnyeros on August 21, 2015, 10:24:38 am
I  pretty much feel the same way. I have spent countless hours on the phone but at the end of a day, 1 year into it this router Wifi is Weak as bunny. I just recently got the new speed bump from ISP to 200 Mbps, but the most of my wireless device is still suffering and I'm tired of tweeaking and upgrading. Almost about to call it a day and buying a new Asus Router. By the time this product release it was at best an AC1300 router. Hardware is out of day and software / automation support is lacking.
Title: Re: R80 Feedback / Issues
Post by: Ashok on August 21, 2015, 10:27:22 am
@ nVidia,

You may have to login to the console and then use the TFTP software to pull the history and if you could get in touch with our support team, we can assist you properly.
Title: Re: R80 Feedback / Issues
Post by: Ashok on August 21, 2015, 10:29:22 am
@ Johnyeros,

Try to reach our support team at (support@securifi.com) would ensure to get this taken care as high priority for you.