Integrating Xiaomi Mi Scale

[Himdola]

When i install the HA add-on and configure, save and i will start the addon i get this error:

This add-on does not expose configuration for you to mess with…

I dont see anything on the logs.

[lolouk44]

That error message doesn’t look familiar at all. Are you sure you installed my add-on?

[Himdola]

Yes it is the good one.

Xiaomi Mi Scale

Current version: 0.3.6

[lolouk44]

Please raise an issue on my github repo

[Himdola]

I have added now via the Official integration on HA bodymiscale integration. I can there add users and give the high CM. But there is no option to give some KG greather than or Lower than. How will this app now detect the users?

How will be detect that integration users?
Why are you not use that integration, what is missing there?

[lolouk44]

That is why I have built my integration, so that multiple users can use it

[Himdola]

Very interested can you please share your config? I want also see some last months history. My grafana with infulxDB is up and running.

[Himdola]

It is now working fine, no idea how this is now solved, Do you have also an option how i can see the last months weight on a Graph?

[lolouk44]

Click on the entity in your dashboard, then click on show more on top right of the chart
Alternatively you can indeed to track this via grafana:

Complete guide on setting up Grafana/InfluxDB with Home assistant using official Docker images

I know there are already a few tutorials on setting up InfluxDB and Grafana with Home Assistant, but they did not meet my requirements. Specifically, I did not want to use third-party images, which may not be maintained, and not use panel iframes to display the plots. Moreover, many of the tutorials still show the InfluxDB admin GUI, which is no longer available. So, here’s my version of how to get everything set up with the official images. Run the following command to start the InfluxDB con…

[Himdola]

That is ok, but i need to have the metric settings etc. that coming from MQTT and add it to Grafana, how to show that data on a dashboard, that part is very difficult.

[Akira]

Same here. Also interested in getting the add-on to work with an esp32 Bluetooth proxy.

[dpaganin (Diego)]

Hi Guys, im new here, can you please get some help? the info below come from Xiaomi Mi ScaleXiaomi Mi Scale.

im stuck, i step on scale but nothing happen.

2023-06-22 16:10:29 - Loading Config From Add-On Options…
2023-06-22 16:10:29 - (INFO) -------------------------------------
2023-06-22 16:10:29 - (INFO) Starting Xiaomi mi Scale v0.3.6…
2023-06-22 16:10:29 - (INFO) Loading Config From Options.json…
2023-06-22 16:10:29 - (WARNING) Invalid logging level provided, defaulting to INFO…
2023-06-22 16:10:29 - (INFO) Config Loaded…
2023-06-22 16:10:30 - (INFO) MQTT Discovery Setup Completed…
2023-06-22 16:10:30 - (INFO) -------------------------------------
2023-06-22 16:10:30 - (INFO) Initialization completed, step on scale to wake it up and get a weight value sent… Make sure the scale is within reach…

[polenquick]

I’ve just the same problem ;/
added MQTT and MiScale add-on

[Ernst]

I have added MiScale support to the Xiaomi BLE integration, so you can now use it directly in HA

[DonNL]

Thanks @Ernst. I got it to work. However, it only shows weight, no impedance. I have a composition scale 2.

Edit: Nvm. Works now too. Low batteries probably.

[mcnguyen33r (Minh Chau)]

Thanks for your sharing

[atv]

Not sure what I am doing wrong here. Crosspost from GitHub issue.

Keep getting this:

mi-scale         | KeyError: 'options'
mi-scale         | TERM environment variable not set.
mi-scale         | Traceback (most recent call last):
mi-scale         |   File "/opt/miscale/Xiaomi_Scale.py", line 122, in <module>
mi-scale         |     data = json.load(json_file)["options"]
mi-scale         | KeyError: 'options'

My docker file is:

  mi-scale:
    image: lolouk44/xiaomi-mi-scale:latest
    container_name: mi-scale
    restart: always
    network_mode: host
    privileged: true
    volumes:
      - ./mi-scale:/data
      - /var/run/dbus/:/var/run/dbus/:ro #needed for bleak
    

Been over and over on this but can’t find out what’s wrong. And the options.json file is there obviously. I have placed the options file in data, data/options, opt/miscale/ etc but no dice. I must be something missing in my understanding. In the python code it refers to options.json but then later it does a json load of options, maybe a bug? @lolouk44

Nevermind, figured out the options.json from the add-on differs in that it needs an another dictionary entry called options. Loads now.

Starting mi-scale ... done
Attaching to mi-scale
mi-scale         | TERM environment variable not set.
mi-scale         | 2024-02-20 10:10:27 - (INFO) -------------------------------------
mi-scale         | 2024-02-20 10:10:27 - (INFO) Starting Xiaomi mi Scale v0.3.5...
mi-scale         | 2024-02-20 10:10:27 - (INFO) Loading Config From Options.json...
mi-scale         | 2024-02-20 10:10:27 - (WARNING) Invalid logging level provided, defaulting to INFO...
mi-scale         | 2024-02-20 10:10:27 - (INFO) Config Loaded...

