Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
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

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Controllers
  3. IOBroker
  4. Possible Bug with MySensors 2.0

Possible Bug with MySensors 2.0

Scheduled Pinned Locked Moved IOBroker
1 Posts 1 Posters 903 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • scribere8146S Offline
    scribere8146S Offline
    scribere8146
    wrote on last edited by
    #1

    Hi,

    could it be that there is a litte bug in the mysensors adapter for iobroker?
    The MYSensors API say that V_VAR1 .. V_VAR5 is possible for "any Device".
    But I can't use them with S_INFO.
    The MYSensors Controller can Handle this.
    So i edit the getmeta.js like this
    'S_INFO': {index: 36, role: 'info', vars: ['V_TEXT', 'V_VAR1', 'V_VAR2', 'V_VAR3', 'V_VAR4', 'V_VAR5']},

    With this modification, it works...

    Regards Thorsten

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    21

    Online

    11.7k

    Users

    11.2k

    Topics

    113.1k

    Posts


    Copyright 2025 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • MySensors
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular