Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Русский
  3. ioBroker
  4. ioBroker драйвера
  5. [solved]Pushover

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.5k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.0k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.6k

[solved]Pushover

Geplant Angeheftet Gesperrt Verschoben ioBroker драйвера
8 Beiträge 4 Kommentatoren 2.5k Aufrufe
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • aurodionovA Offline
    aurodionovA Offline
    aurodionov
    schrieb am zuletzt editiert von
    #1

    Словил проблему с отправкой сообщений с приоритетом 2, остальные отправляются исправно.

    ! host-SmartHome 2015-07-17 11:50:06 error instance system.adapter.pushover.0 terminated with code 6 (uncaught exception)
    ! Error: 2015-07-17 11:50:05 error at process._tickCallback (node.js:419:13)
    ! Error: 2015-07-17 11:50:05 error at _stream_readable.js:929:16
    ! Error: 2015-07-17 11:50:05 error at IncomingMessage.emit (events.js:117:20)
    ! Error: 2015-07-17 11:50:05 error at IncomingMessage. (/opt/iobroker/node_modules/iobroker.pushover/node_modules/pushover-notifications/lib/pushover.js:152:9)
    ! Error: 2015-07-17 11:50:05 error at Pushover.errors (/opt/iobroker/node_modules/iobroker.pushover/node_modules/pushover-notifications/lib/pushover.js:82:10)
    ! Error: 2015-07-17 11:50:05 error expire must be supplied with priority=2
    ! uncaught 2015-07-17 11:50:05 error exception: expire must be supplied with priority=2
    ! pushover-0 2015-07-17 11:50:04 info Send pushover notification: {"message":"test!","title":"SmartHome","sound":"pianobar","priority":2}

    Пишу с пульта….

    1 Antwort Letzte Antwort
    0
    • V Offline
      V Offline
      vtec
      schrieb am zuletzt editiert von
      #2

      Отправь на гитхаб в раздел issue. Так хоть ошибки будут в одном месте собираться будут. Если не умеем давайте учится. А то потом по всему форуму искать, да еще помнить.

      1 Antwort Letzte Antwort
      0
      • BluefoxB Offline
        BluefoxB Offline
        Bluefox
        schrieb am zuletzt editiert von
        #3

        error exception: expire must be supplied with priority=2

        https://pushover.net/api

        ! ` > Emergency Priority (2)

        Emergency-priority notifications are similar to high-priority notifications, but they are repeated until the notification is acknowledged by the user. These are designed for dispatching and on-call situations where it is critical that a notification be repeatedly shown to the user (or all users of the group that the message was sent to) until it is acknowledged. Applications sending emergency notifications are issued a receipt that can be used to get the status of a notification and find out whether it was acknowledged, or automatically receive a callback when the user has acknowledged the notification.

        To send an emergency-priority notification, the priority parameter must be set to 2 and the retry and expire parameters must be supplied.

        The retry parameter specifies how often (in seconds) the Pushover servers will send the same notification to the user. In a situation where your user might be in a noisy environment or sleeping, retrying the notification (with sound and vibration) will help get his or her attention. This parameter must have a value of at least 30 seconds between retries.

        The expire parameter specifies how many seconds your notification will continue to be retried for (every retry seconds). If the notification has not been acknowledged in expire seconds, it will be marked as expired and will stop being sent to the user. Note that the notification is still shown to the user after it is expired, but it will not prompt the user for acknowledgement. This parameter must have a maximum value of at most 86400 seconds (24 hours).

        For example, sending a retry parameter of 60 and an expire parameter of 3600 will cause your notification to be retried every 60 seconds for 1 hour.

        The optional callback parameter may be supplied with a publicly-accessible URL that our servers will send a request to when the user has acknowledged your notification.

        When your application sends an emergency-priority notification, our API will respond with a receipt value that can be used to get information about whether the notification has been acknowledged. See our receipts and callbacks section for more information. `

        То есть:

        {"message":"test!","title":"SmartHome","sound":"pianobar","priority":2,"expire":30, "retry": 15}

        1 Antwort Letzte Antwort
        0
        • aurodionovA Offline
          aurodionovA Offline
          aurodionov
          schrieb am zuletzt editiert von
          #4

          Bluefox, спасибо за пинок в нужном направлении. Заработало так:

          sendTo("pushover.0", {message:'test!',title:'SmartHome',sound:'pianobar',priority:2,retry:30,expire:30})

          Пишу с пульта….

          1 Antwort Letzte Antwort
          0
          • I Offline
            I Offline
            instalator
            schrieb am zuletzt editiert von
            #5

            Отвалился инет сегодня, pushover выдал такую ошибку в лог

            pushover-0	2015-11-18 19:27:10	error	Cannot send notification: {"code":"EAGAIN","errno":"EAGAIN","syscall":"getaddrinfo"}
            

            Высокий уровень Децибел вреден для здоровья!

            http://blog.instalator.ru/

            1 Antwort Letzte Antwort
            0
            • I Offline
              I Offline
              instalator
              schrieb am zuletzt editiert von
              #6

              появилась ошибка:

              ! pushover-0 2015-12-26 23:50:07 error Cannot send notification: {"code":"ENOTFOUND","errno":"ENOTFOUND","syscall":"getaddrinfo"}
              что означает я не понял, последующий сообщения приходят.

              Высокий уровень Децибел вреден для здоровья!

              http://blog.instalator.ru/

              1 Antwort Letzte Antwort
              0
              • aurodionovA Offline
                aurodionovA Offline
                aurodionov
                schrieb am zuletzt editiert von
                #7

                @instalator:

                появилась ошибка:

                ! pushover-0 2015-12-26 23:50:07 error Cannot send notification: {"code":"ENOTFOUND","errno":"ENOTFOUND","syscall":"getaddrinfo"}
                что означает я не понял, последующий сообщения приходят. `
                У меня пока работает, ошибок нет
                2858_12_iobroker.2018-11-23.log

                Пишу с пульта….

                1 Antwort Letzte Antwort
                0
                • V Offline
                  V Offline
                  vtec
                  schrieb am zuletzt editiert von
                  #8

                  @instalator:

                  появилась ошибка:

                  ! pushover-0 2015-12-26 23:50:07 error Cannot send notification: {"code":"ENOTFOUND","errno":"ENOTFOUND","syscall":"getaddrinfo"}
                  что означает я не понял, последующий сообщения приходят. `
                  Может интернет или ДНС отвалился, данное словосочетание getaddrinfo смущает.

                  1 Antwort Letzte Antwort
                  0
                  Antworten
                  • In einem neuen Thema antworten
                  Anmelden zum Antworten
                  • Älteste zuerst
                  • Neuste zuerst
                  • Meiste Stimmen


                  Support us

                  ioBroker
                  Community Adapters
                  Donate

                  758

                  Online

                  32.4k

                  Benutzer

                  81.4k

                  Themen

                  1.3m

                  Beiträge
                  Community
                  Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                  ioBroker Community 2014-2025
                  logo
                  • Anmelden

                  • Du hast noch kein Konto? Registrieren

                  • Anmelden oder registrieren, um zu suchen
                  • Erster Beitrag
                    Letzter Beitrag
                  0
                  • Home
                  • Aktuell
                  • Tags
                  • Ungelesen 0
                  • Kategorien
                  • Unreplied
                  • Beliebt
                  • GitHub
                  • Docu
                  • Hilfe