Closed JensHoRi closed 7 months ago
It could happen because binding calculates device address from provided data (serial number, manufacturer etc) which then is matched against device address reported over serial interface. Key is registered with first address which might require tweaking. I’d wait until #45 so we will have a way to compare frame and key assignment in binding code.
I believe was a one time only situation
Under the neath all keys are shared because they are being held by library within serial or tcp connection. This means that in case of miss-configuration or two things having same device address but different encryption keys one will work and other will fail.
Device got already actual data went suddenly to offline "wrong keys". Save configuration (change in label eg) let it come online again
Maybe only a onetime issue, if no further notices like this could be closed again.