Instead of numeric sensors with a unit of measure, text sensors are created
Invalid sensor:


Сorrect sensor:

Home Assistant 0.109.0
DSM 5.2
configuration.yaml
@Quentame , you just don’t get rid of me :-)
Hey there @ProtoThis, @Quentame, mind taking a look at this issue as its been labeled with a integration (synology_dsm) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)
Yeaaayyy man, when will you let me alone ? :joy: :joy: :joy:
Yeah sure, this is a bug, actually I am quite sure this was here before 0.109.0
Will fix shortly (as always you know) with other issues.
Volume data will be shown as Terabytes with 2 digits, I don't think there is a lot of people with less than a Tb on a NAS.
Well, I still have gigabytes ...
I seen yah ... 2 digits are for you actually :blush:
You gonna get 0.45 TB and 0.08 TB 🤷♂️
Not bad no ?
People from #34861 helped me to solve a storage issue with SHR disk dedundancy.
I've added their data to the library tests, check volume_size_total from https://github.com/ProtoThis/python-synology/blob/master/tests/test_synology_dsm.py we are getting from 3Tb to 35Tb.
I think you start with 500Gb, but you gonna get more in the future :wink:
I still want HA to appear as in DSM 😉

I think you start with 500Gb, but you gonna get more in the future 😉
I have like this


"container" : "internal",
"device_type" : "shr_with_1_disk_protect",
"disk_failure_number" : 0,
"disks" : [ "sda", "sdb", "sde" ],
"id" : "pool_1",
"is_actioning" : false,
"is_writable" : true,
"maximal_disk_size" : "0",
"minimal_disk_size" : "249953402880",
"num_id" : 1,
"pool_child" : [
{
"id" : "volume_1",
"size" : {
"total" : "482379890688",
"used" : "83747278848"
}
}
],
"pool_path" : "",
"progress" : {
"percent" : "-1",
"step" : "none"
},
"size" : {
"total" : "490221862912",
"used" : "490221862912"
},
Oh yeah, so you have more than a 1Tb !