question

+1 for this bug.

After adding an alarm via API, I tried to use PUT to edit the value per the official API bundle. The API response shows as if it is successful with the returned data showing the new edited values, but if I view the alarm setup in the VRM UI it still has the old value. The value specifically was for the lowhysteresis number.

The challenge is that the API doesn't seem to have a DELETE for an alarm rule so I'm stuck.

@Guy Stewart (Victron Community Manager)

Thanks for the report, I'll pass it up to VRM team to investigate.

+1 for this bug

Hi All,

Thanks for your bug reports, the VRM team has just applied a fix and it should now be resolved.

Not quite yet... it's getting confused between notifyAfterSeconds and NotifyAfterSeconds-

Request content

{ "idDataAttribute": 442, "instance": 6, "AlarmEnabled": 1,

"NotifyAfterSeconds": 84000,

"highAlarm": 9000, "highAlarmHysteresis": 3000, "lowAlarm": 1, "lowAlarmHysteresis": 5}

Response:

• dataCollection

  • idDataAttributeLimit

    110342

  • idSite

    199439

  • idDataAttribute

    442

  • instance

    6

  • lowAlarm

    1

  • lowAlarmHysteresis

    5

  • highAlarm

    9000

  • highAlarmHysteresis

    3000

  • AlarmEnabled

    1

  • NotifyAfterSeconds

    86400

  • alarmEnabled

    1

  • notifyAfterSeconds

    84000

Was this fixed?