@rob_in said in JS-MQTT DP eines Bildes (JFIF) in Datei schreiben (jpg):

For months I have been using a an MQTT topic change trigger to send an image (via Telegram) that was fetched via HTTP from http://frigate/api/myCam/latest.jpg?bbox=1 Works well, but...

I have just done a lot of work adding new cameras and configuration to Frigate and want to take advantage of it's MQTT image publishing. It seems silly to fetch something via HTTP when an image can be pushed via MQTT is all.

Surely there is an easy solution? So why can I not find it?

Having messed around with this a bit have discovered I was doing it correctly in the first place.

Turns out that images published through MQTT are not what I want anyhow so best ignored. Doh!

See: https://github.com/blakeblackshear/frigate/issues/6241

raintonr created this issue in blakeblackshear/frigate

closed Option to save/publish via MQTT snapshots of all identified targets even when event is in progress #6241

Hi all, has anyone managed to make this work?

For months I have been using a an MQTT topic change trigger to send an image (via Telegram) that was fetched via HTTP from http://frigate/api/myCam/latest.jpg?bbox=1 Works well, but...

I have just done a lot of work adding new cameras and configuration to Frigate and want to take advantage of it's MQTT image publishing. It seems silly to fetch something via HTTP when an image can be pushed via MQTT is all.

Surely there is an easy solution? So why can I not find it?

Adapter zum Empfangen von Ereignissen von Hikvision-Kameras über den Netzwerkmechanismus „Alarm Server“.

Benötigt keine Erkennung, da jede Kamera zum Senden von Ereignissen konfiguriert werden muss.

Fühlen Sie sich frei zu testen und geben Sie Feedback als Issues in Github. Funktioniert hier aber einwandfrei

English:

Adapter for receiving events from Hikvision cameras via 'Alarm Server' network mechanism.

Does not need discovery as each camera needs to be configured to send events.

Feel free to test and give any feedback as issues in Github. Working perfectly here though

@apollon77 Indeed, the chromecast issue is correct by this commit: https://github.com/ioBroker/ioBroker.js-controller/pull/1167/commits/8e43c640e5f6d06966becda582a7ffba6ed169bc

foxriver76 created this issue in ioBroker/ioBroker.js-controller

closed do not return an error if object does not exist on delForeignObject/d… #1167

Problem with chromecast adapter. Debug output:

2021-01-09 13:36:54.062  - error: chromecast.0 (32660) Not exists
  ioredis:redis write command[10.1.1.30:9000 (chromecast.0 (32660))]: 0 -> publish('messagebox.system.host.pg.mh,{"command":"addNotification","message":{"scope":"system","category":null,"message":"Not exists","instance":"chromecast.0"},"from":"system.adapter.chromecast.0","callback": ... <REDACTED full-length="351">') +12ms
2021-01-09 13:36:54.065  - error: chromecast.0 (32660) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-01-09 13:36:54.067  - error: chromecast.0 (32660) unhandled promise rejection: Not exists
2021-01-09 13:36:54.069  - error: chromecast.0 (32660) Error: Not exists
    at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2270:17)
    at Immediate.adapterObjects.getObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3010:38)
    at runCallback (timers.js:706:11)
    at tryOnImmediate (timers.js:676:5)
    at processImmediate (timers.js:658:5)
2021-01-09 13:36:54.070  - error: chromecast.0 (32660) Not exists
  ioredis:redis write command[10.1.1.30:9000 (chromecast.0 (32660))]: 0 -> publish('messagebox.system.host.pg.mh,{"command":"addNotification","message":{"scope":"system","category":null,"message":"Not exists","instance":"chromecast.0"},"from":"system.adapter.chromecast.0","callback": ... <REDACTED full-length="351">') +8ms
2021-01-09 13:36:54.073  - error: chromecast.0 (32660) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2021-01-09 13:36:54.075  - error: chromecast.0 (32660) unhandled promise rejection: Not exists
2021-01-09 13:36:54.077  - error: chromecast.0 (32660) Error: Not exists
    at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2270:17)
    at Immediate.adapterObjects.getObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3010:38)
    at runCallback (timers.js:706:11)
    at tryOnImmediate (timers.js:676:5)
    at processImmediate (timers.js:658:5)
2021-01-09 13:36:54.078  - error: chromecast.0 (32660) Not exists

Adapter für das Legrand Ecocompteur-Modul (auch bekannt als Legrand Measurement Concentrator EMDX³ 412000).

Dies ist ein Leistungsmessgerät mit eigener Weboberfläche. Der Adapter verwendet diese Weboberfläche durch:

• Abfrage nach sofortigen Leistungsmesswerten (Lesen einer JSON-Antwort).
• Abrufen der Indexseite des Geräts zum Lesen der TIC-Schnittstelle. TIC steht für Télé-Information Client, ein französisches Konstrukt. Dieser Wert wird in der Regel von einem an den Ecocompteur angeschlossenen Abrechnungszähler abgelesen.

Diese Objekte werden für jeden der 5 vom Ecocompteur gelesenen Schaltkreise plus Gesamtsumme erstellt:

• Momentane Leistung (in Watt).
• Gesamte kumulierte Energie, gemessen bei laufendem Adapter (in kWh).

Ein weiteres Objekt wird erstellt, um den TIC-Schnittstellenwert zu speichern.

English:

Adapter for the Legrand Ecocompteur module (aka. Legrand Measurement Concentrator EMDX³ 412000).

This is a power measurement device with it's own web interface. The adapter utilises that web interface by:

• Polling for instantaneous power readings (read in a JSON response).
• Polling the device's index page to read the TIC interface. TIC stands for Télé-Information Client which is a French construct. This value is generally read from a utility billing meter connected to the Ecocompteur.

These objects are created for each of the 5 circuits the Ecocompteur reads plus overall total:

• Instantaneous power (in Watts).
• Total cumulated energy measured while the adapter was running (in kWh).

A further object is created to store the TIC interface value.

Hi,

So I created an issue (feature request), forked the repo, fixed and created a push request on https://github.com/iobroker-community-adapters/ioBroker.sony-bravia

This was back in December. No-one has responded to either the issue or the push request in the original repo. What's the story here? Does no-body monitor these things?

How do I become a member of the Github iobroker-community-adapters group so can commit this change myself?

Cheers,

Robin