I just started looking at migrating mcsSprinklers to HS4. mcsSprinklers was introduced to HS during the original HS days where the method of device identification was a variant of the X10 HouseCode-DeviceCode. While there was discussion about retaining the HS Code property, it seems it will be depreciated at time of HS4 release.
When the HS3 .hsd file is imported there is no place in HS4 to hold the HS3 Code property so this information is lost. Since mcsSprinklers uses Code as its primary key for identification of a user setup it means that the user setup data will be lost. I recognize that a new means will be needed within mcsSprinklers for Code identification, but the problem is how to get the data during import or plugin initialization so the plugin can reconstruct the user information.
Do provisions exists for getting access to HS3 device data from HS4 plugin? Is the author to do SQL queries of the HS3 .hsd file? Does a script need to be developed to run on HS3 that spits out the Code/Ref relationships of all devices?
When the HS3 .hsd file is imported there is no place in HS4 to hold the HS3 Code property so this information is lost. Since mcsSprinklers uses Code as its primary key for identification of a user setup it means that the user setup data will be lost. I recognize that a new means will be needed within mcsSprinklers for Code identification, but the problem is how to get the data during import or plugin initialization so the plugin can reconstruct the user information.
Do provisions exists for getting access to HS3 device data from HS4 plugin? Is the author to do SQL queries of the HS3 .hsd file? Does a script need to be developed to run on HS3 that spits out the Code/Ref relationships of all devices?
Comment