Any feedback related to R089

[derrikn]

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.

[mikeys63]

@ 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 ?

[Ashok]

@ mikeys63,

Any updates for the R089 Web Socket API ?

It is updated, please check and let me know, if there is any issue.

[rf134a]

@ 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.

[tonythetech]

  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.

[d.kiran]

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 ?

[Ashok]

@ d.kiran,

Scenario 1 and 2, both are supported and valid.

[d.kiran]

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?

[Ashok]

@ 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.

[d.kiran]

@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?

[Ashok]

@ 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.

[mymaestro]

IPv6 stopped working

[greendew]

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.

[pitchdarkice]

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 )

[engr.jpc]

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.