added moving state to home assistant for TS130F Curtain/blind switch

[cmiguelcabral]

Does this seem less intrusive?

I would like to have someone with different covers test this version.
But people need to be willing to do it as I have more than 30 covers of this model, but don't have any other.

[Koenkk]

Thanks, asked for validation in #15873 (comment)

[cmiguelcabral]

Thanks, asked for validation in #15873 (comment)

Don't you intend to integrate this into the master?

[Koenkk]

@cmiguelcabral dev will be merged to master with every new 1st of the month release.

[cmiguelcabral]

@cmiguelcabral dev will be merged to master with every new 1st of the month release.

Hi,
Yes, I know, it's not what I meant.
I meant to ask if you intend to integrate this on zigbee2mqtt. :-)

[Koenkk]

@cmiguelcabral yes, the changes are already in the dev branch since 8 Jan: 9c4abb6

[Drafteed]

I don't really understand the purpose of this change - we introduce a duplicate state. Why not just rename the moving to motor_state in TS130F Curtain/blind?

[Drafteed]

Or we could also do this by changing just one line:

const motorState = allExposes?.find((e) => e.type === 'enum' && 
    ['motor_state', 'moving'].includes(e.name) && e.access === ACCESS_STATE);

[Drafteed]

#16324