Genmon MQTT to Home Assistant (Help)

[geoguy89]

Checklist

• I made sure that there are no existing issues or discussions - open issues,closed issues,open discussion, closed discussion - which may answer my question or that I could contribute my information to.
• I have read the Known Issues Wiki Page and my question / issue is not listed.
• I have provided the version of the software and the operating system in my post.
• If I have an issue with genmon not communicating with the controller, I have read and followed the serial troubleshooting guide.

Version

1.19.03

Have you submitted your log files from the About page? Note that outbound email must be working for logs to be submitted.

I have not submitted logs

What is/are your question(s)?

I'm very new to Genmon (Just got it setup this week) I've been reading on it for months now though.
Now that I'm hands on I'm trying to get MQTT working with Home Assistant. I have the communication part working I believe now but I can't seem to get sensors recognized.
I would like to get something like this in my home assistant from "drizzay" in the HA forums. They mentioned the need for a specific .yaml file which I found here

Sensors will not pull up from mqtt on their own but when I use the .yaml they do but they say they're "unavailable"

I was hoping someone may be able to point me in the right direction??

I appreciate any help/feedback anyone can give.

Thank you!!!

Additional information

No response

[jgyates]

This thread may be of some use.

#155

I personally do not use Home Assistant, but hopefully some of the other users who do can reply.

[geoguy89]

Thank you jgates!

[cbp0616]

Hey tswillette, did you get this working in HA? I've banged my head against the wall on this one. I have MQTT server running fine in HA, the MQTT service is correct on GenMon, and I can use MQTT explorer to see the posted discussions to my HA MQTT server.

This is where it breaks down for me. I just can't get any sensor information to show up in HA. I've tried using that same "Drizzay" YAML from the HA threads but it's been unsuccessful for me. I made sure to remove the root 199191 (or whatever it was) from my YAML as well.

Again, if you got this working, I'd love to know how you crafted the YAML.

[geoguy89]

I have!
The biggest thing I needed to understand was that certain items would not broadcast unless either the software (genmon) was just started or if they actually were running.

So like "Last outage, alarm, action, Exercise, RPM, Generator Output Voltage, etc" None of those are actively running so they can only be polled by HA when they are running/broadcasting. So my initial thought only seeing "Uptime, Utility Voltage, & Battery voltage running was that something had to be misconfigured but just restarting the genmon software fills in the blanks on some of the data rather than just seeing "unkown"

