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. English
  3. Scripting / Logic
  4. JavaScript
  5. PoC: JSON State Mapper for the ioBroker Javascript Engine

NEWS

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    22
    1
    992

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

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    14
    1
    2.4k

PoC: JSON State Mapper for the ioBroker Javascript Engine

Geplant Angeheftet Gesperrt Verschoben JavaScript
javascript
1 Beiträge 1 Kommentatoren 419 Aufrufe 1 Watching
  • Ä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.
  • S Offline
    S Offline
    stev-io
    schrieb am zuletzt editiert von
    #1

    Hi all!

    I am ioBroker newbie, working a lot with devices that publish JSON documents. So I was looking for ways to automatically persist values from the JSON document as separate data points. The whole thing as configurable as possible (and in some way scalable, meaning only once per same device type and not for each device individually). Effectively without the need to customize scripts. Since with moderate research I couldn't find a solution that best served my preferences and working methods, and I parallely wanted to delve into the depths and shallows of ioBroker anyway, I designed my own software component (a TypeScript module). In the spirit of a proof of concept so that I can see if my wish could be realized. Likely, there are better solutions out there, too, or my flow is not that of the general public, which is why my solution may not be a good fit for others. But: Since on my way to a working solution I got lost in details, the component has therefore already gained some size, I thought I could share the current state of work. It can be found here:

    https://github.com/stevenengland/iobJs-JsonStateMapper

    Roughly speaking, one configures which data points containing JSON documents (source data points) one wants to subscribe to and where (target data points) which values from the source should be written to:

    Here's an example image of a Tasmota socket from which I want to transfer the consumed power from SENSOR (natively from TASMOTA) to CURRENT_POWER (specially created data point).
    622c7bed-bc13-4892-97ec-b009f222e217-grafik.png

    How exactly it works and what is needed is documented in the README in the repo.

    Cheers

    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

    761

    Online

    32.5k

    Benutzer

    81.6k

    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