Non-compliant MiOT devices.

[Wh1terat]

It is so very common that devices have broken or unimplemented specifications, relying on hacky methods within the mihome react plugins.

There is absolutely no way for users to communicate these issues with makers and they seem uninterested in fixing them of their own volition.

The latest issue has really irked me though because unlike other ecosystem products, this seems to be a Xiaomi product.

xiaomi.feeder.iv2001

Problem(s):

SIID	PIID	Name	Problem
2	7	target-feeding-measure	Not used
2	8	feeding-measure	No read/write access defined
2	16	feeding-type	No read/write access defined
2	18	eaten-food-measure	Not used, relies upon petFeederEventApi instead.
2	20	eaten-food-measure	Not used, relies upon petFeederEventApi instead.
2	22	eaten-food-measure	Not used, relies upon petFeederEventApi instead.
2	23	eaten-food-measure	Not used, relies upon petFeederEventApi instead.
2	17	current-time	No read/write access defined , Not used, relies upon petFeederEventApi instead.
2	21	current-time	No read/write access defined , Not used, relies upon petFeederEventApi instead.
2	24	current-time	No read/write access defined , Not used, relies upon petFeederEventApi instead.
2	25	current-time	No read/write access defined , Not used, relies upon petFeederEventApi instead.
4	1	battery-level	Defined as a bool, but type spec is uint8, Not used, relies upon standard consumables endpoint]
6	1	desiccant-left-level	Not used, relies upon standard consumables endpoint.
6	2	desiccant-left-time	Not used, relies upon standard consumables endpoint.

As well as having duplicate names within a single siid:

So much effort has gone into this ecosystem and the miot specification but it all falls down when makers are not held to standards.