Feature #312

Clean up dSM in dSS

Added by Nina Meier almost 2 years ago. Updated 7 months ago.

Status:Closed Start date:02/17/2010
Priority:(P3) Normal Due date:
Assignee:Miguel Rodriguez % Done:

100%
Category:-
Target version:0.8.0-rc1
Severity:Normal
Story points-
Velocity based estimate-

Description

Remove old dSM from list.

Related issues

related to Feature #264: Webinterface function to cleanup zone and circuit objects Closed 01/05/2010

History

#1
Updated by Sergey Bostandzhyan almost 2 years ago

  • Assignee changed from Sergey Bostandzhyan to Nina Meier

Please provide detailed information.

#2
Updated by Miguel Rodriguez almost 2 years ago

  • Status changed from New to Assigned
  • Assignee changed from Nina Meier to Sergey Bostandzhyan

+ Delete appartment.xml
+ Rescan bus 485

#3
Updated by Patrick Stählin almost 2 years ago

Deleting apartment.xml makes no sense as it will be regenerated anyway...

#4
Updated by Nina Meier almost 2 years ago

  • Status changed from Assigned to Feedback
  • Assignee changed from Sergey Bostandzhyan to Miguel Rodriguez

#5
Updated by Michael Troß almost 2 years ago

  • Status changed from Feedback to Assigned
  • Assignee changed from Miguel Rodriguez to Sergey Bostandzhyan

Patrick, the objective of this ticket is to synchronize the dSS objects with the attached hardware, as the related ticket states: cleanup zone and circuit objects.

Background of this feature is the fact that the dSS constantly collects the dSM and Zone ID's of an installation. This leads to dead circuit and zone objects, either because hardware has been replaced or is just powered off. The user interface shows an outdated view of the system and the user cannot distinguish between both states.

It makes no sense to remove apartment.xml as a file, but rather delete the orphan zone and circuit objects. If the current state of the datamodel needs to be synchronized and updated in this case, a ds485 bus rescan may be advisable.

#6
Updated by Sergey Bostandzhyan almost 2 years ago

  • Status changed from Assigned to Feedback
  • Assignee changed from Sergey Bostandzhyan to Michael Troß

I thought there was a requirement that we do not forget old devices? That's what the isPresent flag is for, right?
So just to be sure that I understand this correctly: do you always want an automatic cleanup, where all !isPresent devices are removed, or a possibility to trigger cleanup via the JSON API?

Btw, since we have the last seen timestamps we could also implement something like "remove all that are older than xxxx".

We should also ask Nina where she would like to have that in the installer interface, but first I'd like the confirmation that my understanding of this feature is correct.

#7
Updated by Miguel Rodriguez almost 2 years ago

  • Status changed from Feedback to Assigned
  • Assignee changed from Michael Troß to Sergey Bostandzhyan
  • Target version changed from 0.8.0-alpha1 to 0.8.0-rc1

The isPresent flag is only given for devices that are available in the bus

Please remove all dSM's not connected at the moment the function is called.

#8
Updated by Sergey Bostandzhyan over 1 year ago

Added two API calls: removeMeter(dsid) and removeInactiveMeters
Added removeMeter entry to dSM context menu.
Added removeInactiveMeters button to dSM overview toolbar.

Merge requests submitted.

#9
Updated by Sergey Bostandzhyan over 1 year ago

  • Status changed from Assigned to Resolved
  • Assignee changed from Sergey Bostandzhyan to Miguel Rodriguez
  • % Done changed from 0 to 100

Merged into mainline.

#10
Updated by Miguel Rodriguez over 1 year ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF