Repository navigation
Great start - next up: stats sensors in Home Assistant. #1
Description
Activity
- changed the title
[-]Great start - next up sensors in Home Assistant.[/-][+]Great start - next up: stats sensors in Home Assistant.[/+]on May 2, 2025 +1 for sensors. Seems like little point having all of this monitoring but no way to leverage the information.
Reacted by Danie, Kinetic Screen, Mike Bowie, Mattheus and mcdzimThis is exactly what I was looking for too. That way our dashboards can show the index as it varies across the three or more measures, to trigger actions, audible alerts, etc via HA.
Yeah. Very relevant. I was using the Speed Test integration, but I think Orb can replace it easily.
Reacted by DanieYes same request here
I saw it pushes to MQTT, which is good, but I was hoping for a proper service which I can put in my main dashboard. Today I still have to use the older SpeedTest one to get the speed of my Internet link.
And where to configure the MQTT parameters?
@DIMMonchik Sorry, what do you mean?
I found the device and the MQTT service, I already used because Zigbee2MQTT, and I could find the device. After that was easy to add to the dashboard. I think you can edit the dashboard to show just what you want.
Related to that, I would like a native service, not passing by MQTT, at least on the interface, and would be great if I could check my other orbs too.
There are some add-ons that already implement a card in devices & services configurations, like MQTT itself, and Whisper, so it's not impossible.@DIMMonchik Sorry, what do you mean? I found the device and the MQTT service, I already used because Zigbee2MQTT, and I could find the device. After that was easy to add to the dashboard. I think you can edit the dashboard to show just what you want. Related to that, I would like a native service, not passing by MQTT, at least on the interface, and would be great if I could check my other orbs too. There are some add-ons that already implement a card in devices & services configurations, like MQTT itself, and Whisper, so it's not impossible.
when I turn on MQTT, I have these errors in the logs:
`MQTT Host: null
MQTT Port: null
MQTT User: null- MQTT_PAUSE=5
- echo 'MQTT Host: null'
- echo 'MQTT Port: null'
- echo 'MQTT User: null'
- '[' -z null ]
- '[' -z null ]
- '[' -z null ]
- '[' -z null ]
- '[' null '==' null ]
- echo 'Error: Missing MQTT configuration'`
I think you need to enable the integration MQTT with the Mosquitto Broker add-on.
For me, it just works, but because I already had MQTT installed.But yeah, maybe someone uses an external MQTT service, so it would be nice to configure.
Reacted by Bipin Kumar and mcdzimBut yeah, maybe someone uses an external MQTT service, so it would be nice to configure.
I have just such a case - MQTT on another server
Reacted by Bipin KumarOK so using the Modern Circular Gauge card I've created this:
type: custom:modern-circular-gauge entity: sensor.orb_sensor_score secondary: adaptive_state_color: true show_gauge: none tertiary: {} header_position: bottom needle: false grid_options: columns: 6 rows: 3 name: Orb Score icon: mdi:lightning-bolt segments: - from: 0 color: - 240 - 58 - 72 - color: - 249 - 158 - 73 from: 50 - from: 70 color: - 185 - 195 - 76 - from: 80 color: - 121 - 184 - 82 - from: 90 color: - 24 - 176 - 90 adaptive_icon_color: false adaptive_state_color: true show_icon: true show_unit: true show_state: true smooth_segments: falseAnd also with its custom Badges:
type: custom:modern-circular-gauge-badge entity: sensor.orb_sensor_score name: Orb Score show_name: true show_icon: true icon: mdi:lightning-bolt segments: - from: 0 color: - 240 - 58 - 72 - color: - 249 - 158 - 73 from: 50 - from: 70 color: - 185 - 195 - 76 - from: 80 color: - 121 - 184 - 82 - from: 90 color: - 24 - 176 - 90Reacted by Ben Childs, Christian Sirolli, 0xA51F, Danie, vazquezrodjoel, Mike Bowie, Mattheus and Sander van de GraafAlternate version - also integrating the emoji ratings:
type: custom:modern-circular-gauge entity: sensor.orb_sensor_score secondary: adaptive_state_color: true entity: sensor.orb_sensor_score show_gauge: inner segments: - from: 0 color: - 240 - 58 - 72 - color: - 249 - 158 - 73 from: 50 - from: 70 color: - 185 - 195 - 76 - from: 80 color: - 121 - 184 - 82 - from: 90 color: - 24 - 176 - 90 show_unit: true show_state: true tertiary: {} header_position: bottom needle: false grid_options: columns: 6 rows: 3 name: Orb Score icon: mdi:lightning-bolt segments: - from: 0 color: - 240 - 58 - 72 label: 💀 - color: - 249 - 158 - 73 from: 50 label: ☹️ - from: 70 color: - 185 - 195 - 76 label: 😕 - from: 80 color: - 121 - 184 - 82 label: 🙂 - from: 90 color: - 24 - 176 - 90 label: 😍 adaptive_icon_color: false adaptive_state_color: true show_icon: true show_unit: true show_state: true smooth_segments: falseReacted by Mattheus and Sander van de GraafHaving an integration that can connect to other instances of Orb would be nice. I have Home Assistant running as a VM on a machine with a bunch of other containers and services, most of which have integrations that let me see stats in Home Assistant. I have an Orb sensor running in a separate container, and it would be nice to be able to have an integration that could just pull data from that sensor without needing this separate addon.
Reacted by Olivier MignaultYeah, I agree, I ran a sensor in my PC and my Home Assistant, but I care most about the sensor from my PC. Also would be nice to have a sensor in my OpenWrt router.
Reacted by Olivier MignaultBut yeah, maybe someone uses an external MQTT service, so it would be nice to configure.
I have just such a case - MQTT on another server
This, pushing to external dedicated MQTT server (even within lan) should be an option.

This is extremely cool. I'm wonder how hard it would be to get some of the data into Home Assistant proper as devices / sensors? I'm seeing in the logs that MQTT is somehow being leveraged, is that how the data packets are being communicated between Orbs? Is there a way of getting them seen by the MQTT broker?