krahabb
commented
1 year ago Hello @R1200G, Thank you for reporting this. The native position reported in the attributes is, like you guessed, the position according to the hardware but, in my tests, this hardware position was always reporting either 0 (closed) or 100 (open) with no values in between. Now, maybe things have changed through a recent firmware update but, nevertheless, the device cannot (or shouldnt be able to) report a correct position because it lacks any sort of sensor to read the effective actual position of the shutter. These kind of devices usually estimate the position based on the 'time of run' and are prone to accumulating errors which are only resolved when they run to the end a couple of times.
This is how meross_lan itself calculates the emulated position in software but, of course, this estimate suffers a lot from latencies in communication expecially when you bind the device to meross_lan through HTTP (which is the only option if you still have your meross paired to the Meross App). If you instead bind the device to a local MQTT these latencies are greatly reduced and calculations can provide a better result even though I see this is not viable for many users (i.e. unbinding from the Meross App in order to bind to a local MQTT).
However, this 'software position' proved to work correctly for the same HTTP binding scenario for other users so I suggest you to try (or investigate) this:
- when the shutter is closed (in real), start another 'close command' on HA so the shutter 'emulated' position could realign with the real value (i.e. move to 0 and stick there )
- now, if this works, you should then have correct position reporting from now on in HA too
- also, if not already, try to set the 'opening time' and 'closing time' for the device to the right amount. The values you set on the app should be correctly read by meross_lan (in the picture they are at 18.1 and 17.7 seconds so I guess you already set these accordingly but..). meross_lan uses these values to interpolate and estimate the actual position when the device moves. These values should be set a little larger (say 10%) than the real effective time of run in order for the algorithm to try to 'catch up' with the real position. Of course, the calculations will never be correct, and you will get and accumulate increasing errors if you start playing with the shutter opening and closing it several times around a mid position (i.e. never reaching the physical full open or close) but in real scenarios, shutters runs are most of the times full runs
- if you observe the 'Position native' attribute is reporting a better estimate (like I said, this used to report only 0 or 100 even when the shutter was halfway) then I will happily update meross_lan to use this value instead of the software calculated one. Again, I'm pretty sure this native value is computed too, exactly the same as the meross_lan calculations, but maybe it is better!
R1200G
lucas-TT
Hi there,
I´m quite new to HA. I´didnt find the issue yet, so hopefully you guys can help me.
I integrated my Meross Shutters in HA via the cloud and meross_lan integration. Problem:
The Position which is displayed in HA lovelace or directly at the entity is always wrong (not the same like in the Meross app or in the Homekit app on the iPhone, this is the real position). I found out, that when i looked at the attribute of the Shutter (entity) there is always the correct positon displayed (Position Native).
In my case (shown on the picture) the shutter is fully closed.
How can i fix that?
Thanks a lot,
R1200G