Confim alarm with API or SQL

[ggre]

Hello,

I am trying to confirm an alarm via an external supervision system.

To do this, I found an Events API that would confirm an alarm but I can't get it to work. I manage to generate a Token with the RequestType "Events", but when I send the confirm command with Events.ashx, it gives me an error.
Do you know how to use this API?


Then, I noticed that there was possibility to confirm an alarm directly in SQL. I did an insert in the Confirms table and an Update in the AlarmItems table, but I don't know how to generate the Hash column. Is there a way to generate this Hash code via a script? Without this Hash, the alarm line in the RMS turns red.

For integration into the supervision system, the solution with SQL is preferred.

Thanks in advance for your feedback

[James]

Hi,

You cannot extract the events via the API, only historical measurement data: https://service.rotronic.com/manual/data-request.html.

There is no way to confirm the alarm directly within the SQL database. Any direct changes in the SQL database are manipulations and will be shown as such within the RMS interface.

For integration into the supervision system, if you want to extract data via the SQL database, then we can give you the table overview.

Please reach out to rms@rotronic.ch for more details.

Regards,
James

[Beenests]

You need to reach the destination to complete the level in geometry dash 3d

[lorde]

Are there any database triggers, stored procedures, or views related to alarm confirmation that might generate or validate the Hash? Geometry Dash Lite

[mikehalloween]

When an API token works for the Events endpoint but the confirm call fails, it’s often a mismatch in the payload signature—worth logging the full request JSON to spot tiny typos. I sometimes draft example payloads in AI Cartoon Generator (oddly handy for quick flow diagrams), then copy the text field-for-field into Postman.

[mikehalloween]

If you fall back on SQL, first check whether the Hash column is created via an MD5 or SHA algorithm that combines AlarmID + Timestamp + a secret key; running a test hash generator in Character Headcanon Generator (it supports simple scripting) helped me crack a similar pattern once.

[mikehalloween]

Once you decipher the hashing logic, whip up a small T-SQL function (or CLR if it’s SHA-256) and test its output; a quick sanity check on the visual layout of your confirm dashboard via AI Beauty Rating can catch alignment glitches that slip through data-only tests.

[mikehalloween]

Before updating AlarmItems, confirm there isn’t an audit trigger that expects the hash at insert time—dropping a screenshot of the table schema into AI Describe Image can give you a quick text description of all column defaults so you don’t miss hidden constraints.

[mikehalloween]

If hashes turn rows red in RMS, try capturing a “good” confirm row, export it as CSV, and compare byte-for-byte to your insert. I’ve used AI Image Extender to expand side-by-side diff screenshots when presenting issues to teammates—it keeps the relevant columns visible.