Ankündigung

Einklappen
Keine Ankündigung bisher.

Text Input to Miniserver

Einklappen
X
 
  • Filter
  • Zeit
  • Anzeigen
Alles löschen
neue Beiträge

  • Text Input to Miniserver

    I've created a wiki HowTo at the following link - https://www.loxwiki.eu/display/LOXEN...+to+Miniserver

    Please feel free to discuss in this thread.
    Ich spreche kein Deutsch. Gib Google Translate die Schuld, wenn ich unverständlich bin.

  • #2
    Oh, whow!
    This looks like quite some work from your side.
    Thank you for your effort, even if I have currently no direct use case for this.
    Loxone-Installation mit mehreren Extensions, Dimmer-Extension, DMX, 1-Wire (alles aktuell noch im Auslieferungszustand);
    FritzBox, Netgear Plus Switch mit mehreren VLANs, Intel NUC mit VMWare ESXi 6.5 (pfSense, Loxberry, Kleinkram)

    Kommentar


    • Tico
      Tico kommentierte
      Kommentar bearbeiten
      You're welcome.

  • #3
    Wow, that looks like a LOT of work!
    Will give it a try to get Title informations from iTunes into Loxone!

    Thank you for sharing this!

    Kind regards,

    Martin

    Kommentar


    • #4
      Impressive. But I wonder, does it not put excessive load on the miniserver? Meaning how big is increase of Miniserver load percentages?

      Kommentar


      • #5
        The extra CPU load is not noticeable. This will depend though on the polling interval for the Virtual Inputs. For my use case, polling every 5 minutes has no problems.

        I recently deleted an A3 page of 53 Status Blocks with associated Virtual Inputs. The Miniserver dropped by about 2% Memory Requirement.
        Ich spreche kein Deutsch. Gib Google Translate die Schuld, wenn ich unverständlich bin.

        Kommentar


        • #6
          Wow - that is a huge workaround - thanks!
          Unfortunately I would need this at several places, so the huge number of blocks would make my (already complicated) config a lot of more complicated.

          When digging into a similar problem (parsing weather data), I found some suggestions to implement this using Pico-C - see https://groups.google.com/forum/#!to...sh/KZNGlIQz4qU, https://github.com/netdata-be/loxone...wunderground.c, https://www.loxforum.com/forum/faqs-...stein-abfragen. Wouldn't this be a more elegant solution?

          Kommentar


          • #7
            Yes...it wouldn't be very hard to find a more elegant solution! It's really there to satisfy the need to ingest text when there's no other way.

            Of those solutions you posted - The Wunderground PicoC script never really worked. It has a memory leak and the Miniserver will ultimately crash or reboot continuously.

            Remember you can also delete as many Status Blocks as required to suit your needs. You can also adapt the single tab of Status Blocks for multiple uses without duplicating the blocks. So your 'several places' re-uses the single page of blocks.



            Ich spreche kein Deutsch. Gib Google Translate die Schuld, wenn ich unverständlich bin.

            Kommentar


            • #8
              Zitat von Tico Beitrag anzeigen
              You can also adapt the single tab of Status Blocks for multiple uses without duplicating the blocks. So your 'several places' re-uses the single page of blocks.
              How could that work? If I have e.g. 2 times 20 letters to parse - so 40 inputs, how could I attach them to 20 status blocks?

              Kommentar


              • #9
                I should qualify that. Re-use of the blocks is limited to when you can adapt the command recognition to suit both data sources. In your case, what is the command recognition you are using for the first 20 letters? And the command recognition being used for the second 20 letters? (ie. Just the first letter for each case).
                Zuletzt geändert von Tico; vor einer Woche.
                Ich spreche kein Deutsch. Gib Google Translate die Schuld, wenn ich unverständlich bin.

                Kommentar


                • #10
                  It is more easy to fetch the data from a Raspberry/LoxBerry and send the text to a VTI. That’s only some lines of code.
                  LoxBerry/Plugin Support: Wenn du einen Begriff in meiner Antwort nicht auf Anhieb verstehst, bitte nicht gleich rückfragen, sondern erst die Suche im LoxWiki und bei Google bemühen.
                  PN/PM: Ich bevorzuge die Beantwortung von Fragen in öffentlichen Threads, wo andere mithelfen und mitprofitieren können. Herzlichen Dank!

                  Kommentar


                  • Eusebius
                    Eusebius kommentierte
                    Kommentar bearbeiten
                    VTI = Virtual Text Input
                    Zuletzt geändert von Eusebius; vor einer Woche.
                Lädt...
                X