Securifi Community Forum
Securifi Products => Almond+ => Topic started by: techrecoded on January 07, 2015, 11:26:49 pm
-
Hi,
I updated the firmware and had a slew of issues immediately with wifi. I found that after reboot DHCP was issuing duplicate ips or failing to allow devices to connect and the System Log show conflicting ips causing all devices on the network not to have external/internet connectivity. Logs as follows:
Jan 8 04:57:26 AlmondPlus daemon.crit dnsmasq[8425]: failed to bind DHCP server socket: Address already in use
Jan 8 04:57:26 AlmondPlus daemon.crit dnsmasq[8425]: FAILED to start up
I was able to get external/internet connectivity but onyl after a complete shutdown, 2 reboots left me with the same issue. I also seem to notice that wifi signal seems weaker.
As to the automation my zigbee light bulbs don't respond to any setting. I tried setting them to turn on if off at a specific time and then off if on at a specific time without any success. Additionally I noticed that if I tried to configure an if "between" config the time is never stored on the the "if" section only the device fucntion or state is stored rendering the fucntion useless.
I even tried to state if at 00:00 or any time a certain lights state is in on/true state to turn on another light no luck there either.
Lastly, time does not sync to my local time zone, had to manually set the clock.
The weather app only sits on "Getting Local Weather. Please Wait" for long period of time followed by "Unable to get Location Data! Please try later." with the following logs:
Jan 8 04:30:26 AlmondPlus user.info sysinit: --2015-01-08 04:30:26-- (try: 6) http://ec2-54-166-64-119.compute-1.amazonaws.com:8888/forecast/autoip.json
Jan 8 04:30:26 AlmondPlus user.info sysinit: Connecting to ec2-54-166-64-119.compute-1.amazonaws.com|54.166.64.119|:8888... connected.
Jan 8 04:30:27 AlmondPlus user.info sysinit: HTTP request sent, awaiting response... Read error (Connection timed out) in headers.
Jan 8 04:30:27 AlmondPlus user.info sysinit: Retrying.
Jan 8 04:30:32 AlmondPlus user.info sysinit: The source address 10.10.10.105 for group 239.255.255.250, is not in any valid net for upstream VIF.
Jan 8 04:30:33 AlmondPlus user.info sysinit: --2015-01-08 04:30:33-- (try: 7) http://ec2-54-166-64-119.compute-1.amazonaws.com:8888/forecast/autoip.json
Jan 8 04:30:33 AlmondPlus user.info sysinit: Connecting to ec2-54-166-64-119.compute-1.amazonaws.com|54.166.64.119|:8888... connected.
Jan 8 04:30:34 AlmondPlus user.info sysinit: HTTP request sent, awaiting response... Read error (Connection timed out) in headers.
Jan 8 04:30:34 AlmondPlus user.info sysinit: Retrying.
I keep seeing the following message from multiple ips "Jan 8 04:19:24 AlmondPlus user.info sysinit: The source address 10.10.10.187 for group 239.255.255.250, is not in any valid net for upstream VIF." in the logs as well.
Effectively from a zigbee lightbulb no luck with any automation. Things seem to perform weird if any rules are present and seem to operate closer to normal if none are present. I hope you can get this working fast.....I was super excited about this firmare but now need to know if I can downgrade it?
Thanks
-
Yes, you can roll back just fine.
I dunno about your weird networking issues, but the bulbs aren't working properly yet. It's possible to turn them off, but not on.
As mentioned, the automation has limited support and this is a beta build, so things are a bit buggy.
-
I have similar results and log messages after upgrading (to R069cb), but signal strengths are the same as before the upgrade. The WAN connection remains connected, but I periodically can't hit any outside addresses and the web UI starts missing pieces (says there are no sensors or rules, sometimes will not load at all). Resetting power is the only fix I've found so far.
A simple rule to turn the peanut plug on and off results in the on/off being repeated a number of times. I'm not sure if creating rules or running rules are causing the issues. We'll see tomorrow as they're all deleted at this point.
Thanks
-
I turned on the 2.4ghz radio this evening for the first time in a while (I have the Almond+ in bridged mode and just use it for automation/sensor control, connected to my apple time machine on 5.8ghz), after installing the R069bc and it locked up the router. As in, the screen went blank and the router functions stopped responding over the local address and through connect.securifi.com. The automation still functioned though through both previously mentioned routes as well as through the IOS app. I had to pull the power to get it to come back to life. Possible bug problem.
Thanks for your help Lars, it is is always much appreciated.
-
This is a current limitation when you're upgrading the firmware, both of the Wi-Fi radios need to be enabled when this is done or the Almond+ will throw a hissy fit.
-
Can't change name of sensors or their description from Web-UI, it works from iOS app. Tried both Firefox and Safari on OS X Yosemite.
-
Vision Door/Window sensor still highly unreliable, it works for few open-close cycles but soon the status changes are not displayed on the Almond+.
-
Vision Door/Window sensor still highly unreliable, it works for few open-close cycles but soon the status changes are not displayed on the Almond+.
Odd, not something I've seen internally since they fixed it and we've done a fair bit of testing to make sure they work properly. Did you remove and re-add the sensor?
-
I'm not sure if creating rules or running rules are causing the issues. We'll see tomorrow as they're all deleted at this point.
I haven't been fiddling with any rules today and wifi has been solid for both 2.4 and 5GHz networks. I'll do further testing later today.
-
after installing the beta I experienced that the almond freezes after 20-30 seconds, the display and the web-interface was not responding. also the reset button seemed to do nthing at all. wifi connections appeared to stay available though, but i'm not quite sure about that.
after 3 power cycles the almond stayed up and running for a while now.
was looking forward to test the rules but apparently i have only 1 zwave dimmer that can be used and at the moment. It stopped working a few days back (unrelated, I might have accidentally triggered the pairing mode). so I cant do anything with the rules yet.
the time app showed the wrong time, when I tried to synchronize it said no internet connection (perhaps looking for the WAN link and not wifi?). After dismissing the popup the lcd screen went entirely black, but when touching the screen, interface elements show up again.
-
Odd, not something I've seen internally since they fixed it and we've done a fair bit of testing to make sure they work properly. Did you remove and re-add the sensor?
Yes, a couple of times, it seem like status quo from last firmware. It works for a couple of open/closed cycles then the almond+ stops showing state-changes, despite the red led showing that it sends a state change. Have tried it on a door 2 m from Almon+ so range should not be an issue.
-
Not an issue as such but, a potential pitfall that you should think about...
If you have a rule X that says that binary switch A should be off IF time is between midnight and seven in the morning. If you then try to override that using your iOS app, then it will immediately turn on and then off again essentially you will wrestle and lose against the rule. Tried this yesterday it was mildly amusing.
My opinion is that it a manual input shouldoverride the rule for a globally settable time. A default of 30 minutes might be appropriate.
-
...
My opinion is that it a manual input shouldoverride the rule for a globally settable time. A default of 30 minutes might be appropriate.
thats definitely something to take in account, scenarios like this illustrate the battle betweeen automation and controls. Somewhere between those variables lies a golden cut that defines comfort :D
I think in this case you should be able to use an AT timing for your desired automated state whilst you are using an BETWEEEN timing rule at the moment
-
hello
is it normal in home automation option it shows all my sensors in "IF" section but nothing in my "THEN" section ..and it did not shows also my Zwave everspring 812 sirene..
thanks
-
Linear in-wall dimmers are now working from all the UI's (WebUI, LCD UI, and Android app) The dimming function does seem a little buggy though. You go to set the level of dimming and it sometimes takes multiple tries to get it to stay at your set level. To clarify, you turn it on and it goes to 99% according to the UI (never to 100%) and then when you want to set a dimming level you tap or drag the slider to what you want for this example I tried around 20%. Then it will do 1 of 3 things, dim the light to that setting and then move back to 99%, dim the light to that setting and move to another setting say 60%, or maybe you'll get lucky and it will actually dim to 20%. Oh another thing it could do is bounce back and forth between 20% 60% and 99% then coming to rest on one of them, randomly it seems.
I don't see this as too much of an issue when wanting to set it manually but when it comes to rules and scenes (when they come out) it could be an issue if you wanted to set a certain dim level and it doesn't go to the preset.
-
hello
is it normal in home automation option it shows all my sensors in "IF" section but nothing in my "THEN" section ..and it did not shows also my Zwave everspring 812 sirene..
thanks
As stated not all sensors are supported at this time, more will be in the next update hopefully coming next week.
-
Great Work! Nice to finally see some automation features.
A few items of note with initial playing (Some may have already been covered). Using PIRs, Window/Door Senor and Key Fob purchased with the Almond+ and an Aeotec inline dimmer.
1. Sensors did not show on web interface after update, required restart of router, software request for the router to reboot resulted in a hang, had to physically pull the power.
2. When setting Between times, both times must be on the same day ( I can't set a light to come on between 7PM and 6AM it returns Īnvalid Time, 6AM to 7PM is vaild).
3. At the moment it appears that the rule is being run everytime the trigger is true, without terminating the already running instance of the rule.
I have a PIR and a Light. When there is moment I turn on the light, wait for 180 seconds, then turn the light off. At the moment when I walk into the room the light will turn on (good) if there is only 1 trigger this is good, if I stop moving, then move again the rule is triggered again, turning on the light (which is already on) then the first timer ticks over and turns the light off, then the motion turns the light on again. which is about when the 2nd rules timer turns the light off again etc... My desk lamp has been flashing at me for the past 5 minutes :?
Suggestions
1. It would be nice (as mentioned by another user) to prioritize rules, so a light staying on for security reasons will always stay on if its triggered by the door switch. regardless if somebody has triggered a PIR for which the same lamp is used as a convenience/safety lamp.
Keep up the great work,
Shane
-
Massive thanks for all the very helpful feedback.
I've passed it all on to the software team to have a look at, since I'm still at CES for another 30h or so and then I got a rather long flight back to Taiwan until I can really help with any of this.
It's all really useful stuff and the software team has clearly made some interesting assumptions about how the rules should or shouldn't work. A few of you really made me laugh at the oddities you were seeing ;D
-
I too had the automation fight. It was with my front door lock. As soon as I finished punching in the unlock code, the almond would re lock the door. I had to pull out my key to get in. So I deleted the rules, only to find out the rule didn't really go away until I finally rebooted the almond.
-
I haven't been fiddling with any rules today and wifi has been solid for both 2.4 and 5GHz networks. I'll do further testing later today.
Both wireless networks have been fine, but http://10.10.10.254/cgi-bin/luci stopped loading. Trying a reboot from the touchscreen just hung. Had to pull the plug.
-
Upgrade has caused these issues, some of which were mentioned earlier:
1. Time does not sync.
2. Weather hangs up trying to retrieve and never does, causing a lock up.
3. Can no longer access cloud: "Unable to connect to HTTPS."
4. I think this is related to 3, I can no longer access share drive.
Elliott
-
Yes, a couple of times, it seem like status quo from last firmware. It works for a couple of open/closed cycles then the almond+ stops showing state-changes, despite the red led showing that it sends a state change. Have tried it on a door 2 m from Almon+ so range should not be an issue.
Mike - I have this same issue but slightly different - I installed R069bc several days ago and made no changes to configuration outside what was already set in R066.
Same thing - when the almond reboots it comes on for 30 seconds or so and then freezes and you can't get back into.
I was playing with the rules for Port Forwarding trying to configure a static IP for my PC and open ports for my Plex.
Since saving the config, that is when these problems started.
One other thing is that for some reason on reboot - the Almond + by default is trying to force 192.168.1.1 which I never put into it. I assume its pulling it from somewhere else as I used to have a Netgear. I can clear this by going through the wizard again where it picks up the proper IPs both from Comcast and assigns the 10.10.x.x for my home network but am confused why it did it.
AT present - I cannot use the almond+ unless I can edit the config or roll back the software.
I will try to direct connect and see if i can do this. I also could not get the reset button on the top to do anything!?
Is there an option for factory reset or default reset available?
-
You have to press and hold the rest button for 10 seconds before the Almond+ will reset.
-
The Rules tab is completely messed up and useless in Firefox on my Windows 7 box, but OK in Internet Explorer.
I got locked out of the WebUI (totally unresponsive), which a reboot fixed (for now). If it happens again I'll revert the firmware while I have a chance -- wouldn't want to get completely locked out and be unable to update the firmware in the future!
As for the automation: the keyfob works: I set the "arm all" to turn out all my lights and lock my door, and it did, which was great. (BTW - locking the door works now, which it did not before). Everything else SEEMS OK so far (SMB access to the USB drive, DLNA, VPN all work)
-
(this may double post since I got logged out when trying to submit...)
Couple things of note with the new firmware:
Time syncs via NTP, but there is no option to set the timezone, so time is displayed in GMT.
Weather app times out.
If you have screen lock enabled and the time is being displayed, when you tap the screen to close the clock, the screen does not prompt for the unlock code. The default screen lock timeout should still be in effect (even though the clock is visible).
-
(this may double post since I got logged out when trying to submit...)
Couple things of note with the new firmware:
Time syncs via NTP, but there is no option to set the timezone, so time is displayed in GMT.
Weather app times out.
If you have screen lock enabled and the time is being displayed, when you tap the screen to close the clock, the screen does not prompt for the unlock code. The default screen lock timeout should still be in effect (even though the clock is visible).
Time and the weather app are very much in beta, I think some one stated this is the first build they have been in. You can set your time zone by using openwrt.
The Rules tab is completely messed up and useless in Firefox on my Windows 7 box, but OK in Internet Explorer.
I got locked out of the WebUI (totally unresponsive), which a reboot fixed (for now). If it happens again I'll revert the firmware while I have a chance -- wouldn't want to get completely locked out and be unable to update the firmware in the future!
As for the automation: the keyfob works: I set the "arm all" to turn out all my lights and lock my door, and it did, which was great. (BTW - locking the door works now, which it did not before). Everything else SEEMS OK so far (SMB access to the USB drive, DLNA, VPN all work)
I had the same problem, seems to be a file caching problem. Deleting browsing cache or after a few forced refreshes it fixed it for me.
-
I had the same problem, seems to be a file caching problem. Deleting browsing cache or after a few forced refreshes it fixed it for me.
Yes, you are right -- after I did a forced refresh this morning the rules UI in Firefox looked just fine. Should have thought of that myself -- thanks for the tip.
-
GE Link bulb - turns off with rules no problem, cannot turn on with rules. (Tried using Arm-All to either set state to on, set dimmer to 70, 99, etc., set both. No changes). Same with time-based rules.
Keyfob (from Securifi kickstarter) - States reported on "sensor status" do not match available rule states. For instance "Arm Perimiter is a state in sensors, but not available in rules.
Wishlist:
Edit rules.
Manually trigger rules.
Fade-on or fade-off feature without manually entering multiple levels and timers.
-
I'd love a fade-on feature. My current wake-up rule looks like this:
Triggers
At 5 hrs 25 mins On Mon.Wed.Fri.
Actions
Wait for 0 Sec, do Light --- 01
Wait for 0 Sec, do Light --- true
Wait for 60 Sec, do Light --- 25
Wait for 60 Sec, do Light --- 50
Wait for 60 Sec, do Light --- 75
Wait for 60 Sec, do Light --- 99
Wait for 0 Sec, do Light --- true
-
I've passed this on to the software team.
-
GE Link bulb - turns off with rules no problem, cannot turn on with rules. (Tried using Arm-All to either set state to on, set dimmer to 70, 99, etc., set both. No changes). Same with time-based rules.
Keyfob (from Securifi kickstarter) - States reported on "sensor status" do not match available rule states. For instance "Arm Perimiter is a state in sensors, but not available in rules.
Wishlist:
Edit rules.
Manually trigger rules.
Fade-on or fade-off feature without manually entering multiple levels and timers.
Yes, "Edit Rules" and "Fade-on and Fade-off" are expected to come soon. Coming to "Manually trigger rules", it is whole together a separate implementation called scenes. They are also expected to come soon.
-
I set up a rule that when my front door is unlocked, the lamps on the front porch and foyer come on. They do come on but it took about 10 seconds to do so - it would be nice if that was a bit faster.
The biggest issues is that the rule only works when I unlock from a browser or my iOS app. If I unlock from the keypad on the lock, the rule does not work. I am not sure if this is by design, but it would be nice if it did work. I anticipate wanting to turn off the alarm when someone unlocks the door and the two seem so similar.
-
Which bulbs/switches are you using? Never seen that kind of a delay. I presume you didn't add a delay inbetween?
I'm honestly not sure if we can detect when the door is unlocked via the keypad, it might be a lock limitation, but I'd have to check.
-
I used a stopwatch and the process takes just over seven seconds. When I hit the unlock button, it takes about 4.75 seconds for the sensor data to update and the lock to cycle, then another 2.5 seconds for the light to come on. The lock is a Schlage FE599NX and the switch is a GE/Jasco 45609. There are no delays programmed in between.
-
Well, the lock is mechanical, so I can't do anything about that, it's only as fast as the manufacturer has made it.
That said, 2.5 second delay seems long to switch on lights, considering doing it manually has a lag of between 0.5-1.5 seconds with normal lag being around 0.8-1 second for me in Taiwan. Admittedly I haven't tried the specific delay with that switch, but Z-Wave tends to have a slightly longer delay compared to ZigBee in my experience.
That said, the rules is still in very early Beta in this build, so expect things to improve and I'll talk to the software team to see if we can do something like when the lock is initiated, then the next thing should happen, rather than after the lock has already been unlocked.
-
Regarding running rules when unlocking from the keypad: Other HA systems have the option to send a notification that indicates which person unlocked the door. This can let you know when a child comes home as opposed to a spouse, etc. I assume this is done by the lock code, but may well be wrong.
-
It should be, yes and it's something we should be able to do down the road.
-
I seem to be able to get the 5Ghz Radio to reliably crash out and need a reboot to come back.
I have a device on an Intel-AC NIC and if it starts sending a large file over SMB it will crash the radio out after a few minutes. The device it's sending to is a Drobo 5N going through a gigabit switch connected to the Almond+
This may be the same for the 2.4Gig radio as well but the Intel-AC NIC in question is particularly awful on that band so I don't use it at all.
What sort of logs would you like for this?
-
[...]
3. At the moment it appears that the rule is being run everytime the trigger is true, without terminating the already running instance of the rule.
I have a PIR and a Light. When there is moment I turn on the light, wait for 180 seconds, then turn the light off. At the moment when I walk into the room the light will turn on (good) if there is only 1 trigger this is good, if I stop moving, then move again the rule is triggered again, turning on the light (which is already on) then the first timer ticks over and turns the light off, then the motion turns the light on again. which is about when the 2nd rules timer turns the light off again etc... My desk lamp has been flashing at me for the past 5 minutes :?
[...]
Thanks to Lars, I finally got my Hue-lights working and the first thing I wanted to do was get the light in my bathroom on a PIR sensor (my kids always forget to turn of the lights >:( ).
I ran into the same problem...
I made two rules:
- If motion, light on
- If no motion, wait 120sec, light off
The problem is, the sensor that Securifi supplied has (in my opinion) some strange behaviour.
When it detects motion, the led turns on and it sends a 'Motion' signal. Then the led turns off again, and it immediately sends a 'No motion' signal.
The result of this is, as shstevenson explained, that even if there is still motion, the light goes off after 120sec and it immediately turns on again.
What happens next depends on how the detection time for the PIR is set. For example, if it detects motion every 30sec, the light goes on and off every 30 sec.
Quite annoying and pretty much unusable ;)
Should I use another rule to turn off the light, or is this something that the software team has to fix? :)
-
I noticed a similar issue. Different sensors though. I think it is a rule limitation. I am going to have different rules. One for if motion turn on. A second for if no motion, wait x minutes then turn off.
-
Any one of you tried adjusting the sensitivity and time lag knobs over the Securifi Motion sensor?
-
Any one of you tried adjusting the sensitivity and time lag knobs over the Securifi Motion sensor?
Yep. Sensitivity doesn't really do anything about this problem.
Time lag however does. That's what I meant with:
"What happens next depends on how the detection time for the PIR is set. For example, if it detects motion every 30sec, the light goes on and off every 30 sec."
If you set the time lag at 5sec, your light will start going on and off every 5sec as long as motion is detected.
If you set it at 1min, the loop start at 1min.
You get the idea? :)
I removed both my rules now and replaced it with 1 rule.
On motion, light ON AND wait 5, then light OFF.
Same problem occurs, but it saves me 1 rules and keeps the rules list cleaner...
I'm hoping they'll fix this soon enough.