0.156.0

CHANGELOG.md

@@ -1,5 +1,20 @@
 # Changelog Hiber API
 
+### 0.156 (2023-06-26)
+
+##### StatusService
+
+- Removed the outdated status service; it was no longer in use and used the old health.
+
+##### ModemService
+
+- Fix a bug where `connected_to_gateway` was not set on modem when showing child organizations.
+
+##### UserService
+
+- Invites now expire after 30 days.
+  - This has also been applied to existing invites.
+
 ### 0.155 (2023-06-19)
 
 - Refactored encryption logic to allow us to more easily improve encryption (i.e. switching algorithms) in the future

docs/html/message.html

@@ -1813,6 +1813,13 @@ <h3 id="hiber.message.MessageSelection">MessageSelection</h3>
                   <td><p>Filter message by time range. This field is required, to limit the amount of messages. </p></td>
                 </tr>
 
+                <tr>
+                  <td>modem_message_ids</td>
+                  <td><a href="#int64">int64</a></td>
+                  <td>repeated</td>
+                  <td><p>Include messages by id </p></td>
+                </tr>
+
                 <tr>
                   <td>override_time_range_with_modem_time_zone</td>
                   <td><a href="#bool">bool</a></td>

docs/md/message.md

@@ -388,6 +388,7 @@ Filter messages by modem and time sent (note that this is not the time the messa
 | ----- | ---- | ----------- |
 | modem_selection | [ hiber.modem.ModemSelection](#hibermodemmodemselection) | Select the modems to return messages for. |
 | time_range | [ hiber.TimeRange](#hibertimerange) | Filter message by time range. This field is required, to limit the amount of messages. |
+| modem_message_ids | [repeated int64](#int64) | Include messages by id |
 | override_time_range_with_modem_time_zone | [ bool](#bool) | Replace whatever time zone was specified in the start and end time with the modem time zone. This means you may get values outside of the original time range, but can be useful when requesting data for a date, for example. For example: start.textual = 2022-01-01, end.textual = 2022-02-01 would return a month of data in UTC time. When combined with this flag, it would return that month of data in the time zone of the modem, which may even be different per modem. |
 
 

event-json-examples/modem-alarm.json

@@ -27,7 +27,7 @@
       }
     ],
     "title": "Expected battery to be within 20..100%, but it is now at 15%!",
-    "description": "In organization your-organization modem AAAA AAAA has failed the following checks:\n\n- example-check-id: Expected battery to be within 20..100%, but it is now at 15%!\n\nThe error messages were produced by alarm example-identifier: example\n\nwell: example-tag, example-tag-2",
+    "description": "In organization Your Organization (your-organization) modem AAAA AAAA has failed the following checks:\n\n- example-check-id: Expected battery to be within 20..100%, but it is now at 15%!\n\nThe error messages were produced by alarm example-identifier: example\n\nwell: example-tag, example-tag-2",
     "time": {
       "timestamp": "2020-06-01T05:15:25.355Z",
       "textual": "2020-06-01T05:15:25.355Z",
@@ -61,7 +61,7 @@
     "severity": "3"
   },
   "title": "Expected battery to be within 20..100%, but it is now at 15%!",
-  "description": "In organization your-organization modem AAAA AAAA has failed the following checks:\n\n- example-check-id: Expected battery to be within 20..100%, but it is now at 15%!\n\nThe error messages were produced by alarm example-identifier: example\n\nwell: example-tag, example-tag-2",
+  "description": "In organization Your Organization (your-organization) modem AAAA AAAA has failed the following checks:\n\n- example-check-id: Expected battery to be within 20..100%, but it is now at 15%!\n\nThe error messages were produced by alarm example-identifier: example\n\nwell: example-tag, example-tag-2",
   "modem": {
     "number": "AAAA AAAA",
     "name": "AAAA AAAA",

message.proto

@@ -132,6 +132,9 @@ message MessageSelection {
     /* Filter message by time range. This field is required, to limit the amount of messages. */
     TimeRange time_range = 2;
 
+    /* Include messages by id */
+    repeated int64 modem_message_ids = 4;
+
     /* Replace whatever time zone was specified in the start and end time with the modem time zone.
      * This means you may get values outside of the original time range, but can be useful when requesting
      * data for a date, for example.