Not getting any messages on console yet though, maybe because of invalid logging level? Also no entities created yet, so I’m guessing something is not working yet/passing stuff to MQTT.

All working now, wrong MQTT password.

[marnau (Marius Naujikas)]

Hello,

I did everything. Installed add on, configured, configured configuration yaml. In add on log I see that poeple is on scale and see all info about it, but in HA entity of weight and bmi not appear, what is wrong?
2024-03-14 08:49:53 - (INFO) Initialization completed, step on scale to wake it up and get a weight value sent… Make sure the scale is within reach…
2024-03-14 15:26:12 - (INFO) Publishing data to topic miscale/Martynasnau/weight: {“weight”:40.80,“weight_unit”:“kg”,“bmi”:17.89,“basal_metabolism”:1280.72,“visceral_fat”:1.00,“timestamp”:“2024-03-14T15:26:12+00:00”}
2024-03-14 15:26:12 - (INFO) Data Published …

In mosquito broker log I see too some info of connection:
2024-03-14 15:26:12: New connection from 192.168.8.155:44395 on port 1883.
2024-03-14 15:26:12: New client connected from 192.168.8.155:44395 as auto-C03B54B5-6170-BCD7-C47C-203E03FD3655 (p2, c1, k60, u’marius’).
2024-03-14 15:26:12: Client auto-C03B54B5-6170-BCD7-C47C-203E03FD3655 disconnected.

But no entity appear on HA.

CONFIGURATION:
HCI_DEV: hci0
BLUEPY_PASSIVE_SCAN: false
MISCALE_MAC: 88:22:B2:E7:F3:2A
MQTT_PREFIX: miscale
MQTT_HOST: 192.168.8.155
MQTT_USERNAME: marius
MQTT_PASSWORD: xxxxx*x
MQTT_PORT: 1883
MQTT_RETAIN: true
MQTT_DISCOVERY: true
MQTT_DISCOVERY_PREFIX: homeassistant
MQTT_TLS_CACERTS: Path to CA Cert File
MQTT_TLS_INSECURE: false
DEBUG_LEVEL: debug
USERS:

• NAME: Mariusnau
  SEX: male
  GT: 85
  LT: 105
  HEIGHT: 190
  DOB: “1984-07-27”
• NAME: Martynasnau
  SEX: male
  GT: 35
  LT: 50
  HEIGHT: 151
  DOB: “2013-07-05”

CONFIGURATION.YAML
mqtt:
sensor:

• name: “Mariusnau Weight”
  state_topic: “miscale/Mariusnau/weight”
  value_template: “{{ value_json[‘weight’] }}”
  unit_of_measurement: “kg”
  json_attributes_topic: “miscale/Mariusnau/weight”
  icon: mdi:scale-bathroom
  state_class: “measurement”
• name: “Mariusnau BMI”
  state_topic: “miscale/Mariusnau/weight”
  value_template: “{{ value_json[‘bmi’] }}”
  icon: mdi:human-pregnant
  unit_of_measurement: “kg/m2”
  state_class: “measurement”
• name: “Martynasnau Weight”
  state_topic: “miscale/Martynasnau/weight”
  value_template: “{{ value_json[‘weight’] }}”
  unit_of_measurement: “kg”
  json_attributes_topic: “miscale/Martynasnau/weight”
  icon: mdi:scale-bathroom
  state_class: “measurement”
• name: “Martynasnau BMI”
  state_topic: “miscale/Martynasnau/weight”
  value_template: “{{ value_json[‘bmi’] }}”
  icon: mdi:human-pregnant
  unit_of_measurement: “kg/m2”
  state_class: “measurement”

Whats the problem?

[Himdola]

Guys by me all the impedence value is unavailable, what can be the reason? With the loluk mqtt custom integration i get well this data.

[haaahaha]

There are more elegant solutions that differentiates persons by weight in HA instead of in ESPHome

Template sensor showing "unknown"

There is no need for a triggered template sensor. This is redundant: Templates are already monitored for state changes of the included sensors. This will do exactly the same thing: template: - sensor: - name: Weight Eq and Above Threshold unique_id: f700e52a-1304-4d47-8bea-5b2c8f4049fe unit_of_measurement: kg device_class: weight state: > {% set weight = states('sensor.bluetooth_proxy_miscale_weight') | float %} {{ weight if weight…

Template sensor showing "unknown"

That template isn’t going to achieve anything, but I’m not sure what your end goal is either. If you want to track every weight that is below 80 on one entity, and every weight that is above (or equal to 80) on another entity, this would be one option: - trigger: - platform: state entity_id: sensor.bluetooth_proxy_miscale_weight not_to: - unavailable - unknown variables: threshold: 80 sensor: - name: Weight Eq and Above T…