The only thing I can think of is deleting the invalid link record line that is shown for that device.
This is the result of the Motion Sensor not supporting the normal Peek/Poke commands used to read/write link records. The Motion Sensor and the TriggerLinc are the only SH devices I know of that have not implemented Peek/Poke. It is a valid thing to do as those commands have been “depreciated”. However, this means that the I2 Extended command 2F ALDB must be used to read/write link records in the Motion Sensor and the TriggerLinc which the EZSrve does not currently support.
Don’t know if that is why the device entry is behaving oddly. It is the only thing that looks odd about the device entry.