Hello,
it is not a normal behaviour of a device to change it’s engine id, therefore this case has to be handled by the application. If you get a timeout, you can use the v3MP::remove_from_engine_id_table() functions to remove the currently cached value and then the new engine id can be discovered and added again.
Kind regards,
Jochen