value_mmol_l bad value ?

[Leter-Pustig]

Thanks to all contributors for this great work.

Checked state of variable sensor.user_name_glucose_level in Developer tools -> states.
I found a possible glitch, value_mmol_l and value_mg_dl seem to be the same:

state_class: measurement
value_mmol_l: 184
value_mg_dl: 184
target_high_mmol_l: 10
target_low_mmol_l: 3.9
target_high_mg_dl: 180
target_low_mg_dl: 70
trend: decreasing
measurement_timestamp: "2026-02-19T21:00:58+00:00"
unit_of_measurement: mg/dl
icon: mdi:arrow-bottom-right-thick
friendly_name: glucose

In current example I think that value_mmol_l should be a bit above 10 instead of 184

Please correct me if I'm wrong.

using Version 1.0.0

[PTST]

I am unable to reproduce this issue on my end. Do you use mmol/l or mg/dl as your native measurement in the app? And which unit is the integrations set to use?

But yes, that mmol value is definitely wrong unless you are in a diabetic coma or similar right now.

[Leter-Pustig]

Do you use mmol/l or mg/dl as your native measurement in the app?

mg/dl

And which unit is the integrations set to use?

[PTST]

My app is set to use mmol, and I guess something acts differently in the api then. I will look into it tomorrow and see if i can reproduce it if changing the units in my app as well

[Leter-Pustig]

I am unable to reproduce this issue on my end.

Well, it is not really an issue, as provided values in mg/dl are fine.
Maybe setting the integration to mmol/l changes sth ?
Will try.

Don't know if my region set to EU has impact ( api server to use ? )

[PTST]

It seems that you cannot change your unit of measurement in the app at all 😑

If your are up for it i will send some commands for you to execute tomorrow that will call the api. But that would include sharing the returned data with me. So that is up to you to decide whether you would be willing to do so?

[Leter-Pustig]

If your are up for it i will send some commands for you to execute tomorrow that will call the api. But that would include sharing the returned data with me. So that is up to you to decide whether you would be willing to do so?

If your GlassMarble does not tell you a possible cause, the only chance to find a cause seems to debug.

So that is up to you to decide whether you would be willing to do so?

Yes, I will :-)

[Leter-Pustig]

changed to mmol/L

and reloaded the integration
only change:

state_class: measurement
value_mmol_l: 146
value_mg_dl: 146
target_high_mmol_l: 10
target_low_mmol_l: 3.9
target_high_mg_dl: 180
target_low_mg_dl: 70
trend: stable
measurement_timestamp: "2026-02-19T21:44:59+00:00"
unit_of_measurement: mmol/L
icon: mdi:arrow-right-thick
friendly_name: glucose

Will try to call api with your input ( hope that I will be able 2 ... )

[PTST]

I have released v.1.1.6 which should fix this issue.
I had some wrong assumptions on how the api behaved.
Please let me know whether this release fixes the issue for you, otherwise please just reopen this issue

[Leter-Pustig]

I have released v.1.1.6 which should fix this issue. [...] Please let me know whether this release fixes the issue for you,

Looks like the value is completely lost:

Will open an issue as requested

[PTST]

Could you please provide me with the logs from
https://my.home-assistant.io/redirect/logs/

[Leter-Pustig]

This error originated from a custom integration.

Logger: homeassistant
Source: custom_components/libreview/sensor.py:147
integration: LibreView (documentation, issues)
First occurred: 2:24:35 pm (1 occurrence)
Last logged: 2:24:35 pm

Error doing job: Task exception was never retrieved (task: None)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 294, in _handle_refresh_interval
await self._async_refresh(log_failures=True, scheduled=True)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 533, in _async_refresh
self.async_update_listeners()
~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 200, in async_update_listeners
update_callback()
~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 613, in _handle_coordinator_update
self.async_write_ha_state()
~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1018, in async_write_ha_state
self._async_write_ha_state()
~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1163, in _async_write_ha_state
) = self.__async_calculate_state()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1074, in __async_calculate_state
if extra_state_attributes := self.extra_state_attributes:
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/libreview/sensor.py", line 157, in extra_state_attributes
"value_mmol_l": self.get_mmol_l_value,
^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/libreview/sensor.py", line 147, in get_mmol_l_value
return self.gcm_value_in_mg_per_dl / 18.0
^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'GlucoseSensor' object has no attribute 'gcm_value_in_mg_per_dl'