znuttyone

Ok, that explains it. So if you perform an upgrade of ISY from one version to the next and then viewed the event log you would only see the event since the reboot as you would need to establish a new console session. Would be nice if this was persistent across console sessions. It also would be nice to view the 'Tools/Log' and 'Tools/ Error Log', without the need to actually download it and open with separate viewer

I had not seen the event log, nice. looks like it is of limited duration, seems to shows only 1 hour, is that expected?

Positive ,I was expecting it to change but it never did until after I upgraded and only after the reboot of ISY and restarting the console, at that point the writing device xx.xx.xx dialog came up which was the address of the new device, at that point when I checked the address associated with the named device I replaced, the address was changed from the old to the new. Was not sure what the replace function would do, so I took precautions, on the next one will attempt without making changes to see the real benefit of the feature as I really like the design of the feature. The console show now pending changes (writes) green icon. The old device is no longer show anywhere in the console that i can see now that the replacement is complete.

BTW prior to replacing the old device I removed it from all scenes and controllers so timing should have been fast for the activities. I did wait for over ~10mins prior to giving up and upgrading. I would like to see one or both of the following enhancements to allow users better understanding of what is occurring and self diagnostics. 1) a log that shows all events initiated and responses and or errors. Think Call stack with parameters passed to sub routines and response 2) better status displayed on device updates and completion that are being requested by ISY

Your description of the expected behavior is what I would have expected. The deviation from this is that the named device address did not get changed and remained pointed to the address of the device that went bad, which seems to indicate that something went wrong and so there were pending updates that prevented any new changes to that named device. Is there a log that you want to determine root cause?

Just updated to 3.3.10 , after the reboot, noticed a status window popped up with ISY attempting to write to the new module I had installed and discovered under 3.3.8, now the original named module was truly replaced and functions as expected. Not sure if this was some 3.3.8 issue or if it still exist in 3.3.10 and the reboot for the upgrade solved the problem.

had a similar experience. Module: 944i release: v3.3.8 Replace function does not work Reproduction: 2473SWH/v4.9 removed to simulate bad unit Add new 2473SWH with new address Link to ISY, new unit shows up in console Attempt to replace using replace function. system will warn not to power off.. behavior: newly discovered module will disappear in the console and old unit will remain in the console with no changes. subsequently if you attempt to discover the module again, it will discover, but never shows up in the console again. Now cannot get the new module to add, and the old module cannot be deleted, renamed.