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. Feature Requests
  3. Generic text variable type

Generic text variable type

Scheduled Pinned Locked Moved Feature Requests
13 Posts 4 Posters 5.3k Views 3 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.
  • M medline2c

    Hello,
    I'm interesting about sending or receive text through a node for exemple to receive informations to write to a LCD or OLED screen... I've read about V_TEXT type but I don't found any example with text and LCD example or description, or idealy Build example... do you have ideas for How to do this ?
    Thanks
    (sorry, my engliish's very bad, I know... oups !)

    AWIA Offline
    AWIA Offline
    AWI
    Hero Member
    wrote on last edited by AWI
    #4

    @medline2c there are a few examples on the forum scrolling text

    1 Reply Last reply
    0
    • soifS soif

      V_TEXT already exists in version 2.0 : see in the code, or in Doxygen ! :-p

      But because of the NRF24L01 limitation, the maximum payload size is 25 bytes!.
      This means that V_TEXT messages would be limited to 25 characters, which could be too short in some case.

      Maybe Mysensors could split longer V_TEXT in multiple messages when sending, then recomposing it when receiving ie:

      "Here is a sentence longer than 25 characters that should be splitted."

      Could be encoded into messages like this :

      1;0;0;47;Here is a sentence lon;1;4
      1;0;0;47;ger than 25 characters;2;4
      1;0;0;47; that should be splitt;3;4
      1;0;0;47;ed.;4;4
      

      Then it would be automatically decoded at the arrival.

      This way V_TEXT message would be limited to 23*255 characters (more than enought), without writing complicated code from the controllers or in the sketch !

      AWIA Offline
      AWIA Offline
      AWI
      Hero Member
      wrote on last edited by AWI
      #5

      @soif this has been discussed when the V_TEXT was introduced.

      1 Reply Last reply
      0
      • soifS Offline
        soifS Offline
        soif
        Plugin Developer
        wrote on last edited by
        #6

        @AWI Thank you very much for poiting me to this interesting project.

        If it has been discussed, it has not been solved, wasn't it? I've read @John proposal, which sounds really similar to mine.

        Any progress or decision from the maintainers about this ?

        1 Reply Last reply
        0
        • hekH Offline
          hekH Offline
          hek
          Admin
          wrote on last edited by
          #7

          No, nothing has been done to the long-text thing.

          Long message (chunking) support should probably be implemented in a more general way (working for all V-types)

          1 Reply Last reply
          0
          • soifS soif

            V_TEXT already exists in version 2.0 : see in the code, or in Doxygen ! :-p

            But because of the NRF24L01 limitation, the maximum payload size is 25 bytes!.
            This means that V_TEXT messages would be limited to 25 characters, which could be too short in some case.

            Maybe Mysensors could split longer V_TEXT in multiple messages when sending, then recomposing it when receiving ie:

            "Here is a sentence longer than 25 characters that should be splitted."

            Could be encoded into messages like this :

            1;0;0;47;Here is a sentence lon;1;4
            1;0;0;47;ger than 25 characters;2;4
            1;0;0;47; that should be splitt;3;4
            1;0;0;47;ed.;4;4
            

            Then it would be automatically decoded at the arrival.

            This way V_TEXT message would be limited to 23*255 characters (more than enought), without writing complicated code from the controllers or in the sketch !

            M Offline
            M Offline
            medline2c
            wrote on last edited by
            #8

            @soif
            It's great but I'am not in Version 2.0 but in V 1.5 API... how to update to 2.0, I don't found the link to do this ... or I don't understand something ?... could you say me ?
            Christophe

            1 Reply Last reply
            0
            • M Offline
              M Offline
              medline2c
              wrote on last edited by
              #9

              An other question: I use Jeedom 2.0.1 ... do you know if Jeedom compatible with V_TEXT ?...

              1 Reply Last reply
              0
              • hekH Offline
                hekH Offline
                hek
                Admin
                wrote on last edited by
                #10

                2.0.0.beta can be found here:
                https://github.com/mysensors/Arduino/tree/development

                I don't know much about what Jeedom supports unfortunately.

                1 Reply Last reply
                0
                • M Offline
                  M Offline
                  medline2c
                  wrote on last edited by
                  #11

                  Jeedom support only 1.5 Stable branch ... Do you confirm me that it isn't compatible with V-Text usage ... ? ;-(

                  1 Reply Last reply
                  0
                  • hekH Offline
                    hekH Offline
                    hek
                    Admin
                    wrote on last edited by
                    #12

                    V_TEXT became available after 1.5. So it will probably not show up any devices for S_INFO/V_TEXT.

                    1 Reply Last reply
                    0
                    • M Offline
                      M Offline
                      medline2c
                      wrote on last edited by
                      #13

                      Thanks, I'll install a domoticz again to my NAS Synology... I don't have choice if I want to use V_TEXT... ;-)
                      So I don't know how to communique between Jeedom and Domoticz efficiantly, I'll search...
                      Great !...

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


                      17

                      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