Skip to content

Code to connect and control alarms by PIMA.

active 2023-10-262026-06-10 (UTC)

Complete coverage26,387 / 26,387 hourly files (100%) · 2 absent upstream2023-08-152026-08-18 (UTC)
Events
52
Pushes
6
Pull requests
3
Issues
9
Stars
13
Forks
6

Activity over time

Daily event counts in the loaded window

Line chart, 959 days from 2023-10-26 to 2026-06-10. Pushes: 6 total, peak 4 in a day. Pull requests: 3 total, peak 2 in a day. Issues: 9 total, peak 1 in a day. Comments: 14 total, peak 4 in a day. Stars: 13 total, peak 4 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
deiger11623
ohadlevy7005
maorcc7013
mizrachiran3002
docoboao1000
alws341001
carferrer1000
omermodawi31-sketch1000

Recent activity

Latest issues, pull requests and releases

  • Issue#36omermodawi31-sketch2026-06-10 21:13
    omer alarm pro
  • Issue#34docoboao2025-08-26 06:16
    Having issues with net4pro - any specific details on using that rather than serial cable ?
  • Issue#33ohadlevy2025-05-29 16:29
    sync pima system clock
  • Pull request#31deiger2025-03-23 13:02
  • Issue comment#31deiger2025-03-23 13:02
    Improve error handling and recovery mechanisms in PIMA alarm communication - fixes #30
  • Issue comment#31ohadlevy2025-03-23 12:24
    Improve error handling and recovery mechanisms in PIMA alarm communication - fixes #30
  • Issue comment#31deiger2025-03-23 12:20
    Improve error handling and recovery mechanisms in PIMA alarm communication - fixes #30
  • Issue comment#30ohadlevy2025-03-23 12:05
    Exception raised by Alarm - often failure of communication
  • Issue comment#31ohadlevy2025-03-19 10:13
    Improve error handling and recovery mechanisms in PIMA alarm communication - fixes #30
  • Issue comment#30ohadlevy2024-12-25 16:12
    Exception raised by Alarm - often failure of communication
  • Issue comment#30maorcc2024-12-25 16:10
    Exception raised by Alarm - often failure of communication
  • Issue comment#30ohadlevy2024-12-25 15:33
    Exception raised by Alarm - often failure of communication
  • Issue#30ohadlevy2024-11-17 09:19
    Exception raised by Alarm - often failure of communication
  • Issue comment#29maorcc2024-09-14 16:08
    What is "Outputs"?
  • Issue#9maorcc2024-09-14 15:44
    pima.service hangs indefinitely after few days of running
  • Issue comment#29maorcc2024-09-14 15:39
    What is "Outputs"?
  • Issue#29maorcc2024-05-27 10:05
    What is "Outputs"?
  • Issue comment#28mizrachiran2024-04-26 08:01
    Error "Not enough data in channel" on script start
  • Issue comment#28alws342024-04-22 13:14
    Error "Not enough data in channel" on script start
  • Issue#28mizrachiran2024-04-20 12:32
    Error "Not enough data in channel" on script start
  • Issue comment#18mizrachiran2024-04-10 07:08
    Pima Hunter Pro 144 - Exception after arming - Not enough data in channel
  • Issue#27carferrer2024-02-24 17:04
    Too long to update sensor
  • Pull request#26deiger2023-12-17 18:45
  • Issue comment#26deiger2023-12-17 18:45
    Set MQTT discovery entity name to None to solve #25
  • Pull request#26maorcc2023-12-17 17:14

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 13 stars here means stars gained during the window, not the repo's star count.