Any idea if the modbus integration could allow for using attributes but states? Would come handy if using the
count + data_type: custom + structure
since the length limit of state is sort of identical to filename lengths in the old 8bit days.
e.g. something like this:
modbus:
count: <number>
data_type: custom
structure: ">xxxxxxxx"
# sort of a feature to select if using state or attributes
use_attributes: true
which should result in the response shouldn’t end up with a csv which likely won’t fit into a state, throwing an error, but simply create a bunch of attributes an assign the values returned from the modbus read requesst.
Problem now is you might think that the csv reponse might fit within 255chars upon testing, bit in case you’re close to the 255 chars and some values do change you run into problems.
Fom scratch I’d say it should have been like this anyway if using structure: but implementing it that way would result in a breaking change thus surely not the ideal way.