Now in Genmon MQTT make sure to leave the radio buttons off (numeric topics, json, remove spaces in topic path (unless you happened to put spaces in yours)

Below is my genmon configuration I ADDED to the bottom of my configuration.yaml file. I was having trouble referencing another yaml (or maybe it was just because of my misunderstanding at first) either way I didn't want to keep messing with it so I left it at the bottom of my configuration.yaml This was something that had to be rewritten in part. There were some pieces that were deprecated from my understanding so I just had chatgpt make it compatible with the new standard. There may be some parts that are still wrong but everything has been working fine for me for that last month.

https://pastebin.com/hykirAgz

Then the actually card configuration.
You obviously need to make sure to have all the referenced cards installed but here's my configuration

https://pastebin.com/PF1FDHkn

I'd be happy to find out if you figured it out from this!
Let me know if I can be of any more help.
Good luck!

[bon1wheel636]

I had to make a change removing mygen/ from the topic. Other than that thank you for sharing it supports my understanding and learning. I typically learn best by dissecting.

Thank you!

[cbp0616]

This is great and helping me dial it in. My biggest disconnect was why I wasn't seeing these messages published in the HA MQTT broker log. I just saw the initial "MQTT-USER" login. Also the MQTT integration didn't show any devices like it did with my Govee setup. Regardless, I went ahead and wrote in your YAML and noticed that I WAS GETTING SOME INFO! I had to revamp some of your cards, especially the hui-element since it was deprecated.

So I'm still getting unknowns on a lot of the data, I've restarted HA and genmon several times. I'm guessing its something to do with the Genmon MQTT settings. What is your blacklist filter like? Root topic is 'mygen' I'm guessing.

[jgyates]

Look at the setting "Flush Interval" on the Genmon MQTT add on. This value will set the time to send all of the data, even if it has not changed. If this value is zero then the add on will only send MQTT data when it starts (all of the data) and when it changes. The flush interval setting sets a timeout to resend the data even if has not changed. I set min to 1800 seconds (which is 30 minutes). This will make the add on send all of the data that has not changed every 30 minutes.

[cbp0616]

Thanks JG! I’ve removed everything in my black list filter as well as set the flush to 1800. I’ve managed to get everything except my battery and Genmon version populating

My HDR washed out my last photo so here it is now from mobile. Almost there!

[geoguy89]

Hey that's great news!!!! So happy you got that sorted! Glad to be of assistance.
Great info too JG, I didn't know that about the flush interval. I'll definitely be looking into updating that.

[thomasshawn]

mind posting your final files? you did a lot of trial and error. might save someone else the same headache.
thanks

[geoguy89]

mind posting your final files? you did a lot of trial and error. might save someone else the same headache. thanks

If you read through this thread you'll see MY final stuff...I haven't changed anything. This isn't a plug and play solution you have to do a little investigation on your own, as your setup is not going to be identical to anyone elses. Check out mqtt explorer make sure your connections are correct. Make sure you've downloaded the correct cards. If you get an error initially, check what the error is...is a card missing? Get yourself to a point where you're ready to troubleshoot if you're running into problems then we'll see what we can do to help. Read through the thread. Copy the yaml for the generator...you can make a new yaml file for it and reference it in your configuration YAML, if you know how to do that ..I personally was having trouble so I just added it to my configuration.yaml file

My YAML for the cards is there too...I haven't changed anything since I've posted it and it's all been working great.

Do what you can then ask for help if you need it please.

[thomasshawn]

Thanks. I understand it's not a plug N play scenario but serval people get stuck for different reasons. They dissappear for a while and come back with "got it working" and no follow up so was just asking for someone to close the loop for the next guy. Maybe not even me. I've had genmon running for ~2yrs. Toyed with adding it to HA but I get what I need with other methods and I like the built in genmon UI but, maybe if I get bored I'll add it for completeness.

[geoguy89]

Thanks. I understand it's not a plug N play scenario but serval people get stuck for different reasons. They dissappear for a while and come back with "got it working" and no follow up so was just asking for someone to close the loop for the next guy. Maybe not even me. I've had genmon running for ~2yrs. Toyed with adding it to HA but I get what I need with other methods and I like the built in genmon UI but, maybe if I get bored I'll add it for completeness.

Fair enough.
I just wanted it within my HA environment.
Everything I've personally done is within the YAML, I've not altered it since adding it to my configuration.yaml.
I've made sure I had the correct cards installed.
If you decide to try it, I'll help the best I can but I don't have the time to go back and write a step-by step guide.
Feel free to reach out if you decide to take it on and we can troubleshoot if you get stuck.

Thanks

[jcleek]

Late to the party but hope someone can help. I am trying to get this working and have figured out that apparently none of the genmon info is actually being passed. I get generator info but genmon version, Pi temp, CPU, network info, etc are reported. Any idea why?

[jgyates]

I am confused as to what is working and what is not working. you mentioned that none of the genmon info is passed but also say that you get generator info. Can you give more specific detail?

The file /var/log/genmqtt.log would have any specific errors related to the MQTT add on. Also, on the MQTT add on settings, check the "Blacklist Filter" settings. If a keyword in the blacklist are contained in an MQTT topic it will not be sent to the MQTT broker.

[jcleek]

@jgyates it was definitely the blackllist filter. Now to figure out what I can turn back on!

[jgyates]

Great, I am glad it is working for you

[jcleek]

Still working on fine tuning the layout but this is what is working for me today. https://pastebin.com/g4bqmfvA

My Pi is on eth0. Any thoughts on what to put in place of the WiFi?

[jgyates]

That looks great.

You could use "Monitor Health" on the Monitor page. This is "OK" if everything is working as expected or a text value stating any issues genmon may be having. The error that is more likely is "Not receiving data". It can be a combination if any of the errors if multiple occur.

genmon/genmon.py

Line 1234 in 73a8f8e

def GetSystemHealth(self):

[jcleek]

Got it. Had to add a sensor so the configuration yaml info changed as well. Changed the formatting a little so it fits nicely in 2 columns on a bigger screen. Still not sure to do about WiFi since I don't use it.

Configuration of sensors for configuration.yaml: https://pastebin.com/Th6tpyuT
Dashboard YAML: https://pastebin.com/jdnvwQzr

[jterrace]

For any future readers, I have put together some instructions for pulling in genmon's mqtt feed into home assistant as well as an updated yaml file defining the entities here: https://github.com/jterrace/genmon-ha-yaml

[thomasshawn]

ThanK you very much. That's awesome

[jgyates]

That is great. I added a link to this at the bottom of the genmqtt wiki entry: https://github.com/jgyates/genmon/wiki/1----Software-Overview#genmqttpy-optional

[inventor7777]

For anyone else looking for Home Assistant MQTT configs, please consider also having a look at mine.

I've looked at and tried all of the existing popular configs and none of them worked well for me, so I took the best parts of each and made my own, with extra sensors and even better icons :D

https://github.com/inventor7777/Other-Configs

[inventor7777]

Ah cool, I did not realize that MQTT had that functionality.
As for built in discovery prefix - that would be phenomenal! As long as it supports the correct icons and stuff to look nice.

[jterrace]

@inventor7777 could definitely use a tester once I get it implemented if you are willing, shoot me an email jterrace@gmail.com

[inventor7777]

Totally willing to test but I'd prefer to stay on GitHub if you don't mind

[jterrace]

ack, will ping you here when a branch is ready for testing

[inventor7777]

thank you, sounds good

[jterrace]

Home Assistant Discovery implementation is ready for testing. To switch your genmon installation to try it, enter the root directory of genmon and run:

git remote add jterrace https://github.com/jterrace/genmon.git
git fetch jterrace
git switch -c mqtt-ha-discovery jterrace/mqtt-ha-discovery

then restart genmon with:

sudo ./startgenmon.sh restart

To revert:

git checkout master

(then restart)

Then in the mqtt addon settings, enable "Home Assistant Discovery". You also must enable "JSON for Numerics" and disable "Numeric Topics". I also recommend enabling "Retain Data".

The device will show automatically in home assistant with "Genmon {SiteName}" where "{SiteName}" is pulled from your site name configuration in genmon. All entities being published are automatically added into the device, and the "availability" works correctly. I tested it: if genmon is offline, all entities become "unavailable".

@inventor7777 please have a try when you have a chance - I also integrated your icons from your repo. If I can get at least one other person to test it, I'll send out a pull request to integrate into genmon.

[inventor7777]

@jterrace alright...I'm going to write as I test. Great job btw

---

So I noticed immediately that I needed to change the decimals in the Battery Voltage sensor in order to get 13.8 rather than 14. Incredibly minor but it would have been nice to have it default to having a decimal.

---

Next - units. On sensors like Nominal Line Voltage, Rated Max Power, Nominal Frequency, they are presented as text sensors. This is probably better for monitoring changes, (but why would this change anyway?). So I'm not sure whether this should be standardized with the correct units, or left. And the Nominal RPM doesn't even have a unit, which does not match the RPM sensor. That should probably get a unit added.

---

Next thing I notice is that it's hard to read through.

On my own MQTT config, I split Genmon and the Generator into different devices, which works great for me. That, however, is subjective - most integrations do not natively do that. Now, another thing I did thatI definitely think this should implement as well is the different entity categories.

On my Generator device setup, I placed Activation Time, Battery Check Due, Exercise. the text logs (Alarm/Action/Service A/B/Last Service, and for Genmon, I put errors (CRC/Modbus/Sync/Timeout/Invalid Data/Validation/Health) and Version/Undervoltage under Diagnostic. I did that change on a whim, which means further thought is likely required before implementation. I never even added sensors like serial number and the calibrate sensors, but those would be a good candidate for Diagnostic.

---

Next, I do not see any Genmon computer stats (CRC errors, WiFi, etc). On my manual config I actually split these into another device to make entity IDs easier and just be overall more organized.

Side note: I've just updated my repo with the latest updates :)

---

Lastly, some things don't have icons.

Phase - should probably use mdi:sine-wave or mdi:cosine-wave
Engine displacement - probably mdi:engine
Fuel Type - mdi:fuel
I think for model, capacity, nominal frequency and nominal rpm it should likely use mdi:generator-stationary
For Switch State, maybe mdi:switch

Personally, I think the Controller entities should be mdi:alarm-panel because it looks kinda similar, but I'm not sure.

---

One thing I feel could also be good is having the controller model in place of the Genmon devices name, so it would look like
Evolution 2.0, Air Cooled
by Genmon

Not sure how feasible it is but maybe a future polish to make it even more like a native integration.

---

As for the Genmon UI itself...I think it should automatically switch on JSON for Numerics when you enable HA Discovery. Not sure if that is easily possible but would be good QoL

---

TL;DR – Initial Feedback Highlights

• Improve precision on battery voltage sensor
• Standardize units across sensors
• Consider splitting Genmon & Generator as devices (subjective)
• Add missing entities (Activation Time, computer stats)
• minor QoL to Genmon UI

[inventor7777]

Another thing - I do not see the Activation Time sensor, which in my config usually says something like 3 years, 279 days, 9 hours

[jterrace]

Thanks, @inventor7777 ! Just wanted to let you know I'm working through your excellent feedback. One thing I didn't realize is I was missing a bunch of entities because I had the default blacklist turned on, which filters out quite a bit by default:

genmon/conf/genmqtt.conf

Line 60 in 3d39aeb

blacklist = Monitor,Run Time,Monitor Time,Generator Time,External Data

Unfortunately, a bunch of the entities are text based, so I'll either have to leave it as text or add a bunch of string parsing.

I do agree with you that a bunch of the entities should be moved to diagnostics. From what I can gather, there isn't a clear cut rule for what should be a diagnostic, but it seems like sort of metadata about the device rather than the core data. I also agree that now that I can see all these entities about genmon (vs. about the generator), it would make sense to split into two devices. Something like "Genmon Sitename" and "Generator Sitename" makes sense to me, WDYT?

Another annoyance with mqtt discovery is some updates don't seem to take effect unless I delete the discovery topic (which deletes all the entities) and then add it back. For example, switching the entity type to diagnostic doesn't have any effect unless I recreate them. Even adding the suggested_display_precision attribute (which fixes your complaint about battery voltage precision) requires recreation. Some other things, like the icon, does take effect on updates. I'm not sure if that's a bug or by design with MQTT discovery, but I may file a separate issue with home assistant mqtt component to ask about it at least. It seems like some of these things should apply with updates.

I'll let you know when it's all ready to test test. Thanks again for all your feedback!

[inventor7777]

Yeah, I definitely agree that there should be two devices but with unified Genmon/Generator names (for easy entity ID based programming). And that's actually the scheme I'm using for my manual entities, just minus the sitename :)

That's interesting that MQTT discovery doesn't update immediately. I'd have expected it to behave just like manual sensors...but that's what's nice about OSS...people can fix that!

As for the text based sensors...that sounds like an issue with Genmon to me - I'd have expected those to be JSON as well (it should just a number and unit...🤷‍♂️) so maybe something to be fixed later

And you're welcome for the feedback - I wouldn't mind using this over manual sensors and so I want to help get it right the first time 👍

[inventor7777]

Also the blacklist has "External Data"? What even is that? I don't recall seeing an "External Data" topic tree but maybe I wasn't paying attention.

I removed the blacklist immediately when I set my Genmon up lol so I legit don't know

[jgyates]

Hi @inventor7777

The external data functionality is described here.

Let me know if you have any questions.

[inventor7777]

Ah, thank you. That answers that!

[jtubb]

I should have checked here first to make sure I wasn't duplicating efforts. However hopefully you enjoy the fruit of my labor. #1360

[jtubb]

If your MQTT server is set to retain messages then you will need to manually delete the autodiscovery topic. I'm traveling so I can't pull up exactly where this will be but I would expect "/{ha_base_topic}/sensors/1 Date" where the default ha_base_topic is "homeassistant".

[jterrace]

It's not MQTT that's set up to retain - it's the code that sets retain=True (which I think is correct, since you have proper availability topic set up).

But it doesn't look like it's stale - I still see these three sensors being updated:

• homeassistant/sensor/generator/outage_outage_log_1_date/config
• homeassistant/sensor/generator/outage_outage_log_1_duration/config
• homeassistant/sensor/generator/outage_outage_log_1_estimated_fuel/config

from:

• genmon/sensor/outage_outage_log_1_date/state
• genmon/sensor/outage_outage_log_1_duration/state
• genmon/sensor/outage_outage_log_1_estimated_fuel/state

When I look in MQTT explorer, it says last updated timestamp for all three are 01/23/2026 8:36:33 AM (which is 10 minutes ago).

Looking in /cmd/outage_num_json, I do see this in there:

{
      "Outage Log": [
        {
          "0": [
            {
              "Date": "12-30-2025 10:40:20"
            },
            {
              "Duration": "0:00:26"
            },
            {
              "Estimated Fuel": "0.00 gal"
            }
          ]
        },
        {
          "1": [
            {
              "Date": "12-30-2025 09:02:41"
            },
            {
              "Duration": "0:00:22"
            },
            {
              "Estimated Fuel": "0.00 gal"
            }
          ]
        },
        {
          "2": [
            {
              "Date": "12-19-2025 17:31:36"
            },
            {
              "Duration": "0:00:22"
            },
            {
              "Estimated Fuel": "0.00 gal"
            }
          ]
        },
        {
          "3": [
            {
              "Date": "12-19-2025 16:14:44"
            },
            {
              "Duration": "0:00:22"
            },
            {
              "Estimated Fuel": "0.00 gal"
            }
          ]
        },
        {
          "4": [
            {
              "Date": "11-23-2025 00:53:01"
            },
            {
              "Duration": "0:00:11"
            },
            {
              "Estimated Fuel": "0.00 gal"
            }
          ]
        }
      ]
    }

So maybe they're correct? I also see the "0" version of these at e.g. homeassistant/sensor/generator/outage_outage_log_0_date/config but they have "name": "Last Outage Date", vs. the "1" have e.g. "name": "1 Date",. Any idea what's going on?

[jtubb]

I think this is a parsing issue, I just pushed a PR that should clear these things out and/or fix log formatting. It has already been accepted so just pull the latest genmon version down and restart it. #1365

Let me know what the results of that are. Thanks for the troubleshooting help!

[jterrace]

@jtubb thanks! I updated and everything looks good except I still see those "1" prefixed entities and they're still being updated:

[jtubb]

Hmmm, let me dig into the docs some, clearly there are differences in the outage logs depending on the generator model. I'll loop back here when I think I have a fix.

[jtubb]

In case anyone is interested I also built this lovelace card for HomeAssistant that will automatically pickup your the generator info that this GenMon addon provides.

https://github.com/jtubb/generator-hmi-card

[jtubb]

@jterrace @inventor7777 I also updated this card to work with the corrected entity ID's from the fixes in PR 1364. If you are using it please update and let me know if you have any issues.

[jterrace]

I haven't been using the card, but here's my dashboard:

[jtubb]

Very nice!

[tcflint]

Did you share yaml for this?

[nigelellis]

@tcflint -- I found it a while back and built a similar version.

views:
  - title: Generator
    path: generator
    icon: mdi:power-generator
    cards:
      - square: false
        type: grid
        cards:
          - type: entity
            entity: sensor.generator_engine_generator_state
            name: Current Status
            state_color: true
          - type: custom:mushroom-template-card
            primary: 'Generator: {{ states(''sensor.generator_outage_status'') }}'
            secondary: 'Switch: {{ states(''sensor.generator_switch_state'') }}'
            icon: mdi:power-generator
            entity: sensor.generator_outage_status
            tap_action:
              action: more-info
            color: |
              {% if is_state('sensor.generator_status', 'Running') %}
                green
              {% elif is_state('sensor.generator_status', 'Standby') %}
                blue
              {% else %}
                red
              {% endif %}
            features_position: bottom
        columns: 1
      - square: false
        type: grid
        columns: 2
        cards:
          - type: entity
            entity: sensor.generator_battery_voltage
            name: Battery
            icon: mdi:battery-charging
          - type: entity
            entity: sensor.generator_rpm
            name: Engine RPM
          - type: entity
            entity: sensor.generator_output_voltage
            name: Gen Voltage
          - type: entity
            entity: sensor.generator_output_frequency
            name: Gen Frequency
          - type: entity
            entity: sensor.generator_utility_voltage
            name: Utility Voltage
            icon: mdi:transmission-tower
          - type: entity
            entity: sensor.generator_total_run_hours
            name: Total Runtime
      - square: false
        type: grid
        cards:
          - type: custom:canvas-gauge-card
            card_height: 150
            entity: sensor.generator_utility_voltage
            name: ''
            gauge:
              type: radial-gauge
              title: Utility
              width: 150
              height: 150
              minValue: 0
              maxValue: 280
              startAngle: 40
              ticksAngle: 280
              valueBox: true
              units: Vac
              majorTicks:
                - 0
                - 28
                - 56
                - 84
                - 112
                - 140
                - 168
                - 196
                - 224
                - 252
                - 280
              minorTicks: 10
              strokeTicks: true
              highlights:
                - from: 0
                  to: 218
                  color: rgba(234, 51, 36, .75)
                - from: 218
                  to: 228
                  color: rgba(255, 255, 85, .75)
                - from: 228
                  to: 252
                  color: rgba(104, 225, 67, .75)
                - from: 252
                  to: 262
                  color: rgba(255, 255, 85, .75)
                - from: 262
                  to: 280
                  color: rgba(234, 51, 36, .75)
              borders: 'no'
              needleType: arrow
              needleWidth: 4
              needleCircleSize: 7
              needleCircleOuter: true
              needleCircleInner: false
              animationDuration: 1500
              animationRule: linear
              valueBoxBorderRadius: 10
              colorValueBoxRect: '#222'
              colorValueBoxRectEnd: '#333'
              valueDec: 0
              valueInt: 0
          - type: custom:canvas-gauge-card
            card_height: 150
            entity: sensor.generator_output_voltage
            name: ''
            gauge:
              type: radial-gauge
              title: Generator
              width: 150
              height: 150
              minValue: 0
              maxValue: 280
              startAngle: 40
              ticksAngle: 280
              valueBox: true
              units: Vac
              majorTicks:
                - 0
                - 28
                - 56
                - 84
                - 112
                - 140
                - 168
                - 196
                - 224
                - 252
                - 280
              minorTicks: 10
              strokeTicks: true
              highlights:
                - from: 0
                  to: 218
                  color: rgba(234, 51, 36, .75)
                - from: 218
                  to: 228
                  color: rgba(255, 255, 85, .75)
                - from: 228
                  to: 252
                  color: rgba(104, 225, 67, .75)
                - from: 252
                  to: 262
                  color: rgba(255, 255, 85, .75)
                - from: 262
                  to: 280
                  color: rgba(234, 51, 36, .75)
              borders: 'no'
              needleType: arrow
              needleWidth: 4
              needleCircleSize: 7
              needleCircleOuter: true
              needleCircleInner: false
              animationDuration: 1500
              animationRule: linear
              valueBoxBorderRadius: 10
              colorValueBoxRect: '#222'
              colorValueBoxRectEnd: '#333'
              valueDec: 0
              valueInt: 0
          - type: custom:canvas-gauge-card
            card_height: 150
            entity: sensor.generator_output_power
            name: ''
            gauge:
              type: radial-gauge
              title: Gen Load
              width: 150
              height: 150
              minValue: 0
              maxValue: 22
              startAngle: 40
              ticksAngle: 280
              valueBox: true
              units: kW
              majorTicks:
                - 0
                - 4
                - 8
                - 12
                - 16
                - 18
                - 22
              minorTicks: 4
              strokeTicks: true
              highlights:
                - from: 0
                  to: 16
                  color: rgba(104, 225, 67, .75)
                - from: 16
                  to: 20
                  color: rgba(255, 255, 85, .75)
                - from: 20
                  to: 22
                  color: rgba(234, 51, 36, .75)
              borders: 'no'
              needleType: arrow
              needleWidth: 4
              needleCircleSize: 7
              needleCircleOuter: true
              needleCircleInner: false
              animationDuration: 1500
              animationRule: linear
              valueBoxBorderRadius: 10
              colorValueBoxRect: '#222'
              colorValueBoxRectEnd: '#333'
              valueDec: 0
              valueInt: 0
          - type: custom:canvas-gauge-card
            card_height: 150
            entity: sensor.generator_output_frequency
            name: ''
            gauge:
              type: radial-gauge
              title: Gen Freq
              width: 150
              height: 150
              minValue: 0
              maxValue: 70
              startAngle: 40
              ticksAngle: 280
              valueBox: true
              units: Hz
              majorTicks:
                - 0
                - 10
                - 20
                - 30
                - 40
                - 50
                - 60
                - 70
              minorTicks: 10
              strokeTicks: true
              highlights:
                - from: 0
                  to: 57
                  color: rgba(234, 51, 36, .75)
                - from: 57
                  to: 58.5
                  color: rgba(255, 255, 85, .75)
                - from: 58.5
                  to: 61.5
                  color: rgba(104, 225, 67, .75)
                - from: 61.5
                  to: 63
                  color: rgba(255, 255, 85, .75)
                - from: 63
                  to: 70
                  color: rgba(234, 51, 36, .75)
              borders: 'no'
              needleType: arrow
              needleWidth: 4
              needleCircleSize: 7
              needleCircleOuter: true
              needleCircleInner: false
              animationDuration: 1500
              animationRule: linear
              valueBoxBorderRadius: 10
              colorValueBoxRect: '#222'
              colorValueBoxRectEnd: '#333'
              valueDec: 0
              valueInt: 0
        columns: 2
    type: masonry
    theme: Mushroom