Securifi Community Forum
Securifi Products => Almond+ => Topic started by: mr23 on May 23, 2015, 02:03:39 pm
-
Installed R076.
Using: https://connect.securifi.com/home
Lamp percentage of illumination are all NaN%. Lamp states of On/Off do not stay in sync with the lamps.
Last release of Almond+ Android App launches (HTC Sensation), cloud is checked, displays incorrect lamp On/Off state, and all say 0% illumination. Turn all lamps on. Adjust lamp level higher. No display change, even after relaunch. Try to change On/Off state, "Could not connect, please try again". Hit slider at 71%, lamp turns on, app gui says "could not connect, please try again" and back to 0%. https://connect.securifi.com/home still says the same thing, NaN%. Turn lamp off via Sensation, "Could not Connect"... but lamp turns off, connect.securifi says On, NaN%. Cloud still checked on Sensation app.
Updated HTC Sensation to the latest release of the app, open app, it gets as far as refreshing devices (toast) and it crashes. Probably the NaN%.
'Beta' Almond+ Android App fails to launch (1st Gen Kindle, Cyanogenmod). I'd guess it's the NaN's found in place of the actual lamp percentage illumination. Android log below
Timeline: Activity_launch_request id:com.securifi.almondplus time:4199416
START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.securifi.almondplus/.MainActivity bnds=[360,701][480,855]} from pid 691
Permission Denial: broadcasting Intent { act=com.android.launcher3.action.LAUNCH flg=0x10 (has extras) } from com.cyanogenmod.trebuchet (pid=691, uid=10013) requires com.google.android.launcher.permission.RECEIVE_LAUNCH_BROADCASTS due to receiver com.google.android.googlequicksearchbox/com.google.android.search.core.icingsync.ApplicationLaunchReceiver
Permission Denial: receiving Intent { act=com.android.launcher3.action.LAUNCH flg=0x10 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.search.core.icingsync.ApplicationLaunchReceiver requires com.android.launcher3.permission.RECEIVE_LAUNCH_BROADCASTS due to sender com.cyanogenmod.trebuchet (uid 10013)
Switching descriptor 32 to /dev/null
Switching descriptor 9 to /dev/null
Start proc com.securifi.almondplus for activity com.securifi.almondplus/.MainActivity: pid=6864 uid=10077 gids={50077, 3003, 1028}
handleBindApplication:com.securifi.almondplus
setTargetHeapUtilization:0.75
setTargetHeapMinFree:524288
Registering default exceptions handler
Flushing...
Registering default exceptions handler
Enabling debug mode 0
recvfrom(ctrl_iface): Try again
Displayed com.securifi.almondplus/.MainActivity: +1s285ms (total +1m17s369ms)
Timeline: Activity_windows_visible id: ActivityRecord{425872c0 u0 com.securifi.almondplus/.MainActivity t8} time:4200797
Timeline: Activity_idle id: android.os.BinderProxy@41e5a530 time:4200962
Timeline: Activity_launch_request id:com.securifi.almondplus time:4201443
START u0 {cmp=com.securifi.almondplus/.AlmondPlusActivity} from pid 6864
Could not find method android.app.Activity.finishAfterTransition, referenced from method android.support.v4.app.FragmentActivity.onBackPressed
VFY: unable to resolve virtual method 17: Landroid/app/Activity;.finishAfterTransition ()V
VFY: replacing opcode 0x6e at 0x000e
Could not find method android.content.Context.getDrawable, referenced from method android.support.v4.content.a.a
VFY: unable to resolve virtual method 202: Landroid/content/Context;.getDrawable (I)Landroid/graphics/drawable/Drawable;
VFY: replacing opcode 0x6e at 0x0006
Could not find method android.view.View.getTransitionName, referenced from method android.support.v4.app.l.a
VFY: unable to resolve virtual method 2854: Landroid/view/View;.getTransitionName ()Ljava/lang/String;
VFY: replacing opcode 0x6e at 0x0021
Unable to resolve superclass of Landroid/support/v4/app/ao; (484)
Link of class 'Landroid/support/v4/app/ao;' failed
Could not find class 'android.support.v4.app.ao', referenced from method android.support.v4.app.l.a
VFY: unable to resolve new-instance 185 (Landroid/support/v4/app/ao;) in Landroid/support/v4/app/l;
VFY: replacing opcode 0x22 at 0x0168
Could not find method android.view.View.getTransitionName, referenced from method android.support.v4.app.l.b
VFY: unable to resolve virtual method 2854: Landroid/view/View;.getTransitionName ()Ljava/lang/String;
VFY: replacing opcode 0x6e at 0x0014
Unable to resolve superclass of Landroid/support/v4/app/ao; (484)
Link of class 'Landroid/support/v4/app/ao;' failed
DexOpt: unable to opt direct call 0x03ce at 0x16a in Landroid/support/v4/app/l;.a
Thread[main,5,main]: int configuration name not recognized: ga_dispatchPeriod
Shutting down VM
threadid=1: thread exiting with uncaught exception (group=0x419b3ce0)
recvfrom(ctrl_iface): Try again
FATAL EXCEPTION: main
Process: com.securifi.almondplus, PID: 6864
java.lang.NumberFormatException: Invalid int: "false"
at java.lang.Integer.invalidInt(Integer.java:137)
at java.lang.Integer.parse(Integer.java:374)
at java.lang.Integer.parseInt(Integer.java:365)
at java.lang.Integer.parseInt(Integer.java:331)
at com.securifi.almondplus.sensor.a.d.a(SourceFile:17)
at com.securifi.almondplus.sensor.a.a.a(SourceFile:25)
at com.securifi.almondplus.sensor.a.c.a(SourceFile:92)
at com.securifi.almondplus.sensor.b.getView(SourceFile:1053)
at android.widget.AbsListView.obtainView(AbsListView.java:2255)
at android.widget.ListView.measureHeightOfChildren(ListView.java:1263)
at android.widget.ListView.onMeasure(ListView.java:1175)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1450)
at android.widget.LinearLayout.measureVertical(LinearLayout.java:695)
at android.widget.LinearLayout.onMeasure(LinearLayout.java:588)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at android.view.View.measure(View.java:16521)
at android.widget.LinearLayout.measureVertical(LinearLayout.java:870)
at android.widget.LinearLayout.onMeasure(LinearLayout.java:588)
at android.view.View.measure(View.java:16521)
at android.support.v4.widget.DrawerLayout.onMeasure(SourceFile:851)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at com.android.internal.widget.ActionBarOverlayLayout.onMeasure(ActionBarOverlayLayout.java:327)
at android.view.View.measure(View.java:16521)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5125)
at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)
at com.android.internal.policy.impl.PhoneWindow$DecorView.onMeasure(PhoneWindow.java:2552)
at android.view.View.measure(View.java:16521)
at android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:1915)
at android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:1109)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1291)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:996)
at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5603)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:761)
at android.view.Choreographer.doCallbacks(Choreographer.java:574)
at android.view.Choreographer.doFrame(Choreographer.java:544)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:747)
at android.os.Handler.handleCallback(Handler.java:733)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5146)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
at dalvik.system.NativeStart.main(Native Method)
Force finishing activity com.securifi.almondplus/.AlmondPlusActivity
Force finishing activity com.securifi.almondplus/.MainActivity
Sent logs, "AndroidApp NaNs". "D338".
Apps were working before upgrade to R076.
With R076, http://10.10.10.254/cgi-bin/luci displays NaN% for illumination level. On/Off turns lamp on/off, but ,light level is stuck at 0 so it doesn't *really* turn on.
Interestingly, my 'local control' app http://forum.securifi.com/index.php/topic,2527.0.html (http://forum.securifi.com/index.php/topic,2527.0.html) still functions correctly. Direct link in my sig.
-
" Glad" :-\ :-\ :-\ to see I am not the only one. Updated to 076 and lost 1/2 my sensors in Android app and even trying to scroll down to see more than the first 5 sensors crashes the app.
The not reading the proper state is not new,nor limited to just the app. It is across the all controls, LCD Web UI, Lan UI. I have had that issue since 070 and nothing has changed. At first I thought it was just the CREE bulb, but then with 072 the virus spread to all my bulbs. Then the Leviton switches if they are turned on or dimmed at the switch. The only thing currently reporting reliably are the Schlage locks.
-
" Glad" :-\ :-\ :-\ to see I am not the only one. Updated to 076 and lost 1/2 my sensors in Android app and even trying to scroll down to see more than the first 5 sensors crashes the app.
Let me guess, you do not have any multilevel switches aka dimmable lamps in the first 'page' (top/visible of scrollable) of devices.
Probably related to this bug fix:
> Bug Fix: Multilevel On Off switches not taking correct value.
-
Actually almost all my sensors are multi-level swiches, either Leviton wall dimmers or GE bulbs. App shows first 5. Web UI shows lights that are on as off and any attempt to turn the light on/off or change dimmer lever results in nan% or "updating status" . " can not connect please refresh " through LAN webui.
-
I am getting similar results on my dimmers;
1. Leviton - it was behaving badly; only updating when using the slider. I uninstalled/reinstalled the switch. Now it responds, albeit very slowly 5-10 seconds later. It does not keep its state.
2. Wink/link bulbs - dead, not responding. Uninstalled/reinstalled. Now I can turn them on with slider. Turning them off reports "On 0%".
3. GE dimmer (fan). Works fine; albeit slow (2-3 seconds)
4. Android app crashes immediately.
-
Using LED screen, I was able to turn lights off/on , but it is not reading the proper state and it took 6 taps to get the light to turn off and another 3 before it turned back on. Screen read as off 0% and still does.
-
And my SmartACSwitch voltage/current/etc reports don't update and doesn't turn off/on via luci or connect.securifi.
Update: I removed this device, reset the device, and repaired it (took 2 tries), then it operated.
-
Leviton in wall dimmer is working and showing proper state. Response time to any changes is 3-4 seconds rather than the normal 0.2-0,4 seconds.
Schlage lock is showing properer state and working however response time to any action is 4-5 seconds.
Peanut plug unresponsive , but at least does not crash the app.
All Ge and Cree bulbs just crash the app with any attempt to select them.
Issues like these are exactly what I was talking about in my comment in the " disappointed " thread. How can I possibly expand A+ to be a fully automated home control/alarm system when it can not even be relied on to turn on a porch light at 7pm , or tell me I left the cellar lights on ?
-
Where to begin...
All my Wink bulbs are screwed up. They report "Off" when they are on and then will not connect. My Aeon Labs Smart Energy switch which worked before is now showing as not supported. So far the Peanut Plug and the thermostat appear to be OK.
App crashes instantly and is now useless.
I bought this to use for Home Automation and if it doesn't work dependably then I feel like I wasted a lot of money on it and sensors.
Losing faith quickly...
-
Please post a link to 73 so I can go back to it.
-
Upgraded to R076. Immediate Android app crash on first toggle of a Cree bulb. Android application would not launch properly after that--repeated crashing. The Almond+ web interface was unresponsive for turning the bulbs on and off also.
Solution;
- Downgraded firmware back to R072.
- After downgrading back to R072, any sensors which had been toggled while operating under R076 still were not working properly and the Android app was still crashing
- Under R072 I removed any sensor that had been touched in the R076 interface and then re-added back under R072. Android app is working again now and the all appears to be functioning back to how it was under R072 prior to the R076 upgrade.
-
Sorry for the stupid question, but how do you go back to 72?
-
Under the web interface of the Almond+, on the "Router" tab, there is a "Software" button which will take you to a page allowing you to select a firmware file to update the software and flash the Almond+ with that firmware file.
The R072 firmware file can be downloaded here: https://www.dropbox.com/s/5ustm4u2jcnxqkx/AP2-R072-L009-W016-ZW016-ZB005?dl=0
(Note to Securifi Admins -- I will remove this link to R072 if asked. In the meantime and until Securifi has a chance to respond to the problems with this upgrade, it seems courteous to customers to post it so that those suffering a significantly degraded to non-functional Almond+ performance after the upgrade to R076 can try to recover functionality back at R072 if they wish).
-
My Everspring dimmers seems to be working ok. They properly synchronise state and brightness between Z-wave controll and manual override.
Great work there.
My qubino flush dimmer doesn't do that though, so some work is still needed.
My Belkin WeMo dimmable bulb gets a NaN in the Web UI and always a 0% brightness in the current iOS app. It still works but the UI functionality is worse than before.
All sensors mentioned were added under the new firmware.
-
Thank you very much johnny. I am bummed because I was on 073 and it was working and I really like the Home/Away as a trigger. Never should have updated until I was sure about 076. Two bad releases in a row does not bode well.
-
Even after going back to 072 the Android app crashes. Uninstalled and reinstalled with no success. Web UI does not control GE bulbs either.
-
Even after going back to 072 the Android app crashes. Uninstalled and reinstalled with no success. Web UI does not control GE bulbs either.
In the thread further below it is recommended to remove and re-add any sensor 'touched' while in R076.
I went back to 072, but my multilevel switch lamps are all reporting NaN% in the web ui.
So i ssh -l root 10.10.10.254 into the router
cd /tmp
vi DeviceList.xml
/SWITCH MULTILEVEL
found that value that should have been an int between 0 and 255 was set to true or false.
<LastKnownValue Index="1" EndPoint="1" Name="SWITCH MULTILEVEL" Type="Byte">true</LastKnownValue>
changed each one to some other value, like 55
<LastKnownValue Index="1" EndPoint="1" Name="SWITCH MULTILEVEL" Type="Byte">55</LastKnownValue>
:w
:q
Then refreshed my browser and the multilevel switch (dimmable) lamps were back to normal. [Update: well, functionality is restored, but the %display is stuck at 21% (55/255); probably stuck with removing and readding all devices, but going to hang tight since my light control app is working fine.]
The beta version of Almond App even after cache clearing still won't launch. That's odd. Cleared/Uninstalled/Reinstalled. Same.
-
Same is happening with my GE Link bulbs.
-
Wow... with all these comments and issues with 076 there is still not a single comment or explanation from Securifi. Hello? This release basically deleted HA from my Almond+ and nothing?
-
Wow... with all these comments and issues with 076 there is still not a single comment or explanation from Securifi. Hello? This release basically deleted HA from my Almond+ and nothing?
There's a weak response over at beta firmware.
http://forum.securifi.com/index.php/topic,3321.0.html (http://forum.securifi.com/index.php/topic,3321.0.html)
For those without beta forum access, I copied the response here:
Ashok: That is how generally we release the full firmware first by making sure beta firmware is released to the beta group. If you check the release notes, there is not much change compare to R075 to R076. Except resolving the status of Aeon Labs (DSC06106) smart energy switch. I am positive there is something else which could be causing the issue. I have already escalated it to our team and waiting for their response. Thank you for helping us with the beta firmware.
-
This is fairly insignificant compared to everyone's problems, but R076 introduced timezone sync and it uses old timezone for Moscow, one hour ahead (GMT+4). It's been GMT+3 w/o any kind of DST for about a year now. For now as a workaround you can set Minsk timezone in OpenWRT and then just not touch the clock app in LCD.
-
It always says 0 connected users in status. Also in the app.
-
Okay, granted this is a holiday weekend here in the US, but AFAIK, there in no corresponding holiday in Taiwan and India. This leave there being no justifiable excuse why there has not been a single response from Securifi in the 48 hours since this firmware release that killed all HA function. This was a general release, not a " hey here's a beta if you want to try ,but we make no promises it will work " release .
073 was so good that it was pulled within a few hours and a link to go back to the more stable 072 was posted. I never even saw 074 or 075, so I assume they were just skipped over. Now 076 is pushed out via LCD and it immediately kills everything and Securifi is silent.
Anybody else get a sinking feeling that this ship is going down and we are the rats too slow and stupid to get off ? Since my Wink and Link hubs were in a drawer, I think I am safe in assuming they should not have been effected by the OTA firmware push that killed so many of those hubs.
Maybe it is time for A+ and Wink to trade places ,and for me to give some serious thought to why I keep wasting time and money supporting these start-ups instead of just spending the money to invest in hardware that has been proven. The saving grace is that most sensors are not brand specific and will work with any hub.
-
@ All,
We regret the inconvenience caused and apologies for the late response. I was just waiting for a proper information or resolution from our team. It seems like there is an issue with the Multi Level switch with our new firmware R76 and current Andriod app that is the reason, it was crashing. However, this has been taken care with our new Andriod app which is already released and users may get the update any time. Meanwhile, we can also download the apk file attached in zip format which can be unzipped and installed on any andriod device.
In order to make it even more simple, I am sharing the link through which we can download the latest update of Andriod app. Please click on the following link:
https://drive.google.com/file/d/0B6cFyWWSXjqEbndFaWdoN3lBOEk/view?usp=sharing
-
If it is just an issue with the Android app, then why are the sensors also not working via LCD nor web UI ?
@ All,
We regret the inconvenience caused and apologies for the late response. I was just waiting for a proper information or resolution from our team. It seems like there is an issue with the Multi Level switch with our new firmware R76 and current Andriod app that is the reason, it was crashing. However, this has been taken care with our new Andriod app which is already released and users may get the update any time. Meanwhile, we can also download the apk file attached in zip format which can be unzipped and installed on any andriod device.
In order to make it even more simple, I am sharing the link through which we can download the latest update of Andriod app. Please click on the following link:
https://drive.google.com/file/d/0B6cFyWWSXjqEbndFaWdoN3lBOEk/view?usp=sharing
-
@ rldreams,
We don't have any issues like that so far, you are not able to access multiple sensors or only one sensor and also are they Zigbee or Z-wave. May be you can send logs (Help-->Send Logs), so that I could request my team to look and see what exactly is going on.
-
Updated to the latest version of the Android app... Updated back to 076... tried to turn on a GE bulb and CRASH! Now I cannot even add the bulb back (I get an error on the LCD..."association failed"). I reset the bulb three times and even moved it closer but no dice. Getting pretty darn upset with these updates that break more than they add. Looks like I am headed back to 072, and then shopping for a Smartthings hub. I already updated my Amazon review of the Almond+ to reflect the recent failures.
-
Updated to the latest version of the Android app... Updated back to 076... tried to turn on a GE bulb and CRASH! Now I cannot even add the bulb back (I get an error on the LCD..."association failed"). I reset the bulb three times and even moved it closer but no dice. Getting pretty darn upset with these updates that break more than they add. Looks like I am headed back to 072, and then shopping for a Smartthings hub. I already updated my Amazon review of the Almond+ to reflect the recent failures.
I would guess you'll have to remove and readd your sensors, too. Let us know how it goes for you. No sense all of us going through the same pain again. Thanks.
-
@ rldreams,
We don't have any issues like that so far, you are not able to access multiple sensors or only one sensor and also are they Zigbee or Z-wave. May be you can send logs (Help-->Send Logs), so that I could request my team to look and see what exactly is going on.
Ashok, did you read my original post (reply #1) in this thread? It includes a posted logs reference, as well as brief descriptions of issues initially found in the cloud web (connect.securifi), the local web (luci), and the apps. Were my logs useful to the team?
I know I've read whether in this thread or others of people describing broken function web sensor interfaces, and I'm sure I did too. Did you read my reply #17, below?
> Bug Fix: Multilevel On Off switches not taking correct value.
What code was touched to make this fix? A+FW? App(s)? Web UI? All?
-
This time I only used one sensor (GE bulb) because of the previous fiasco. Now I cannot even add the bulb back after reverting back to 072. I just keep getting an "association failed" message.
-
@ rldreams,
We don't have any issues like that so far, you are not able to access multiple sensors or only one sensor and also are they Zigbee or Z-wave. May be you can send logs (Help-->Send Logs), so that I could request my team to look and see what exactly is going on.
Log sent, I entered description 3 times and when "done" the window returned to blank asking me to enter optional description. Z-wave Schlage locks are working/ reporting fine, ( although to be honest I haven't played with them at all, but they are triggering the lights as they should) all Zigbee devices including Pnut are not registering proper state. All robots for ZigBee lights are hit/miss 1/2 the lights shut off this AM as scheduled, the others were still on.
LCD shows all devices as " Off 0%" LAN Web UI shows as " OFF dimmer level NAN% " even thought lights are very clearly on .
https://plus.google.com/u/0/+RandyMartinRlDreams/posts/8LQf2eJGud6?pid=6152839220110782050&oid=117038646025391394905 (https://plus.google.com/u/0/+RandyMartinRlDreams/posts/8LQf2eJGud6?pid=6152839220110782050&oid=117038646025391394905)
-
@ rldreams,
Thank you for taking time and providing the information and sending the logs. While I try to check with our team, could you please remove and add one sensor may be Peanut plug and let us know the status.
-
Made sure the Android app was up to date and went back to 076 AGAIN to see if I could add a GE bulb. No go... just "Association Failed" on two different bulbs. Now I have no control over two of the six bulbs and I am afraid to even turn the others on.
-
Made sure the Android app was up to date and went back to 076 AGAIN to see if I could add a GE bulb. No go... just "Association Failed" on two different bulbs. Now I have no control over two of the six bulbs and I am afraid to even turn the others on.
Exactly my issue.
Removed and re-paired one of the GE bulbs. It reads off 99% when on and on 0% when off controlled via LCD . App still crashing , LAN web UI reads on 99% when off, attempted to turn it on got " ON, NaN% " and " refresh and retry" light did not do anything.
I am about to the point that if I need to go around the house collecting all my Zigbee devices to re-associate them with A+ again, I might as well just associate them with the Wink or Link hubs and see if they have made any measurable progress on stability in the last few months.
-
After updating to R076 my 2 GE bulbs are no longer working with iOS apps nor web UI. They can only be controlled on LCD UI. I tried unpairing and pairing both of them again but I'm still experiencing the same issue. :(
-
I'm still on 72 and my peanut does not show any power. (0.000W/0.000A/0.000V)
This coupled with plum-sack performance on wifi (so bad, I disabled it and am now solely using a UniFi AP) and bugs all around, I'm not sure how much more of this I can take. Considering I'm in the SW world, this is shameful.
-
After removing and re-pairing 1 GE Zigbee bulb as you requested, A+ is now also no longer reading the proper state of Schlage ZW locks either. Amazingly enough though the lock is still working as a trigger to turn on/off the light even though I have no control of the light or lock via app, LCD or LAN WebUI . It is not the bulb I removed and re-paired .
I really do have to wonder how anybody could use this as the center for a complete automation and alarm system
-
@ All,
I just had a discussion with our team and every one is working to figure out the issue with R76 and Andriod app. Most probably by end of this week, we would have a proper solution on this. We regret the inconvenience caused, rest be assured taking care of this issue is our top most priority now and would get back once I have any useful update.
-
Just getting this topic back to the top since the issues have not yet been resolved. End of the week is...very soon.
-
I would like to hear that Securifi tested A+ from R072 with a multitude of sensor types (esp ones complained about with R076) upgraded to the new upcoming release (assumed to be R077 or higher) shortly. Please don't make us all pay the price again.
-
I don't have android, but now my Cree bulbs are all messed up. It is showing NaN%, and I can't control them via web UI, and they are really weird via touchscreen, and all my rules broke.
This might be it. I'm out, and buying a Smart Things hub. You guys are incompetent at planning, development, testing, and customer interaction. Rare to see all of those together.
-
R76
Most recent Android App
Most recent IOS App
Added GE Link A19 (clear) bulb. Had to Turn bulb on/off 5 times to put it in paring mode, it associated fine.
Bulb turns on/off/dims properly. All other sensors working properly. (doors, motion from securifi)
Turned bulb off manually, experienced similar issues as described in this thread. Incorrect bulb status, no response when using app.
Rebooted router, powered light bulb on/off.
Current GE Link A19 Status:
Using Android App
Bulb shows always on. (perhaps connection status, not bulb status?) On/Off Switch turns bulb Off, but not On.
I am able to turn bulb on using Dimmer Control.
Perhaps On/Off multilevel switch is not correctly toggling levels, Max brightness is showing as 99%, not 100%.
Using Web Interface
Able to turn bulb Off, but NOT On
Dimmer slider not working (Safari)
Sensor window asked if I wanted to Save Data (meaning something had changed) and it appended the IP of the Router to the Name Field (i.e. Light1http://10.10.10.254)
-
Added a CREE Bulb, all the same issues as the GE Link A19 bulb.
-
Since R076, the multi sensor (motion, light, humidity and temp) is no longer supported? Works fine on the A+ LCD, but the rule busted, and the local web interface and iOS app no longer recognize the sensor.
Add it to the list, boys.