Securifi Community Forum
Securifi Products => Almond+ => Topic started by: Ashok on August 11, 2016, 09:42:27 am
-
Any feedback related to R089, please post it here.
-
I am still on R83 and have a question before upgrading.
My already registerded ZWAVE devices will still be there after the upgrade, right? I have installed them behind the wall in switches and dont want to open -> pair then again with the almond.
-
Your devices should remain over upgrade. They did for me and it has pretty consistent about that.
-
@ TEmp,
I am still on R83 and have a question before upgrading.
My already registerded ZWAVE devices will still be there after the upgrade, right? I have installed them behind the wall in switches and dont want to open -> pair then again with the almond.
To my best knowledge, there shouldn't be any issue, please go ahead and update it and let us know the status.
-
I am still on R83 and have a question before upgrading.
My already registerded ZWAVE devices will still be there after the upgrade, right? I have installed them behind the wall in switches and dont want to open -> pair then again with the almond.
They have all been intact for me. For me the only time, I have had to re-pair is when there are new features added for that specific Z-wave device. If your z-wave device already works the way you want it to, you shouldn't have to add them again.
-
Update worked well, all devices still there and operateable.
-
Update complete, system operational.
Updated Android App working.
Going through and verifying operation of all devices and updates.
-
Created Rule using Sunrise - using WEBGUI
If HOME and SUNRISE THEN light_xxx ON
Saved the Rule
The Rule only displays the HOME IF condition, not the Weather/Sunrise related info.
When going in to Edit the Rule, the Weather/Sunrise info is not displayed/enabled. Not sure if it really operational, will have to wait until early tomorrow morning.
Timezone has been set correctly.
UPDATE:
Went in and edited Rule using Android, everything worked as expected.
The SUNRISE CONDITION was properly displayed in the Rule and showed up in the WEBGUI.
Edited a 2nd time using WEBGUI (emptied browser cache first), same issue.
This is using Safari.
Will repeat using Chrome.
UPDATE2:
Chrome has same issue.
When creating a Rule using WEBGUI and the WEATHER CONDITION, info not retained.
Rule created using Android App, WEATHER CONDITION retained.
Will try rebooting, flushing caches again, see if anything helps. Then will dig a little deeper.
-
@SecureComp:
Did you clear the browser cache after the upgrade before you saw the problem? I have found clearing cache after upgrades to be pretty much mandatory.
-
@SecureComp:
Did you clear the browser cache after the upgrade before you saw the problem? I have found clearing cache after upgrades to be pretty much mandatory.
Oh absolutely. Have cleared it several times now, on both browsers. Even closed and restarted the browser, rebooted the laptop as well as the A+.
Are you not observing the issue when creating WEATHER CONDITION based RULE in the WEBGUI?
-
@ SecureComp,
Oh absolutely. Have cleared it several times now, on both browsers. Even closed and restarted the browser, rebooted the laptop as well as the A+.
Are you not observing the issue when creating WEATHER CONDITION based RULE in the WEBGUI?
Try to do the same through Incognito window and check the status.
-
No problems at all with Sunrise or Sunset (screenshot attached). Did you select the checkmark to the right of the sunrise/sunset selection for the offset? That will actually add it to the rule. Screenshot attached.
-
After the upgrade, IOS app is unable to connect to the almond+ via cloud. tried to switch the app to local mode, and the IOS app crashed.
IOS Crash Report:
{"app_name":"Almond","timestamp":"2016-08-11 22:54:35.35 -0400","app_version":"2.2","slice_uuid":"ca998c4d-4929-3d68-abae-1987e83e2fdf","adam_id":908025757,"build_version":"4779","bundleID":"com.securifi.almond","share_with_app_devs":false,"is_first_party":false,"bug_type":"109","os_version":"iPhone OS 9.3.4 (13G35)","name":"Almond"}
Incident Identifier: D23DBA87-E18E-4B2D-B117-3F8931908792
CrashReporter Key: b6b2d0b6d30faedb6f60204523e06b941bb32910
Hardware Model: iPhone7,2
Process: Almond [2176]
Path: /private/var/containers/Bundle/Application/CB188CA0-E09C-4737-A2E3-E4C1889691C1/Almond.app/Almond
Identifier: com.securifi.almond
Version: 4779 (2.2)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
Date/Time: 2016-08-11 22:54:35.35 -0400
Launch Time: 2016-08-11 22:52:41.41 -0400
OS Version: iOS 9.3.4 (13G35)
Report Version: 105
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 0
Filtered syslog:
None found
Last Exception Backtrace:
(0x182d72db0 0x1823d7f80 0x182d72a70 0x18370dff0 0x1836605dc 0x1002244cc 0x100224064 0x182d14dfc 0x182d1461c 0x182d1439c 0x182d7d414 0x182c526c8 0x18365a80c 0x100218a80 0x1827bd47c 0x1827c8a20 0x10021893c 0x100218358 0x10021a4f4 0x10021f3a0 0x10021eaa4 0x1001faaf4 0x1827bd4bc 0x1827bd47c 0x1827c2b84 0x182d28d50 0x182d26bb8 0x182c50c50 0x184538088 0x187f3a088 0x1000aad44 0x1827ee8b8)
Global Trace Buffer (reverse chronological seconds):
0.539640 CFNetwork 0x00000001833f7e7c TCP Conn 0x13ff84670 complete. fd: 7, err: 0
0.539640 CFNetwork 0x00000001833f93a8 TCP Conn 0x13ff84670 event 1. err: 0
8.853404 CFNetwork 0x00000001833558e0 TCP Conn 0x13fd1e210 SSL Handshake DONE
9.361561 CFNetwork 0x00000001833557f0 TCP Conn 0x13fd1e210 starting SSL negotiation
9.362044 CFNetwork 0x00000001833f7e7c TCP Conn 0x13fd1e210 complete. fd: 11, err: 0
9.362897 CFNetwork 0x00000001833f93a8 TCP Conn 0x13fd1e210 event 1. err: 0
9.446128 CFNetwork 0x00000001833f7e7c TCP Conn 0x13fd230d0 complete. fd: 7, err: 0
9.446319 CFNetwork 0x00000001833f93a8 TCP Conn 0x13fd230d0 event 1. err: 0
9.515603 CFNetwork 0x00000001833f9480 TCP Conn 0x13fd1e210 started
10.069554 CFNetwork 0x00000001833f8a64 TCP Conn 0x13fdcf7f0 network reachability changed : setting stream error to ENOTCONN
10.070189 CFNetwork 0x00000001833f8a64 TCP Conn 0x13fee0490 network reachability changed : setting stream error to ENOTCONN
112.340035 CFNetwork 0x00000001833558e0 TCP Conn 0x13fee0490 SSL Handshake DONE
112.416361 CFNetwork 0x00000001833557f0 TCP Conn 0x13fee0490 starting SSL negotiation
112.416811 CFNetwork 0x00000001833f7e7c TCP Conn 0x13fee0490 complete. fd: 8, err: 0
112.418383 CFNetwork 0x00000001833f93a8 TCP Conn 0x13fee0490 event 1. err: 0
112.446056 CFNetwork 0x00000001833f9480 TCP Conn 0x13fee0490 started
113.165733 CFNetwork 0x00000001833558e0 TCP Conn 0x13fe92e10 SSL Handshake DONE
113.210123 CFNetwork 0x00000001833558e0 TCP Conn 0x13fdae9e0 SSL Handshake DONE
113.299436 CFNetwork 0x00000001833557f0 TCP Conn 0x13fe92e10 starting SSL negotiation
113.299629 CFNetwork 0x00000001833f7e7c TCP Conn 0x13fe92e10 complete. fd: 11, err: 0
113.302096 CFNetwork 0x00000001833f93a8 TCP Conn 0x13fe92e10 event 1. err: 0
113.306492 CFNetwork 0x00000001833f7e7c TCP Conn 0x13fdcf7f0 complete. fd: 7, err: 0
113.307160 CFNetwork 0x00000001833f93a8 TCP Conn 0x13fdcf7f0 event 1. err: 0
113.340097 CFNetwork 0x00000001833557f0 TCP Conn 0x13fdae9e0 starting SSL negotiation
113.340510 CFNetwork 0x00000001833f7e7c TCP Conn 0x13fdae9e0 complete. fd: 18, err: 0
113.342439 CFNetwork 0x00000001833f93a8 TCP Conn 0x13fdae9e0 event 1. err: 0
113.479322 CFNetwork 0x00000001833f9480 TCP Conn 0x13fdae9e0 started
113.501771 CFNetwork 0x00000001833f9480 TCP Conn 0x13fe92e10 started
113.507716 CFNetwork 0x0000000183453e5c Creating default cookie storage with default identifier
113.507716 CFNetwork 0x0000000183453e28 Faulting in CFHTTPCookieStorage singleton
113.507716 CFNetwork 0x00000001834a5e50 Faulting in NSHTTPCookieStorage singleton
after upgrading to new IOS app, all seems to be working once again.
-
No problems at all with Sunrise or Sunset (screenshot attached). Did you select the checkmark to the right of the sunrise/sunset selection for the offset? That will actually add it to the rule. Screenshot attached.
THANK YOU !!
That was it, operator error. It happens ::)
I'm guessing the App automatically takes care of that? In any event, now a happily adding a bunch more Rules. 8)
-
Almond and Internet was working fine. My phone updated to latest iOS app. When I opened the app, it says my almond needs to be updated. Did the update. Now it can't connect to Internet. Reboot doesn't help.
Not sure what else to try. :(
-
@ bebopblues,
What does the status show "Internet Connected" or "Internet Disconnected" and try to do a sequential power cycle that should take care of it.
-
So, I updated the firmware from R085 to R089, because the smartphone app would not let me access the Almond+ without upgrading. I did this via the router LCD screen. It was a disaster!! The upgrade process wiped out all my settings (SSID, passwords, port forwarding, static IP addresses), but not my sensors; this despite the UI indicating "save all settings.". To make matters worse, when I tried to restore settings from my backup file, I got the message that it was not a valid file. Furthermore, the UI is flashing that I need to upgrade, the smartphone app states that my router needs an updated, BUT the router LCD indicates that I have installed R089.
-
@ bebopblues,
What does the status show "Internet Connected" or "Internet Disconnected" and try to do a sequential power cycle that should take care of it.
It show disconnected. But it has shown that in the past, doing a DHCP scan usually fixes it.
But anyway, internet is working in the morning after. I'm not sure why it didn't the previous night. I guess there's a slight chance that my internet went down THE EXACT SAME TIME as I was doing the update. I have no idea.
-
So, I updated the firmware from R085 to R089, because the smartphone app would not let me access the Almond+ without upgrading. I did this via the router LCD screen. It was a disaster!! The upgrade process wiped out all my settings (SSID, passwords, port forwarding, static IP addresses), but not my sensors; this despite the UI indicating "save all settings.". To make matters worse, when I tried to restore settings from my backup file, I got the message that it was not a valid file. Furthermore, the UI is flashing that I need to upgrade, the smartphone app states that my router needs an updated, BUT the router LCD indicates that I have installed R089.
Feedback thread over here:
https://forum.securifi.com/index.php/topic,4425.0.html
-
I had to do a manual install, as this update simply wasn't detected when trying via the LCD UI.
Looks like things are starting to finally be what was promised in terms of the HA features at least.
-
Love the Sunset and Sunrise feature! Finally something I've been missing that those crappy WEMO devices had long before my Almond+ shipped.
-
I too wanted sunrise/sunset feature very much. But as it is now it isn't very useful to me. I guess I can only use sunset at Europe/Helsinki, but today
the sun sets where I live. (Vaasa, Finland) 29 minutes after Helsinki sunset.
-
I too wanted sunrise/sunset feature very much. But as it is now it isn't very useful to me. I guess I can only use sunset at Europe/Helsinki, but today
the sun sets where I live. (Vaasa, Finland) 29 minutes after Helsinki sunset.
Try using the WEBGUI to configure, see if the A+ detects a difference between A+ settings and computer settings. Mine did and allowed me to adjust the A+ accordingly.
-
Try using the WEBGUI to configure, see if the A+ detects a difference between A+ settings and computer settings. Mine did and allowed me to adjust the A+ accordingly.
I don't understand what you mean. And looking over the web gui I don't notice anything that would help. I live 700km north of our capital Helsinki so there will always be a
time difference between there and here when sun sets or rises. And in the A+ settings I can only choose Europe/Helsinki as region. Same problem with weather display on A+.
-
I don't understand what you mean. And looking over the web gui I don't notice anything that would help. I live 700km north of our capital Helsinki so there will always be a
time difference between there and here when sun sets or rises. And in the A+ settings I can only choose Europe/Helsinki as region. Same problem with weather display on A+.
When I used the WEB GUI to setup a Rule using WEATHER CONDITION, my browser and A+ were not set to be in the same time zone and I was prompted to adjust the time zone of the A+ to match the web browser.
Not sure if the same would work for Euro Settings. Will try to recreate on this end.
-
Version R089 broke my program that interfaces with the Websocket. Has the Websocket syntax changed? Anyone else having any issues?
-
The Websocket syntax has definitely changed based on my testing.
-
@ mikeys63,
Version R089 broke my program that interfaces with the Websocket. Has the Websocket syntax changed? Anyone else having any issues?
It could be possible, will update the status by tomorrow.
-
When I used the WEB GUI to setup a Rule using WEATHER CONDITION, my browser and A+ were not set to be in the same time zone and I was prompted to adjust the time zone of the A+ to match the web browser.
Not sure if the same would work for Euro Settings. Will try to recreate on this end.
Oh I see what you mean now. The problem for me isn't the time zone. I'm in the same zone as our capital, Helsinki. But with sunrise/sunset also the latitude is important. I live 700 km north of Helsinki, so for example sunset in the summer is later here than in Helsinki (currently 29 minutes). But in the winter the sun sets earlier here than in Helsinki. With the current A+ firmware I get sunrise/sunset and weather info for Helsinki because
I can choose only Helsinki in A+ settings and not where I really am.
-
Oh I see what you mean now. The problem for me isn't the time zone. I'm in the same zone as our capital, Helsinki. But with sunrise/sunset also the latitude is important. I live 700 km north of Helsinki, so for example sunset in the summer is later here than in Helsinki (currently 29 minutes). But in the winter the sun sets earlier here than in Helsinki. With the current A+ firmware I get sunrise/sunset and weather info for Helsinki because
I can choose only Helsinki in A+ settings and not where I really am.
I have the same or similar problem. The Time Zone is set correctly in the Almond+, but the geographic location for Weather is apparently set to "Pretty Prairie, KS." I live in Marion, IA and apparently there is currently no place in Almond+ controls to set the geographic location. So not only is Weather incorrectly shown but also since the latitude of Pretty Prairie is further S from Marion, my Sunrise/ Sunset base times are incorrect. Reading older threads it seems the Almond+ gets geographic location from a NTP Server. Am I missing something insofar as being able to set the geographic location?
-
So for those working the Sunrise, Sunset latitude issue, wouldn't the offset work?
Meaning, the difference between local and configured sunrise/sunset is always 30 mins or whatever?
As for weather, that's a little more involved.
-
So for those working the Sunrise, Sunset latitude issue, wouldn't the offset work?
Meaning, the difference between local and configured sunrise/sunset is always 30 mins or whatever?
As for weather, that's a little more involved.
No, a user shouldn't have to mess around with offset just to get base sunrise/ sunset correct. Sunrise/ sunset should be implemented to be correct for the router geographic location... as should weather if it is going to be reported on the Almond+.
-
There's a thread from a year ago or more about the geographical issue where the weather display problem is already discussed,.
Weather wasn't so important for me, but sunrise(sunset is. So I'm really hoping this can be improved.
-
No, a user shouldn't have to mess around with offset just to get base sunrise/ sunset correct. Sunrise/ sunset should be implemented to be correct for the router geographic location... as should weather if it is going to be reported on the Almond+.
I think folks are conflating issues incorrectly or I am misunderstanding some of the comments.
Timezone does not determine your weather location, nor sunrise sunset. Perhaps there is an issue w/ the A+ but I can't be certain based on the previous posts.
If the weather being displayed is not local enough for you, it may have nothing to do with the A+ and everything with the way your ISP and geoloc play together.
What does matter is how well the geoloc ip stuff is working for your location.
If folks want to msg / PM for more detail, I will work with you to see what your system has identified as your location and the related details on sunrise/sunset/weather/timezone.
We should take detailed discussion on weather/timezone/sunrise/sunset to another thread.
I will not work 'extended problem solving' in this thread as it would be too much of a distraction.
To give you an idea, use a tool like https://geoiptool.com and take a look at that info. If it is not specific enough to your location, it likely explains why the A+ isn't showing you what you might expect.
@bikerbob
@andersos
I sent you both PM's.
-
That tool sets me about 100km from where I live.
Probably not a big difference for sunset/sunrise, but not usable for weather.
Maybe Securifi should implement support for Weather Underground. Those have local stations all over, I even have one in my street...
-
That tool sets me about 100km from where I live.
Probably not a big difference for sunset/sunrise, but not usable for weather.
Maybe Securifi should implement support for Weather Underground. Those have local stations all over, I even have one in my street...
PM inbound
Please check that your routing tables are up to date on your ISP provided equipment.
A reset of your local equipment can make a difference.
-
The easiest solution, perhaps, would be a way to manually change your location (the almond's) if the automated ones are too far off, which would be universal (time, weather, sunrise/set).
-
The easiest solution, perhaps, would be a way to manually change your location (the almond's) if the automated ones are too far off, which would be universal (time, weather, sunrise/set).
We should be given ability to specify a lat/long.
-
We should be given ability to specify a lat/long.
So far, the issue has been with autoip or geoip not providing the correct/best location of the user. This is an ISP issue. (which of course users don't care about, they just want it to work and rightfully so)
Most folks with the issue have requested the ability to specify a zip/postal code. Add to that the ability to specify Lat/Long (varying formats), Country, State, City and you know have a bunch of input screens to work/validate, databases to talk/connect to. I see that being a bit of a mess. Perhaps via the Web GUI as an option or the Cloud connection if it survives.
Maybe it would be best to put in a feature request and make some noise in that thread as the A+ autoip/geoip stuff is working properly?
-
OK. So it looks like the DNS is not very reliable. I tried a ping running over the past 4 days using EMCO ping monitor. This is on a hardwired machine (not wireless). I don't see a pattern to the name resolution problems. But I will continue to look into this.
(https://i.sli.mg/unTxWj.png)
My next test is to include a localhostname to see if it's the Almond's DNS or my AT&T DNS
-
OK. So it looks like the DNS is not very reliable. I tried a ping running over the past 4 days using EMCO ping monitor. This is on a hardwired machine (not wireless). I don't see a pattern to the name resolution problems. But I will continue to look into this.
(https://i.sli.mg/unTxWj.png)
My next test is to include a localhostname to see if it's the Almond's DNS or my AT&T DNS
Not a fan of these tests as they don't account for downtime or 'slow response' from the remote server(s). Often you are talking to cached servers through cached systems and there are all sorts of possible issues. Run a script doing random IP to Name lookups and that would give you a much better idea about DNS vs stability of network routes. Heck your PC doing a Microsoft update locally could hose the results completely.
Are any folks having an actual DNS issue? As in browsers kicking back errors?
-
Are any folks having an actual DNS issue? As in browsers kicking back errors?
That's why I went and set this up. I was getting intermittent browser errors and I wanted data to show that.
I know there are many reasons that this is not the "ideal" , but its good enough. It still doesn't explain why before R089 when I run this for 4 days I had no error and after R089 there are so many errors. I am fairly certain if I downgrade my firmware these numbers would be much better.
-
I have been having intermittent issues as well. I have corrected for any interference and that doesn't seem to be an issue. Has only been since the latest update, before that I was experiencing some wifi interference but adjusting the channels corrected it.
-
@Ashok Any word on the Websocket issues?
It could be possible, will update the status by tomorrow.
-
So far, the issue has been with autoip or geoip not providing the correct/best location of the user. This is an ISP issue. (which of course users don't care about, they just want it to work and rightfully so)
Most folks with the issue have requested the ability to specify a zip/postal code. Add to that the ability to specify Lat/Long (varying formats), Country, State, City and you know have a bunch of input screens to work/validate, databases to talk/connect to. I see that being a bit of a mess. Perhaps via the Web GUI as an option or the Cloud connection if it survives.
Maybe it would be best to put in a feature request and make some noise in that thread as the A+ autoip/geoip stuff is working properly?
I don't know how my ecobee3 thermostat does it, but it (I don't input anything [zipcode, city, lat/long, etc.] identifying where I live) but it somehow via WiFi determines that I live in Marion, IA and reports the weather conditions here... though maybe a few hours late.
-
I don't know how my ecobee3 thermostat does it, but it (I don't input anything [zipcode, city, lat/long, etc.] identifying where I live) but it somehow via WiFi determines that I live in Marion, IA and reports the weather conditions here... though maybe a few hours late.
Do you have an app connected to the Ecobee?
Are you using the Ecobee with Amazon Echo?
Both of the above allow the unit to determine location and other info via your smartphone or via Amazon's loc service.
-
Lat/long should be added to A+ settings. From what I've seen most weather services work with lat/long too. They could add a setup option to the Almond app to get lat/long from smrtphones and set the location in A+.
-
@ Zexon83,
Sorry for the delay, just got the update we will soon update the Web Socket API according to the latest firmware.
-
Do you have an app connected to the Ecobee?
Are you using the Ecobee with Amazon Echo?
Both of the above allow the unit to determine location and other info via your smartphone or via Amazon's loc service.
Yes, I do have the Android Ecobee App connected to the ecobee3... but not an Amazon Echo.
-
Do you have an app connected to the Ecobee?
Are you using the Ecobee with Amazon Echo?
Both of the above allow the unit to determine location and other info via your smartphone or via Amazon's loc service.
Regarding how the ecobee3 determines location for weather I did find this under ecobee Support:
"Weather Station
ecobee Support
posted this on September 12, 2012, 4:04 PM
Q: I live in a mountainous region in New Hampshire, and I'm wondering which weather station the thermostat will connect to (valley or mountain)? Around here, this makes a big difference.
A: The weather forecast is determined by the address you use to register your thermostat. From that address, the ecobee determines the latitude and longitude coordinates. The thermostat finds the closest weather stations and then uses an algorithm to interpolate the data, based on geography, to derive weather for your (very specific) location. The ecobee will then take several closest weather stations in your area, run an algorithm, and estimate the weather at your house (as opposed to a single location - i.e. airport)"
So it looks like ecobee3 determines the geographic location for their weather forecast from the ecobee product registration address.
-
Any feedback related to R089, please post it here.
I'm still having issues with my internet connection dropping; requiring a reboot or power cycle.
I'm also having issues with the Android App where devices I have set to Notify Me will change from "Always" to "Never".
-
It's great the A+ has had generic HEM support since R085, however, we need some way of resetting the stats. With my Aeotec HEM v2, there's no way to reset the "energy XXXkwh" either manually or on a calendar basis. It would be nice to have daily and monthly logs. Also, the clamp measurements are never correct and will never change after the initial setup.
The temperature unit display on my z-wave motion sensor is incorrect. The LCD and web interface shows C but the apps only show F.
-
@ rf134a,
It's great the A+ has had generic HEM support since R085, however, we need some way of resetting the stats. With my Aeotec HEM v2, there's no way to reset the "energy XXXkwh" either manually or on a calendar basis. It would be nice to have daily and monthly logs. Also, the clamp measurements are never correct and will never change after the initial setup.
The temperature unit display on my z-wave motion sensor is incorrect. The LCD and web interface shows C but the apps only show F.
As long as load value is not changed, we don't get any new readings try to connect any other device, which has different load, also try to turn it off wait for few seconds and then turn it back on.
On the app, we are yet to add the support for changing the readings from C to F and vice versa.
-
I'm still having issues with my internet connection dropping; requiring a reboot or power cycle.
I'm also having issues with the Android App where devices I have set to Notify Me will change from "Always" to "Never".
I'm still on R083, and for many months up until recently I had all devices marked as Notify Me -> Always. They are all now Never.
Not sure when they stopped reporting. Couple of months ago maybe.
Must be a cloud issue.
-
After the update my UI is once again unusable(previously got a unit replaced for a very similar issue). This time it seems like the touch screen calibration is really off. If I touch the center of the screen a button far offset from where I pressed will respond to the interaction. Any idea how to reset the calibration?
-
Really like this new drop.
One issue, one Peanut is working well, the other Peanut, not so much. Data being reported by 2nd Peanut (listed as Electronics in my list) is reporting Hex data. It's as if the device did not get through the conversion process.
Screenshots show Device listing (Peanut labeled as Electronics), sample history with good data from another Peanut, sample history with bad data from Peanut labeled as Electronics.
Will forward logs as well.
Power has been cycled on the Peanut.
-
Have you tried removing and pairing the "odd" Peanut Plug?
-
There is definitely some connection flakiness here. I had two laptops, one hooked up to ethernet via a switch to my Almond. The other one was connected to the WiFi of my UVerse router. Ran a test for 4 days to the same 4 websites
The Almond consistently dropped connections and missed connections. The UVerse Wireless while not perfect, was substantially better.
-
Have you tried removing and pairing the "odd" Peanut Plug?
Nope, not yet. Figured I'd forward the info to the team, let them get a look see and go from there.
I'm sure I could delete and re-pair and it would be fine but I don't want to have to do that. Always messes with my rules, device order, etc.
-
Gotcha. My device order is a mess, but at least it is easier to "repair" rules and scenes when a device gets removed than it used to be. Being able to deal with them in the app has really helped.
-
I'm still on R083, and for many months up until recently I had all devices marked as Notify Me -> Always. They are all now Never.
Not sure when they stopped reporting. Couple of months ago maybe.
Must be a cloud issue.
I keep changing the Notify Me to "Always", but the setting resets to "Never" when the router is power cycled.
-
@ Zexon83,
Sorry for the delay, just got the update we will soon update the Web Socket API according to the latest firmware.
Any updates for the R089 Web Socket API ?
-
@ mikeys63,
Any updates for the R089 Web Socket API ?
It is updated, please check and let me know, if there is any issue.
-
@ rf134a,
As long as load value is not changed, we don't get any new readings try to connect any other device, which has different load, also try to turn it off wait for few seconds and then turn it back on.
On the app, we are yet to add the support for changing the readings from C to F and vice versa.
The HEM is attached to the breaker box, so the loads are constantly changing, from a low of 300w to a high of 12kW. While the values to the clamps are off and haven't changed since 5 minutes after installation, the other values are fine.
-
I think the rules are now much better, but still need a lot of work to be useful. There needs to be a way to use state of devices as well as events. It seems to do this sometimes, like triggering at 10:30 and light on. In this case the light on is a state and it works (even though in the editor, it reads as "Desk TURN ON", I don't need to turn on my desk lamp at exactly 10:30). But sometimes it seems like the rules are specifying multiple events to happen simultaneously.
For example: I have a rule "sunset + motion detected + my phone active". This rule never triggers, I'm guessing because I need to trigger motion, and activate my phone at exactly sunset, or the rule won't fire. This is just a guess mind you, because there is no indication if any of these conditions are states or events.
Ideally, you would have some language to define explicitly what is intended. If I set a rule, there should be only one event, and all other conditions are states. It can't always be the last thing though, unless there is a way to specify what order the conditions appear. In my example above, I would set the motion detected event as the trigger and all other portions of the if statement would be states (the sun is down, the phone is active). You've already worked it out for time ('precisely at' is an event, 'between' is a state).
If there is a way to specify my "sunset + motion detected + my phone active" example in such a way that it works, I'd be glad to hear it.
Also: I'm just dabbling right now and I have 5 pages of rules. I need to be able to reorder them and organize them into groups.
-
For example: I have a rule "sunset + motion detected + my phone active". This rule never triggers, I'm guessing because I need to trigger motion, and activate my phone at exactly sunset, or the rule won't fire. This is just a guess mind you, because there is no indication if any of these conditions are states or events.
I agree that this is confusing. Most of the triggers are event based. I assume you want your rule to say "After Sunset", however, the Almond treats it as "At Sunset". You could try setting up a time based rule (not ideal, I know) and verify this, So, between 6 PM and 6 AM + motion detected+ Phone active do something.
Interestingly enough, based on my trials, phone Active seems to be state based. So in theory my suggestion above should work. You would still have to manually change the time to match sunset/sunrise times.
FEATURE REQUEST: Can you add Sunrise and sunset to "Anytime" and "Between" sections. Currently there is no way to create a rule that says between sunrise and sunset
Also the text is incorrect in the rules interface. It says
The order of the triggers does not matter
This is wrong. Take an example of a door that has been left unlocked from 6 PM.
Scenario 1 : If "Time is 10 PM" + "Door Unlocked" Then "Lock Door"
Scenario 2 : If "Door Unlocked" + "Time is 10 PM" Then "Lock Door"
@Securifi/Ashok - These are two separate scenarios defined by the order of the triggers. In the current rules interface, which of the above two scenarios are supported ?
-
@ d.kiran,
Scenario 1 and 2, both are supported and valid.
-
Ashok - In my case, Scenario 1 does not work.
Let us say, I come back home from office at 6 PM and I forget to lock the door. My expectation from that rule is that at 10 PM, the door should lock itself, but that does not happen.
Let me know how I can enable that behavior?
-
@ d.kiran,
If the rule is created at one particular time, then a request would surely be sent to execute the same, please do hit send logs, so that we can take a look and get back to you with an update why it is not working.
-
@Ashok - I tested it right now and it does work. I thought I was certain it did not work.
One question, this same behavior does not work, if I set the time to between 10 PM and 11 PM. It should work the same right?
-
@ d.kiran,
Yep, it would work, but we have to make sure apart from between time add one more thing (Door lock or unlock) as the trigger.
-
IPv6 stopped working
-
2.4 GHz connection consistently dropped off while 5 GHz was fine. The router needs a reboot every 2-3 days to solve this problem.
-
2.4 GHz connection consistently dropped off while 5 GHz was fine. The router needs a reboot every 2-3 days to solve this problem.
@Ashok, any thoughts on this. I'm experiencing a similar situation. Though mine is around 5-6 days this last time around. It reaches a point where the 2.4 ssid shows as available but is never able to connect.
Not sure if this was for the 2.4 or 5, but I notice it when I switch back and forth to check for any errors in logs. This was in the kernel log I believe when connecting through 2.4.
Recevied an assoc frame from 00:xx:xx:xx:xx:xx
wmi_unified_event_rx : no registered event handler : event id 0x901b
FWLOG: [52855081] RATE: ChainMask 7, phymode 6, ni_flags 0x00223006, vht_mcs_set 0x0000, ht_mcs_set 0xffffff, legacy_rate_set 0x326813d
FWLOG: [52855101] WAL_DBGID_SECURITY_UCAST_KEY_SET ( 0x0 )
FWLOG: [52855101] WAL_DBGID_SECURITY_ENCR_EN ( )
FWLOG: [52855101] WAL_DBGID_SECURITY_ALLOW_DATA ( 0x436514 )
FWLOG: [52855154] WAL_DBGID_TX_BA_SETUP ( 0x436514, 0x0, 0x0, 0x40, 0x1 )
FWLOG: [52855154] WAL_DBGID_TX_BA_SETUP ( 0x436514, 0x6, 0x2, 0x40, 0x1 )
FWLOG: [52855154] RATE: ChainMask 7, phymode 6, ni_flags 0x00223006, vht_mcs_set 0x0000, ht_mcs_set 0xffffff, legacy_rate_set 0x32681f5
FWLOG: [52855285] WAL_DBGID_TX_BA_SETUP ( 0x436514, 0x1, 0x0, 0x40, 0x1 )
FWLOG: [52855578] WAL_DBGID_TX_BA_SETUP ( 0x436514, 0x5, 0x0, 0x40, 0x1 )
-
Not sure what happened but all of a sudden 2 of my devices (z-wave plug-in and weiser deadbolt) were removed. I am the only one who knows the LCD and web password and I'm pretty sure I did not remove them. I re-added the plug-in last night without any issue... I will try to re-add the deadbolt later today.
-
@Ashok, any thoughts on this. I'm experiencing a similar situation. Though mine is around 5-6 days this last time around. It reaches a point where the 2.4 ssid shows as available but is never able to connect.
Not sure if this was for the 2.4 or 5, but I notice it when I switch back and forth to check for any errors in logs. This was in the kernel log I believe when connecting through 2.4.
Recevied an assoc frame from 00:xx:xx:xx:xx:xx
wmi_unified_event_rx : no registered event handler : event id 0x901b
FWLOG: [52855081] RATE: ChainMask 7, phymode 6, ni_flags 0x00223006, vht_mcs_set 0x0000, ht_mcs_set 0xffffff, legacy_rate_set 0x326813d
FWLOG: [52855101] WAL_DBGID_SECURITY_UCAST_KEY_SET ( 0x0 )
FWLOG: [52855101] WAL_DBGID_SECURITY_ENCR_EN ( )
FWLOG: [52855101] WAL_DBGID_SECURITY_ALLOW_DATA ( 0x436514 )
FWLOG: [52855154] WAL_DBGID_TX_BA_SETUP ( 0x436514, 0x0, 0x0, 0x40, 0x1 )
FWLOG: [52855154] WAL_DBGID_TX_BA_SETUP ( 0x436514, 0x6, 0x2, 0x40, 0x1 )
FWLOG: [52855154] RATE: ChainMask 7, phymode 6, ni_flags 0x00223006, vht_mcs_set 0x0000, ht_mcs_set 0xffffff, legacy_rate_set 0x32681f5
FWLOG: [52855285] WAL_DBGID_TX_BA_SETUP ( 0x436514, 0x1, 0x0, 0x40, 0x1 )
FWLOG: [52855578] WAL_DBGID_TX_BA_SETUP ( 0x436514, 0x5, 0x0, 0x40, 0x1 )
@pitchdarkice....I tried to change the channel of 2.4 GHz to something else and it has worked much better since. Perhaps give it a try.
-
@pitchdarkice....I tried to change the channel of 2.4 GHz to something else and it has worked much better since. Perhaps give it a try.
Thanks, I'll give it a try. Right now I had it on a scheduled reboot every day. I'll set it to a channel. If this is the case, then something is wrong with the auto function.
-
I just noticed something weird.
(https://tweakers.net/ext/f/wkEapwuhcdNsF51DEYqxSoPX/full.jpg)
(https://tweakers.net/ext/f/W665poZNDBjwVotDJDh9BVdl/full.jpg)
Why does it show DHCP disabled on the main screen??
-
@ Fire69,
Thanks, I'll give it a try. Right now I had it on a scheduled reboot every day. I'll set it to a channel. If this is the case, then something is wrong with the auto function.
Please try to check this in "incognito mode" and also by clearing the cache, let us know.
-
@ Fire69,
Please try to check this in "incognito mode" and also by clearing the cache, let us know.
Thanks, that fixed it.