Device Lables

Follow

Andy brown

• February 10, 2018 12:40

Not sure this has ben mentioned, but couldn't find it in a search.  Ive renamed several devices, which is great.  However, the original name appears in the alarm section, so I have to try and figure out what was the original name or go back and look up the MAC address etc to find out which device was activating the alarm.

1

• 

  Firewalla

  • February 10, 2018 19:37

  Andy, are the alarms happen before or after you did the name change?

  0

  Comment actions Permalink
• 

  Andy brown

  • February 11, 2018 09:15
  • Edited

  These alarms are after I have changed the names. 

  By the way what a fantastic device, really impressed, this issue is minor and have no other problems at all.  

   

  Thanks guys..

  0

  Comment actions Permalink
• 

  Firewalla

  • February 11, 2018 18:14
  • Edited

  Andy, we will log a bug on this.    The device name on alarm should match that of the device after the device change name.  The alarm happens after device name change. 

  The name change may happen a bit slow, let us know if future alarms are changed or not.  It will help us fix the bug faster

  1

  Comment actions Permalink
• 

  Ken Shibata

  • February 12, 2018 01:30

  I too am seeing the same issue of the alarms referencing the old labels even after being renamed. Also, renaming is not consistently set, I have gone through my entire device list renaming to a more friendly/meaningful label, only to find the labels back to the original device name...

  1

  Comment actions Permalink
• 

  Ken Shibata

  • February 12, 2018 02:05

  I've downloaded the Android app 1.70 (76) and the renaming works as expected. The iOS app is still hit or miss. Using iOS 11.2.5 (15D60) on both iPadPro/iPhone6, Firewalla iOS app ver 1.24 (19)

  0

  Comment actions Permalink
• 

  Support Team

  • February 12, 2018 07:37
  • Edited

   Hi Ken,

   

  Label bug is confirmed and fixed in code, will release firmware patch to production in a few days.

   

  Thanks for helping find the bug, it was introduced in latest release, deployed 5 days ago.

   

  Melvin

  0

  Comment actions Permalink
• 

  Firewalla

  • February 15, 2018 07:13

  bug fix is released, your firewalla should already be updated with the fix.

  0

  Comment actions Permalink
• 

  Andy brown

  • February 16, 2018 06:55

  Wow, in 6 days after posting a possible issue, you responded to a customer, investigated the issue, found a problem, fixed it, sent out an update and informed the customer.   If only all other companies followed suit solving customer issues......

   

  Thanks, 

   

  Andy

   

  0

  Comment actions Permalink

Please sign in to leave a comment.