Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. English
    3. Visualization
    4. getting started with visualisations

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    getting started with visualisations

    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Taragorm last edited by

      It's showing in the toolbox now - many thanks!

      1 Reply Last reply Reply Quote 0
      • T
        Taragorm last edited by

        Much progress, but another small issue.

        My visualisation shows values ok in the edit dialog.

        In the normal view, it shows the "undefined" value... unless the value is used by a different widget.

        This suggests I've done something wrong in binding, but as far as I can see, I've done pretty much what the template does.

        Have I missed something out? It feels like whatever code that populates vis.states[] hasn't been invoked correctly. (i.e. the view seems to be unaware of the points I'm asking for).

        1 Reply Last reply Reply Quote 0
        • T
          Taragorm last edited by

          ps: Changed the repo to: https://github.com/Taragorm/ioBroker.vistaragorm

          Bluefox 1 Reply Last reply Reply Quote 0
          • Bluefox
            Bluefox @Taragorm last edited by Bluefox

            @Taragorm It can be, that I forgot to describe, that all ObjectID Variables Names must start with "oid..." or end with "...oid" or "...oidN" (N is any number from 0 to 99)

            Please use following files, that work:
            vistaragorm.js
            vistaragorm.html

            1 Reply Last reply Reply Quote 0
            • T
              Taragorm last edited by

              Ah, that would be it then - I may have missed it.

              I assumed that the /id type in the attr declaration was what did it.

              1 Reply Last reply Reply Quote 0
              • T
                Taragorm last edited by

                That works nicely, thanks.

                Out of curiosity, is there any way to force subscription?

                I have a case where I have mutiple values on a sensor, and I'd like to be able to just specify the sensor oid for the widget, and have the implementation figure out the values.

                e.g. I have
                foo.bah.x
                foo.bah.y
                foo.bah.z

                .. I'd like to only have to supply an oid of foo.bah - the widget can add .x, .y etc as those are fixed.

                or does supplying an oid = "foo.bah" create a subscription for changes of all children too?

                Bluefox 1 Reply Last reply Reply Quote 0
                • T
                  Taragorm last edited by

                  In case it's not obvious, I'd like a widget to be able to generate oids based on, or relative to, an oid in an attribute, and have the object correctly added to the widget/view so I can get data from it.

                  Surely there must be a way to do this?

                  Bluefox 1 Reply Last reply Reply Quote 0
                  • Bluefox
                    Bluefox @Taragorm last edited by

                    @Taragorm I must check it

                    1 Reply Last reply Reply Quote 0
                    • T
                      Taragorm last edited by

                      Appreciated

                      1 Reply Last reply Reply Quote 0
                      • Bluefox
                        Bluefox @Taragorm last edited by

                        @Taragorm Now I understand, what you want.
                        The solution is to provide all OIDs during configuration. You can see the example:

                        • https://github.com/ioBroker/ioBroker.vis-hqwidgets/blob/master/widgets/hqwidgets.html#L61
                        • https://github.com/ioBroker/ioBroker.vis-hqwidgets/blob/master/widgets/hqwidgets/js/hqwidgets.js#L3069

                        If your first OID is changed, the defined function (in example vis.binds.hqwidgets.changedButtonId) will be called and you can define other fields there with desired OIDs.

                        1 Reply Last reply Reply Quote 0
                        • T
                          Taragorm last edited by

                          Thanks- that solves the problem!

                          1 Reply Last reply Reply Quote 1
                          • G
                            goodDay14 last edited by goodDay14

                            That works nicely, thanks.
                            Out of curiosity, is there any way to force subscription?
                            I have a case where I have mutiple values on a sensor, and I'd like to be able to just specify auto clicker wordunscrambler jumblesolver

                            the sensor oid for the widget, and have the implementation figure out the values.

                            1 Reply Last reply Reply Quote 0
                            • S
                              sonusfaber @Bluefox last edited by

                              @Bluefox I do struggle with the following instruction:
                              "replace index.html and edit.html replace files in /opt/iobroker/iobroker-data/files/vis/index.html and edit.html with files from /opt/iobroker/node_modules/iobroker.vis/www/index.html.original and edit.html.original. Change the file /opt/iobroker/iobroker-data/files/vis/cache.manifest. No matter what, just one symbol to trigger the browser to load files anew. The files must be smaller than 200k. If you have got wrong files, so they are definitly largen than 400k."

                              I understood ..
                              Replace the following two files /opt/iobroker/iobroker-data/files/vis/index.html & /opt/iobroker/iobroker-data/files/vis/edit.html with
                              /opt/iobroker/node_modules/iobroker.vis/www/index.html.original and /opt/iobroker/node_modules/iobroker.vis/www/edit.html.original.

                              in other words..
                              cp /opt/iobroker/node_modules/iobroker.vis/www/index.html.original /opt/iobroker/iobroker-data/files/vis/index.html
                              cp /opt/iobroker/node_modules/iobroker.vis/www/edit.html.original /opt/iobroker/iobroker-data/files/vis/edit.html

                              Is this correct ?

                              If yes, in my installation
                              /opt/iobroker/node_modules/iobroker.vis/www/index.html.original and /opt/iobroker/node_modules/iobroker.vis/www/edit.html.original do not exist!

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post

                              Support us

                              ioBroker
                              Community Adapters
                              Donate

                              810
                              Online

                              31.8k
                              Users

                              80.0k
                              Topics

                              1.3m
                              Posts

                              vis
                              4
                              43
                              4866
                              Loading More Posts
                              • Oldest to Newest
                              • Newest to Oldest
                              • Most Votes
                              Reply
                              • Reply as topic
                              Log in to reply
                              Community
                              Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                              The ioBroker Community 2014-2023
                              logo