The scan interval didn’t help, but a firmware update did seem to help. Also I had left in an “unlocked” state, but pulling my linknlink app today I see it’s locked again, which is interesting. I wonder if it does updates in the background as well.
I’m now getting a response in the 1-3 second range over modbus which is 100% acceptable, though it seems like modbus communications randomly drop off, especially when I’m looking at something in the linknlink app, which is less acceptable.
for my configuration with the eMotion I went with:
modbus:
- name: garage_motion
type: tcp
host: [My_ip_address]
port: 502
sensors:
- name: garage_motion
unique_id: garage_motion
address: 802
scan_interval: 1
- name: garage_NoPerson_time
unique_id: garage_noperson_time
address: 832
Other fun Modbus addresses I’ve found
0-2 - Hexadecimal Mac address
8 - Unsure but has data
9 - Unsure but has data
29 - Firmware version
1300 and following - name of access point stored as text. Each register holds two characters. I'm not sure what the last address it uses is, probably 1331 which would give it 32 addresses for a max AP name length of 64 characters.
1332 and following - password for wifi stored as plain text. Each register holds two characters (this really should be hashed if anyone from LinknLink reads this threads, storing the password as plain text is a major no-no)