There is something I don't understand. Its relative to the migration of devices and events. I understand the issues with plugins and scripts, BUT events and devices? All of the events and devices are represented in a machine readable form (the HS 1.7 xml file). Why should one want/need to labourously hand generate them into a fesh DB (mdb). If HS2 can not convert that to its new DB format as a straight forward task then there is something fundamentally wrong. Its a simple transliteration problem (not even translation, just a change in the representational form).
I have, as I suspect most others also do, a single machine that has all the physical connectivity to my house. I have no problem moving between HS 1.7 and HS 2.0 on the same machine (either direction as often as I need to). My plan is to start with a fresh build of HS 2.0 (1.7 is running fine) after a copy all of the Homeseer folder into another folder (Homeseer1). When I have HS2, running in the Homeseer folder, reasonably for events and devices, I will copy that into a folder called Homeseer2. I will then add plugins and scripts. My advantage is that I wrote all of my own plugins (except for 2 for which I have workarounds) and scripts. I do not plan to convert the scripts or plugins to .Net until all is very stable.
My greatest concern is with the new Speaker application. I only want to run it on the main system as the house already has ampifiers and speakers integrated with the HS server. I hear an awful lot of static relative to the performance of that app, or should I say its performance/reliability.
Comments? Experiences?
I have, as I suspect most others also do, a single machine that has all the physical connectivity to my house. I have no problem moving between HS 1.7 and HS 2.0 on the same machine (either direction as often as I need to). My plan is to start with a fresh build of HS 2.0 (1.7 is running fine) after a copy all of the Homeseer folder into another folder (Homeseer1). When I have HS2, running in the Homeseer folder, reasonably for events and devices, I will copy that into a folder called Homeseer2. I will then add plugins and scripts. My advantage is that I wrote all of my own plugins (except for 2 for which I have workarounds) and scripts. I do not plan to convert the scripts or plugins to .Net until all is very stable.
My greatest concern is with the new Speaker application. I only want to run it on the main system as the house already has ampifiers and speakers integrated with the HS server. I hear an awful lot of static relative to the performance of that app, or should I say its performance/reliability.
Comments? Experiences?
Comment