For this to have happened in the first place, something bad is going on with the Z-Stick apparently. This should not happen unless there is some corruption during replication, or if the interface was Erased, or if you did a restore after editing one of the .ZWave files. Those are the only times that the HomeID can be changed, AND that is only possible if your Z-Stick has the installer library, and most of them do not (Aeon created an installer library version, but it did not appear correct to us originally, so they never released it - it does work though.)
So here are the problems - so many things have happened since the original mishap that it is unlikely that it can be recovered such that you do not lose anything - events that reference Z-Wave devices will certainly have to be re-created or edited.
The first thing to do is to figure out which HomeID is the right one, and if the controller is not coming up when initialized with the right HomeID, why is that happening. HomeIDs as I mentioned earlier do not change on their own. The devices in your home should not be affected, so the good news is that if we can get your controller back to being the HomeID that it once was, you will be all set.
I recommend restarting/resetting the interface, if you have not already done that. Do not erase it, but use the controller management page to restart it. Then, shut down HS3 or the plug-in, and restart that, and see how the controller comes up and which HomeID that it has.
If the plug-in finds HomeSeer devices that do not have corresponding information in the Z-Wave database, it will try to read information from the HomeSeer device to re-create the information in the Z-Wave database. If this is successful, then you only have to do a rescan to help the Z-Wave database get populated with some of the other device details not stored in the HomeSeer devices. Conversely, if there is information in the controller about nodes that do not have corresponding HomeSeer devices, then an Import will re-create those.
So once the controller is straightened out, the rest can be fixed. We just need to know for certain which HomeID is the one that all of your devices have. It will be good to also know what type of controller library you have so we know what options exist for fixing things. If there was TEMPORARY corruption and the plug-in got a bad reading for the HomeID, that is how you will have another HomeID appearing in the networks list. We can remove the invalid network later. So after you restart the interface and restart HS3/plug-in, go to the controller management page, and under your controller interface, expand the controller node information and provide that info to me either in email or here, and that will help sort things out too.
So here are the problems - so many things have happened since the original mishap that it is unlikely that it can be recovered such that you do not lose anything - events that reference Z-Wave devices will certainly have to be re-created or edited.
The first thing to do is to figure out which HomeID is the right one, and if the controller is not coming up when initialized with the right HomeID, why is that happening. HomeIDs as I mentioned earlier do not change on their own. The devices in your home should not be affected, so the good news is that if we can get your controller back to being the HomeID that it once was, you will be all set.
I recommend restarting/resetting the interface, if you have not already done that. Do not erase it, but use the controller management page to restart it. Then, shut down HS3 or the plug-in, and restart that, and see how the controller comes up and which HomeID that it has.
If the plug-in finds HomeSeer devices that do not have corresponding information in the Z-Wave database, it will try to read information from the HomeSeer device to re-create the information in the Z-Wave database. If this is successful, then you only have to do a rescan to help the Z-Wave database get populated with some of the other device details not stored in the HomeSeer devices. Conversely, if there is information in the controller about nodes that do not have corresponding HomeSeer devices, then an Import will re-create those.
So once the controller is straightened out, the rest can be fixed. We just need to know for certain which HomeID is the one that all of your devices have. It will be good to also know what type of controller library you have so we know what options exist for fixing things. If there was TEMPORARY corruption and the plug-in got a bad reading for the HomeID, that is how you will have another HomeID appearing in the networks list. We can remove the invalid network later. So after you restart the interface and restart HS3/plug-in, go to the controller management page, and under your controller interface, expand the controller node information and provide that info to me either in email or here, and that will help sort things out too.
Comment