Gauge in Dashboard 2.0: great UI elements with neat features

Поделиться
HTML-код
  • Опубликовано: 19 дек 2024

Комментарии • 13

  • @paulgul1
    @paulgul1 10 месяцев назад

    Great video, thanks. I've started with dashboard 2 but finding it hard going at the moment. Appreciate these videos

  • @BGazzah
    @BGazzah 10 месяцев назад

    Great overview - guess I know what I will be doing at the W/E :)

  • @stoptheirlies
    @stoptheirlies 9 месяцев назад

    Thanks!

  • @edinetgrunhed6000
    @edinetgrunhed6000 8 месяцев назад

    thank you for very good explanation and example

  • @dzikiwiki2915
    @dzikiwiki2915 10 месяцев назад +1

    Thanks for your video. Do you know why I get a message (404: Not Found) when I press "Open Dashboard" in the dashboard 2.0 tab. The old version works properly and a window with indicators is displayed.

  • @stoptheirlies
    @stoptheirlies 9 месяцев назад

    Hi, thank you for the video's. I watched this one hoping you would talk about the input to the gauges, but unfortunately it was all about the gauge itself. I am new to this and I am finding it a nightmare to get information, I have a MQTT node connected to the broker and the topic is a tank sensor which sends temp, alarm, RSSI and depth in cm. I want the gauge to read the depth in cm, how do I separate this information from all the others, there is nothing in the MQTT or the Gauge nodes to select an Entity? Bob. UK

    • @csongorvarga
      @csongorvarga  9 месяцев назад +1

      These gauges expect a number in msg.payload. It depends how your sensor sends information. It it is a single topic, most probably the message contains an object with temp, alarm, rssi and depth as separate attributes of that object. You can direct that to a change node, where you configure to: Set msg.payload To msg.payload.depth. But as I said it depends on how the data in MQTT looks like.

    • @stoptheirlies
      @stoptheirlies 9 месяцев назад

      @@csongorvarga Hi, thank very much for replying. Yes the message is as you describe, under a heading of "Oil-SonicSmart" the message reads
      "678464281,"flags":128,"maybetemp":24,"temperature_C"8.333333."binding_countdown":0,"depth_cm":48,"protocol":"Watchman Sonic / Apolo Ultrasonic...." or at least that is all I can see of it as it runs off the window. Obviously I just need the depth part to go to the meter.
      I will try what you say and put a change node between the MQTT and the guage with the entry you suggest. Bob

    • @stoptheirlies
      @stoptheirlies 9 месяцев назад

      @@csongorvarga Hi, thank you very much for replying. you are correct about the format, the message is as follows I couldn't get it all as you cannot copy and paste in MQTT Explorer.
      Sonicsmart","id":678464281,"flags":128,"maybetemp":24,"temperature_C"8.333333."binding_countdown":0,"depth_cm":48,"protocol":"Watchman Sonic / Apolo Ultrasonic....
      I put what you said in a change node and got this "Cannot set property of non-object type: payload.depth" I have no idea what that means 🙂. Bob

    • @csongorvarga
      @csongorvarga  9 месяцев назад +1

      I don't know what is happening here. I can see your comment in the notifications, but when I want to reply to it, it does not appear. RUclips comments is useless. It also deletes anyting with link or code in it.

    • @csongorvarga
      @csongorvarga  9 месяцев назад +1

      Drop me a mail to csongor dot varga at gmail dot com