Securifi Community Forum
Securifi Products => Almond+ => Topic started by: SecureComp on December 14, 2015, 10:49:26 am
-
R83 is out and there are a lot of new features, capabilities and supported sensors. Please post your concerns, problems, issues and feedback on Release 83 here.
NOTE:
Backup your current firmware before attempting upgrade. Using the Web User Interface, goto Software Upgrade page and click Generate Archive.
Upgrade to R83 using the LCD User Interface. Once complete, reboot your Almond+
When accessing the Web User Interface, clear cache first.
New Android and IOS Apps are available to support R83. Upgrade to them prior to posting a problem with the Apps.
-
After upgrade, reboot, clearing cache and logging into Web User Interface.
Web User Interface:
Problem: Cree Connected bulbs not showing Dimming Level, showing as ON, DIMMER LEVEL NaN%
Problem: Cree Connected bulbs Dimming slider not working
Then tested both Android and IOS apps.
Cree Connected bulbs do work correctly on Android 5.0 App and IOS 1.8 Apps.
After changing brightness level using either Android or IOS App, the Web User Interface showed correct info and dimmer level slider is working !!
Logged out of Web User Interface and back in, Cree Connected bulbs are working and displaying correctly.
Conclusion: If your Cree Connected Bulbs are not displaying correctly in the Web User Interface, adjust the bulbs using either the IOS or Android app and the Web User Interface will display and function correctly.
-
Glad to see an update finally come out, but without support for IFTT and Echo, it is not enough to make me shelve the ST. I've gotten used to using voice commands and so has the family.
-
This is less about R083 than the 'cloud'.
I decided to do some testing before upgrading from R080 to R083, WeMo lamps, Aeon Labs appliance switch.
On the Web UI, the Sensors page, the lamp slider control now functions as you would expect. No lockups, only a little sluggish, however the x% displayed is incorrect (one say 0%, another says 100%, another says 21%, and none change value when the sliders/lights change level). The sliders remain at the last command level.
So it appears they've improved the 'cloud' functioning as well.
The 5.0 Android App x% display is similarly 'stuck', but the sliders function well to set the levels. After some seconds of inactivity, the sliders return to the x% value, yet the light doesn't change. So assuming this operates correctly on R083, the cloud and App fixes were not all that was necessary to get these to interplay/react properly.
The app and the WebUI get out of sync on the appliance switch, showing OFF when on, although at one point they were updating as it was switched, and presently shows OFF *and* 36.687 watts. If I change the 'load' power, then on the next power cycle of the appliance switch, then the power value updates. Now showing OFF *and* 34.822W. Let's hope R083 improves this.
No Rules tab content yet on the 5.0 App.
I'm also hoping the wired LAN dropouts, the wifi devices reconnecting to almond+, and the required 'wakeup' push on the keyfobs all go away, too. Oh, and maybe I'll be able to get rid of the CRON entry to reboot daily.
Updated to R083.
Set lamp power level to 52% via the LCD. Reads 51% and OFF on the 5.0App. Hit slider to 92, shows 92% and OFF, on the App.
Another Lamp shows ON and 0%, it's on near fully on.
-
Post upgrade, my internet connection drops after a few minutes. I have to reboot router to get my connection back. I am not amused.
-
Difficult to follow your point(s) mr23.
Observations on R80 are well documented elsewhere and could be misleading in the R83 thread. Also, what bulbs are you using?
Cree Connected Bulb reports correctly in Android 5.0, IOS 1.8 and Web User Interface meaning Slider % and On/Off Status. The LCD interface at 40% reports as 39% on the apps and Web UI. This is related to the 100% vs 99% for full on condition. Does not impact functionality and imho would rate it as a very minor concern.
Rules are not available on the Apps. (not sure how much that matters to me as Rules can be complex and tedious to work on a smartphone, a tablet maybe)
Scenes are available on Apps. One touch to turn all lights on/off, or all interior or exterior lights on/off for example.
Weekly cron reboots are never a bad thing with most any LINUX box, though I have had some time with uptimes exceeding a year. (not advisable) Interested to hear about any LAN drop outs or WiFi issues as you use the new firmware.
-
Post upgrade, my internet connection drops after a few minutes. I have to reboot router to get my connection back. I am not amused.
After the upgrade, reboot the Almond one time.
Check your Internet connection via the LCD interface diagnostic.
Are you hardwired or WiFi when you are experiencing a drop?
Some incorrectly configured 5Ghz options can create issues. Review your 5gig setup, especially your Country setting and width setting (20/40/80)
If the problem persists, absolutely contact Tech Support directly.
-
Hi !
Before I can fin any issue, I just want to thanks Securifi for this BIG update. Yes we wait a lot, but it's finally there and all seems really good !
Yes I would preffer regular little update but I'm happy to see that you work hard for us.
Just Keep going !
-
Since upgrade to R83, the local WebUI does not show scenes, sensors or rules. I see a screen like this: http://imgur.com/9EXZIsr for each of the tabs.
I tried a reboot. Anyone else? Help?
Edit: I can see sensors from the Android app and from connect.securifi.com just fine.
Edit: Figured it out. I had the websockets port 7681 blocked. Are there any other ports that need to be open on the lan side for everything to work properly?
-
Since upgrade to R83, the local WebUI does not show scenes, sensors or rules. I see a screen like this: http://imgur.com/9EXZIsr for each of the tabs.
I tried a reboot. Anyone else? Help?
Edit: I can see sensors from the Android app and from connect.securifi.com just fine.
You tried clearing your browser cache?
-
With the new R83 firmware, does Securifi has a amended list of compatible Z-wave sensors for reference? It seems the Fibaro Z-Wave Multi Sensor FIB_FGMS-001, Vision Security Z-Wave Flood Sensor VIS_ZF5201 and several other sensors are still not supported. Appreciate your early reply
-
With the new R83 firmware, does Securifi has a amended list of compatible Z-wave sensors for reference? It seems the Fibaro Z-Wave Multi Sensor FIB_FGMS-001, Vision Security Z-Wave Flood Sensor VIS_ZF5201 and several other sensors are still not supported. Appreciate your early reply
From:
https://forum.securifi.com/index.php/topic,3898.0.html
Firmware Z Wave:
• Added support for Aeon labs Multi sensor Gen5, Z-wave plus Fibaro Smoke detector, Z-wave plus Door Sensor, Fibaro Dual Relay module, First Alert Smoke and Carbon Monoxide Alarm.
• Added configuration settings for all Z-wave devices in connected sensors App.
• Added fix for Schlage Door lock (Model: BE469Nx) report issue.
• Added necessary delay during association of door locks to improve association process.
• Improved Energy reader report interval time to 2 minutes.
• Added fix for Schlage BE469NX lock.
• Added fix for z-wave crash.
• Ecolink Door sensors tamper issue fixed by updating Alarm Command class version.
• Added support for First Alert Smoke and Carbon Monoxide Alarm.
• For Schlage locks request value is enabled after setting the value.
• Setting value issue with dead device is fixed.
Firmware Zigbee:
• Added temperature index for Contact Switch, Motion Sensor and Water Sensor.
• Added Support for temperature reporting on Sercomm New door Sensor
• Added fixes for Zen Thermostat, Zigbee devices not responding, Peanut plug firmware upgrade, Thermostat initial values.
• Added Support for Osram color bulb.
• Fixed level reporting issue in Wemo bulb.
---snip---
Known Issues:
• For some Z-wave sensors, Temperature and Humidity rules would not be working.
• Minor responsive UI issues.
The WiKi sensor list is in the process of being updated.
https://wiki.securifi.com/index.php/List_of_compatible_sensors_-_Almond%2B_2014
-
thanks, am hoping the list of compatible Z-wave sensors get updated ASAP
Any plans to integrate an IP camera function into Almond+?
-
This has already been mentioned to Ashok but thought I should share...
After upgrading to R83 I can confirm the Osram RGBW bulb still appears as unsupported on the web ui.
The latest ios app does now show the extra options such as slider for colour choice, brightness etc, but changing any of these does not actual do anything.
Also there is no on/off from the ios app :(
However you are able to do all the above from the Almond touchscreen.
-
@ LaVia,
This has already been mentioned to Ashok but thought I should share...
After upgrading to R83 I can confirm the Osram RGBW bulb still appears as unsupported on the web ui.
The latest ios app does now show the extra options such as slider for colour choice, brightness etc, but changing any of these does not actual do anything.
Also there is no on/off from the ios app :(
However you are able to do all the above from the Almond touchscreen.
This would be taken care through our next release.
-
With the new R83 firmware, does Securifi has a amended list of compatible Z-wave sensors for reference? It seems the Fibaro Z-Wave Multi Sensor FIB_FGMS-001, Vision Security Z-Wave Flood Sensor VIS_ZF5201 and several other sensors are still not supported. Appreciate your early reply
Fibaro Motion Sensor is working just fine here.
-
@ LaVia,
This would be taken care through our next release.
I know you've only just released R83... but when do you think the next release might happen
Thanks
-
I know you've only just released R83... but when do you think the next release might happen
Thanks
Hey, let's finish the public soak of this firmware release and then get the API !! No doubt a few issues will pop up and a maintenance release will be needed but it's only been a couple of days. ::) ;D
If you are a member of the Beta group, next release may not be too far away. 8)
-
I just want to say how much I am loving the Scenes capability, the Presence Sensors and the improvements to the Apps !!
Really enjoying taking my HA setups to the next level.
And for sure, building a list of 'wants' and 'wishes' for future releases but for now, enjoying the hard work everyone at Securifi and in the Beta group has put in, many thanks!
-
I am having some issues regarding "Sensors" that are active or inactive as perceived by my Almond+. I have one device that is listed as being offline for 2 days, yet I can address it directly using its local IP address. This is no big deal.
More puzzling, though, and again not a big deal, is that the MAC addresses for many of of my items do not correspond to what I have for the items based on their IP addresses. So, for example, I have IPCAMS that I can address directly and whose MAC addresses, which I find on the camera set up page, is different from what is listed for that item on the Almond+ list. I also have several items that are listed as active, yet I cannot find their MAC addresses listed by the Almond+ in my Excel spreadsheet list of MAC addresses. I also have items that are absolutely online (Edimax access points) that are not seen by the Almond+, even though each has been assigned their unique IP address.
My Almond+ is otherwise functioning quite well with this firmware update. It has been quite stable.
I'm just wondering if anyone else has seen this issue.
Elliott
-
I am having some issues regarding "Sensors" that are active or inactive as perceived by my Almond+. I have one device that is listed as being offline for 2 days, yet I can address it directly using its local IP address. This is no big deal.
What kind of device?
My GE Link bulbs, if plugged into a 3 way switch, give me trouble. So do the GE Link bulbs plugged into an outside lamp that is triggered by Dusk/Dawn or Motion events. For the outside stuff I figure it's the lamp giving me trouble and plan on replace the fixtures.
The 3 way switch thing I am going to test by swapping the specific bulb out to another lamp.
More puzzling, though, and again not a big deal, is that the MAC addresses for many of of my items do not correspond to what I have for the items based on their IP addresses. So, for example, I have IPCAMS that I can address directly and whose MAC addresses, which I find on the camera set up page, is different from what is listed for that item on the Almond+ list. I also have several items that are listed as active, yet I cannot find their MAC addresses listed by the Almond+ in my Excel spreadsheet list of MAC addresses. I also have items that are absolutely online (Edimax access points) that are not seen by the Almond+, even though each has been assigned their unique IP address.
My Almond+ is otherwise functioning quite well with this firmware update. It has been quite stable.
I'm just wondering if anyone else has seen this issue.
Elliott
Incorrect MAC address info? yowza, first I've heard of that. Are the devices behind another router/switch or something? Often devices that support Internet Access, like a web cam, have configurable MAC info, sort of. All me devices are reporting correctly but I'll take a closer look at my camera web internal/external interfaces.
-
I also have items that are absolutely online (Edimax access points) that are not seen by the Almond+, even though each has been assigned their unique IP address.
Have you assigned static IP addresses to any of these by any chance? I think the presence detect stuff only works for devices that pull a DHCP lease from the Almond (hence no support in AP mode).
-
Have you assigned static IP addresses to any of these by any chance? I think the presence detect stuff only works for devices that pull a DHCP lease from the Almond (hence no support in AP mode).
I have a static on an xbox that shows as a presence/notifiable device.
-
More puzzling, though, and again not a big deal, is that the MAC addresses for many of of my items do not correspond to what I have for the items based on their IP addresses. So, for example, I have IPCAMS that I can address directly and whose MAC addresses, which I find on the camera set up page, is different from what is listed for that item on the Almond+ list. I also have several items that are listed as active, yet I cannot find their MAC addresses listed by the Almond+ in my Excel spreadsheet list of MAC addresses. I also have items that are absolutely online (Edimax access points) that are not seen by the Almond+, even though each has been assigned their unique IP address.
Have you tried 'fing' or equivalent, to see what IP/MAC's you get for each device?
-
Have you assigned static IP addresses to any of these by any chance? I think the presence detect stuff only works for devices that pull a DHCP lease from the Almond (hence no support in AP mode).
Yes and this could be the answer.
Thanks,
Elliott
-
What kind of device?
The specific device that is "inactive" is a Global Cahce WF2SL device. It is going through an access point (Edimax). However, there are other devices going through this access point that are recognized as active (e.g., an android tablet).
Incorrect MAC address info? yowza, first I've heard of that. Are the devices behind another router/switch or something? Often devices that support Internet Access, like a web cam, have configurable MAC info, sort of. All me devices are reporting correctly but I'll take a closer look at my camera web internal/external interfaces.
It could be that the access point (e.g., Edimax) is assigning a MAC address to the device.
Thanks for your input.
Elliott
-
Have you tried 'fing' or equivalent, to see what IP/MAC's you get for each device?
Thanks for the suggestion. I will get the "fing" app and take a look. While I was doing some research about MAC addresses, I found this useful website: http://aruljohn.com/mac.pl.
It will look up the manufacturer associated with the MAC address. This has helped me identify some of the devices that were unknown to me.
Elliott
-
Okay, so with the use of http://aruljohn.com/mac.pl to look up the manufacturer associated with a particular MAC address, I have established that the devices connected via Edimax access point have a MAC address pointing to Edimax as "manufacturer." So, that solves the riddle of the devices not having their given MAC addresses by their original manufacturers. The Edimax access point is assigning a new MAC address to the device and this MAC address is not the MAC address of the specific Edimax access point device. It is unique to the connected device (e.g., IPCam).
Elliott
-
Have you tried 'fing' or equivalent, to see what IP/MAC's you get for each device?
Thanks for putting me on to "fing." It's a cool app and very helpful.
Elliott
-
I have a static on an xbox that shows as a presence/notifiable device.
I meant static as in locally configured on the device; i.e., not a static DHCP lease. Guessing your XBox is the latter?
-
Osram lightify RGBW strip pairs to Almond. On/off, saturation, and color controls seem to work without a problem, Tne color temp control is either sluggish or doesn't change the temperature of the strip.
Just a note I don't know if it's app or the almond but it shows as supported in the iPhone app, but changing the controls has no effect on the strip.
-
I am having minor issues with some Scene updates.
Change the dim level of a light to 20%.
Click a Scene that changes a group of lights to 45% and sometimes (hate the intermittent problems) one bulb will stay stuck at 20%.
Wonder if I need to be able to add a delay counter to Scenes.
Will work the issue until I can create a consistent failure and then send logs and the steps needed to recreate the problem.
-
.
-
How do i clear the cache? Can´t find it.
Some issues with Fibaro sensors, the multi sensor shows temp in Farenheit on the app, I want it in Celcius as it is on the router, the humidity shows NAN.
Fibaro smoke sensor still can´t show the temperature. For some reason the Battery level has been on 100% since installation about 6 months ago.
Fibaro wall plug can´t show power consumption.
I did remove all the sensors and tried to install them as "different" sensors without getting all the data from them.
-
No router updates at all. No update to the old OpenWRT build which is over 5 years dated. No security patches for the old build either. The front door of this router should have a welcome banner put on it.
-
@ Paholainen,
Browser cache depends upon the browser, we have to clear the complete temporary files, history etc.,.
We have not added the support to show the temperature in Celsius yet. Other two issues, send the log files to debug and get back to you.
-
Hi,
I've just updated to R083 (I was using R069 as it did work fine for me) but now my upload speed in 5GHz Wifi is very low (way below 1Mbps to nothing), while wired devices gets 30Mbps with same test server on Speedtest.
Is there any way I can revert to R069? I tried to download the firmware from the original R069 release post but the link is already broken (Google Drive).
BR,
Miguel
-
Hi,
I've just updated to R083 (I was using R069 as it did work fine for me) but now my upload speed in 5GHz Wifi is very low (way below 1Mbps to nothing), while wired devices gets 30Mbps with same test server on Speedtest.
Is there any way I can revert to R069? I tried to download the firmware from the original R069 release post but the link is already broken (Google Drive).
BR,
Miguel
Solved. I could find the old firmware in one external drive. I've tested R069 and WiFi 5GHz works fine again, same as wired, so I'll stick with it for the moment.
It would be interesting if some other users could check it to know if it only happens to me or not. I did reboot the Almond+ few times after updating to R083 but the issue was still there.
-
Solved. I could find the old firmware in one external drive. I've tested R069 and WiFi 5GHz works fine again, same as wired, so I'll stick with it for the moment.
It would be interesting if some other users could check it to know if it only happens to me or not. I did reboot the Almond+ few times after updating to R083 but the issue was still there.
R83, easily 170Mbps download 5Ghz about 20ft, through 2 walls.
That is using Speedtest.net, so it is measuring throughput to some server on the Internet.
I have no doubt that testing the actual WiFi performance of a local peer to peer setup would be much much faster.
Make sure you are set to 40/80Mhz width, are on a clear channel and try to get close to the router for a 'best case' benchmark.
-
Local copy:
Download from my server to laptop: 22MB/sec
Upload to my server from laptop: 10MB/sec
(this is limited by my laptop I think)
Internet (via speedtest.net):
Download: 29Mbit/sec
Upload: 5Mbit/sec
(those are the limits of my line)
Seems OK to me :)
-
The Linear GD00Z Z-Wave garage door opener appears to be working acceptably for me now with R83. One small nit is that the IOS app continuous to show the state as "opening' even after the tilt sensor shifts after the door has opened. The LCD and local web browser correctly show the state transitioning from "opening" to "open". Other than that, it certainly appears usable now for me based on preliminary testing. Neither web interfaces allow for commanding yet. I have the GD00Z-2 (ADT) model, but I don't think any of that matters to the Almond.
-
This may have been mentioned, haven't read back through this thread.
The Web User Interface Sensors Page should show Inactive Devices as a different color.
Preferably Grey, same as the Android App.
-
Happens with my Lenovo laptop and happened to my desktop with is on Ethernet. on R80 and lower it was stable for months.
-
I concur with Darwin, with R83 the Linear garage open is working on lcd and android app and so far shows correct status of opened/closed whether actuating from Almond or manually. Great Job.
I have one new problem since R83 update - I have a number of lamp modules from Linear, GE, and Leviton. Since R65 I think, they have been working fine. On R83 there appears to be some glitch. or maybe there is some rule stuck in the background that isn't visible on LCD, Web, or Android. Some - but not all - of my lights are turning off at specific times where there is no rule or scene ir manual activation for them to do so. How can I track down what is causing this?
For example, by rule I have three lamps turn on at 5pm everyday and turn off at 10:40pm everyday. This has worked perfect since R65. After update to R83 two of these lamps turns off unexpectedly at 8:30pm everyday. I can see the turn off event in the device history. However, there is no rule, no scene, no presence setup, no manual activation.... ie, no reason for them to turn off.
What can I do to track down and fix?
-
@ spooky123,
Log files would be more helpful for us to identify what is causing the issue for you. Please do hit send logs by making sure the Almond+ is not rebooted before sending the logs. Thank you!
-
@Ashok
Did you get my log files? sent them a while ago. Also the rules is not working properly since update. A light is supposed to switch on when motion is sensed (worked fine on previous FW) but now it doesn´t always turn on, especially if it has recently turned off, it takes a long time before it turns on again, and sometimes the light is not on for the set duration.
-
@ Paholainen,
Yes, and as per the log files we did not find any issue with the Fibaro. Is it possible for you to remove and add the Fibaro once and check.
See if you can replicate the issue with the Rules and then send the log files which would give us some information on what is causing it.
-
@Ashok - can logs be generated from the web interface or android app?
-
@ spooky123,
Yes, using the latest android app you can send the log files.
-
ISSUE with RULES:
(Rule #30) in my case
Have a Rule setup to Turn on Lights IF Between 6AM-3:59PM AND Device X Joins THEN Turn ON a bunch of Inside Lights, Turn OFF Outside Lights, Set Mode to Home
Expected Result:
Arrive home anytime between 6AM-3:59PM, smartphone joins network, lights set, Home mode set.
What IS Happening:
Every morning at 6AM, All my lights are turning ON and outside lights are turning OFF. (smartphone has been connected to network all night)
Also
Rule works for when I arrive home anytime between 6-3:59, it's just all the lights coming on every day a 6AM that's a problem.
Sending logs tagged "@securecomp waking up every day at 6 because lights on"
snip from runRule.log
[2016-1-9 6:0:1.283793437] {PRINT} <================================runRule started=================================>
[2016-1-9 6:0:1.297905849] {PRINT} False in the range1
[2016-1-9 6:0:1.307612622] {PRINT} executing Rule 30 for AND condition is success
[2016-1-9 6:0:1.307789036] {PRINT} setting Job after 1 seconds for Rule 30 Result 1
-
@SecureComp:
That sounds like expected result to me. The presence sensing function acts more like a statement of "joined" not "joins" (like some of the text). So the rule you have set is acting more like:
IF Between 6am and 3:59pm AND Device X is joined/on the network THEN Turn On a bunch of lights, etc...
Your device is on the network all night. At 6am it is STILL on the network (joined to it) so the rule triggers. The current functionality is truly a presence sensor, are you on the network or not, versus an immediate action of such. So Rules that do not care whether it stays around work fine (If Device X Joins Then Set Home Mode, which I use by the way).
A way to create the "correct" effect might be:
IF Between 6am and 3:59pm And Mode is Away And Device Joins THEN Turn on lights, etc... This assumes you set your home to Away when your device leaves the network. So if the device does not leave the network (you are still home) it would not trigger because your home is in home mode.
-
It appears you are correct in that, though wouldn't I expect the lights to always be turning on every time the rule is evaluated? Which they are not, only during the initial activation of the rule does it evaluate true.
I do not kick on Away mode every time yet. Getting there,but not yet...too many false alarms.
-
If the device remains on the network, I do not know that it would trigger again. But I think you are right. If it is joined and between those times, every rule validation should turn the lights back on set home mode. Interesting that it does not. I really do not know. Someone from Securifi would have to answer that because the behavior does not exactly match a presence sensor and the time range method.
-
This is actually an issue that I had reported prior to the most recent firmware release. Their development staff claimed it was actually not an issue. IMO something is definitely not right. The terminology "JOINS" implies that the rule will execute the instant that the device joins. What is happening is that the rule will execute anytime the device is present on the network. I recommended changing the terminology from JOINS to ACTIVE or PRESENT. The last update I received on this was that my feedback was passed on to the appropriate team.
-
@barntacular:
That is something I am aware of and can be explained as they are being used as presence sensors... So it should activate while they are still around. Although I would also appreciate an immediate, one time option like you mention. The trouble I see with SecureComp's setup is that it triggers at 6am while the device is still on the network but does not continue to trigger. Like it is only being evaluated at the 6am setting unless the device really does leave and rejoin the network.
-
I can send the log files . it has been acting strange every day with the motion trigger. Like I explained if I walk by the sensor shortly after the light has turned OFF it won't come back ON again directly.
@ Paholainen,
Yes, and as per the log files we did not find any issue with the Fibaro. Is it possible for you to remove and add the Fibaro once and check.
See if you can replicate the issue with the Rules and then send the log files which would give us some information on what is causing it.
-
I think what I'll do is setup my Rule to trigger between time, if X joins and if light xyz is on. Light xyz will only be one if I leave the house, turned on by the leave the house rule. Light xyz will be off during the night because I'm sleeping. Will play around with that.
Or, this may force me to finish up my Home/Away testing and work out that last little bugs for my sirens and strobe lights.
-
@ SecureComp,
ISSUE with RULES:
(Rule #30) in my case
Have a Rule setup to Turn on Lights IF Between 6AM-3:59PM AND Device X Joins THEN Turn ON a bunch of Inside Lights, Turn OFF Outside Lights, Set Mode to Home
Expected Result:
Arrive home anytime between 6AM-3:59PM, smartphone joins network, lights set, Home mode set.
What IS Happening:
Every morning at 6AM, All my lights are turning ON and outside lights are turning OFF. (smartphone has been connected to network all night)
Also
Rule works for when I arrive home anytime between 6-3:59, it's just all the lights coming on every day a 6AM that's a problem.
Sending logs tagged "@securecomp waking up every day at 6 because lights on"
snip from runRule.log
[2016-1-9 6:0:1.283793437] {PRINT} <================================runRule started=================================>
[2016-1-9 6:0:1.297905849] {PRINT} False in the range1
[2016-1-9 6:0:1.307612622] {PRINT} executing Rule 30 for AND condition is success
[2016-1-9 6:0:1.307789036] {PRINT} setting Job after 1 seconds for Rule 30 Result 1
This is a normal behaviour because your device is already in the network and we are using "AND" Condition in the rule. However, we are planning to change the terminology of network devices in Rules.
-
@ barntacular,
This is actually an issue that I had reported prior to the most recent firmware release. Their development staff claimed it was actually not an issue. IMO something is definitely not right. The terminology "JOINS" implies that the rule will execute the instant that the device joins. What is happening is that the rule will execute anytime the device is present on the network. I recommended changing the terminology from JOINS to ACTIVE or PRESENT. The last update I received on this was that my feedback was passed on to the appropriate team.
Yes, our team has already accepted the feedback and we are working on changing the terminology of network devices state in Rules.
-
@ barntacular,
Yes, our team has already accepted the feedback and we are working on changing the terminology of network devices state in Rules.
Excellent, appreciate it.
Another item for the "wish" list, an Event that is Triggered by the Joining of a Device, instead of the Presence of a Device.
I will be able to create a work around using the "presence" of a device but it would be convenient to have a "joined" device trigger. Would love to have a look at the logic of the Rules Engine because you are close to having exactly what I need. The goal is being able to trigger events based on the arrival of different devices with variations based on time of day.
-
I too have a use case for 'joins' versus 'joined' or 'present', if it helps.
-
It's simple, there should be two options.
For example:
- at 6pm, when device is already joined
- between 6pm and 7pm, when device joins
-
Excellent examples. That functionality would assist with the Amazon Dash button's also.
I would say you have a 3rd also, based on the current "supposed" method:
between 6pm and 7pm, when the device is joined
Ex: Between 6pm and 7pm if device is joined turn task light on
That way my task light is on, no matter what, if my device is around. As it will be turned back on if turned off just because the command keeps telling it to be on (yes, I know you could just check if it turns off but where is the fun in that example).
That is compared to:
Ex: Between 6pm and 7pm if device joins turn task light on
Which would turn the task light on but only if the device joins during that tineframe
-
Why is there no scene functionality from the LCD UI? One should be able to set scenes from the LCD UI, otherwise there isn't much of a point to this being a touchscreen device.
Also, there should be a lock screen with tiles. I like the idea of the weather and time apps, but you should be able to add a few of these widgets together as tiles to create a lock screen. I would like to see the weather and the time and have the ability to set specific scenes all on one screen while the LCD UI is locked. I don't need to unlock the screen to look at the weather or turn the lights on/off. Right now, since there is no scene widget, if I have the LCD locked on the weather app, I have to unlock it, go to sensors, and turn each light on individually. Again, this isn't useful. This is actually slower than turning the lights on manually.
-
I would like to see another option besides Home and Away.
I would like a setting for Alarm whether I am Home or Away. That way I can have sensors signal an alarm if Alarm is set. Not dependent on Home or Away.
-
I would like to see another option besides Home and Away.
I would like a setting for Alarm whether I am Home or Away. That way I can have sensors signal an alarm if Alarm is set. Not dependent on Home or Away.
+1!
-
I would like to see another option besides Home and Away.
I would like a setting for Alarm whether I am Home or Away. That way I can have sensors signal an alarm if Alarm is set. Not dependent on Home or Away.
Isn't that what Perimeter Alarm is ??
The Perimeter (alarm sensors) are activated while you are still in Home mode and will trigger a siren if you choose.
-
How can we set/use that?
-
How can we set/use that?
I've done a couple things with Rules that are something like IF HOME AND DOOR OPENS THEN SIREN ON or IF HOME BETWEEN 11PM-5AM AND MOTION DETECTED THEN ALARM. I call those "perimeter" Rules.
Additionally, the Keyfob, activating the "lock" function will cause the door/window sensors and motion detectors to trigger an alarm in Home or Away mode. I call that the "perimeter" mode as well. Would have to dig out the key fob documentation to confirm what Securifi calls that, thought it was Perimeter mode.
-
And now that you mention it, it would be nice to be able to specifically check a Box for a Rule that assigns it a "Perimeter Rule" designation that is managed by the "Lock" "Unlock" or "Perimeter" Alarm function.
Specifically I would like to be able to IGNORE SOME SENSORS when ACTIVATING the ALARM SYSTEM but have all the other sensors trigger an Alarm. I do this currently by creating very specific Rule Sets but it would be easier to just check a box.
-
Ah, you're not really setting a different mode, you're just setting a specific state on the keyfob to use that in some rules.
That's indeed a possibility, but as you say, it would be easier if this was a build-in function...
-
I don't have a key fob for my sensors so that doesn't work for everyone.
But, for alarming I don't necessarily want an alarm on when Im home and between certain hours. and I dont want it always when Im away but i do want other types of notifications.
Too many rules to get alarms set up right and right now we cant turn off rules via the app.
I would prefer an alarm mode, that way it is set without any preconditions based on time/home/away etc.
-
Ah, you're not really setting a different mode, you're just setting a specific state on the keyfob to use that in some rules.
That's indeed a possibility, but as you say, it would be easier if this was a build-in function...
No, that's not quite right, I don't think.
The key fob has an "lock" and "unlock" symbol. Meaning, arm or disarm. It works in both Home and Away modes.
In addition to that, I have created some rulesets to leverage the key fob to turn off the Siren or activate the Siren manually.
-
I don't have a key fob for my sensors so that doesn't work for everyone.
Nope it doesn't.
But if you purchased open/close/motion sensors and a siren with the intent of creating a security system, the key fob is only a $15-$20 add on.
Still, a reasonable feature request would be a 'virtual key fob' or Perimeter Arm/Disarm on the LCD User Interface or Apps.
But, for alarming I don't necessarily want an alarm on when Im home and between certain hours. and I dont want it always when Im away but i do want other types of notifications.
Too many rules to get alarms set up right and right now we cant turn off rules via the app.
I would prefer an alarm mode, that way it is set without any preconditions based on time/home/away etc.
Yep, a nice add-on feature for the Apps that shouldn't be too difficult to setup. Not to minimize the effort, any change is a lot of man hours, but at least the underlying features already exist.
-
Problem: If static DHCP leases are used, and the router is rebooted, DHCP in general no longer functions. Disabling and re-enabling the DHCP throws the following errors:
Jan 16 12:52:49 AlmondPlus user.info sysinit: WRITE ERR: ep 01 clus 0019 attr 0006 not supported^M
Jan 16 12:52:49 AlmondPlus user.info sysinit: Svc Disc: Starting discovery for cluster 0x0019^M
Jan 16 12:52:49 AlmondPlus user.info sysinit: Svc Disc: Waiting 2 sec for discovery to complete^M
Jan 16 12:52:49 AlmondPlus user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Jan 16 12:52:49 AlmondPlus user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Jan 16 12:52:49 AlmondPlus user.info sysinit: dnsmasq: bad command line options: duplicate dhcp-host IP address [b]x.x.x.x[/b]
Jan 16 12:52:49 AlmondPlus daemon.crit dnsmasq[23319]: bad command line options: duplicate dhcp-host IP address [b]x.x.x.x[/b]
Jan 16 12:52:49 AlmondPlus daemon.crit dnsmasq[23319]: FAILED to start up
Where x.x.x.x above is one of the static DHCP leases assigned.
Resolution: Remove all static DHCP leases. Supposing these can't be used correctly anymore with R083?
-
Lots of static DHCPs here, I have not had a problem with it so far.
-
Need to implement a rule besides Home and Away so that let say that when Mud Room Door opens between 2.15pm and 2.30pm, it sends notification so we know that kids are home and do not need to be picked up from school.
-
You can set in the mobile app that you want a notification for that room when mode is Away. You'd know your kids came home if you set it like that.
-
I was hoping v83 would FINALLY add in support for the Aotec HEM v2 (DSB28) but alas, it is not to be.
The A+ goes back to the junk pile while I wait for the tp-link SR20 router to be released. Sometimes newer is not better and Almond+ proves this over and over again.
-
I was hoping v83 would FINALLY add in support for the Aotec HEM v2 (DSB28) but alas, it is not to be.
The A+ goes back to the junk pile while I wait for the tp-link SR20 router to be released. Sometimes newer is not better and Almond+ proves this over and over again.
Are you certain?
I've been using the Aeotec HEM Gen1 for over 6 months and now have more configuration options with R83.
What are the distinct advantages of the Gen 2 unit over the $25 Gen 1? Only thing I noted was "real time" data which would have to be collected and forwarded. Currently I'm getting frequent updates and threshold changes, more than enough data to aggregate. Not sure I even care about "real time" data as I don't have a gauge on the wall I'm watching. I am in the process of building an app to monitor usage and set some alarms.
What are your plans for collecting and utilizing data? I ask because for $25 you can have an immediate workaround that is quite serviceable.
-
Firstly found this firmware version pretty stable when running my Almond+ as a AP. The only issue I have come across is on occasions devices are unable to connect to the 2.4 GHz wifi. My newer devices tend to use 5GHz so I don't notice this problem but older devices only work on 2.4GHZ and either disabling/enabling or re-booting the router fixes the problem. This happens after the device has been online for a couple of weeks.