Blade,
Something that is really bothering me I am hoping you can get around to correcting soon. When you create the devices for BLRussound zones, you are not grouping the devices properly using the parent/child relationships. When I look at the Russound devices you create, I have 156 devices that are not grouped, have no location set, have no device API information, and can only be differentiated by the name of the device.
Although HomeSeer/HSTouch does not do anything with the Source Switch API, you can see in HSTouch what we have done with it being able to find and control thermostats and door locks. It should eventually be able to do the same with Music and Source Select devices. As such, the API should be set to Source Switch, and the device type should be one of the eDeviceType_SourceSwitch values. Each Zone should have a root device, and it can be a plain/unused device or you could make the "Name" device the root, and then each of the other devices should be associated as child devices, and that allows for them to appear as a group in the browser. You could then use the name value to list (for example) the volume as "Family Room Volume" rather than "c1z3 Volume". I am not interested in having to look up which controller and which zone everything is just so I can rename 156 devices.
Give it some thought and eMail me if you have questions, but this would be really good if you could make those changes.
Something that is really bothering me I am hoping you can get around to correcting soon. When you create the devices for BLRussound zones, you are not grouping the devices properly using the parent/child relationships. When I look at the Russound devices you create, I have 156 devices that are not grouped, have no location set, have no device API information, and can only be differentiated by the name of the device.
Although HomeSeer/HSTouch does not do anything with the Source Switch API, you can see in HSTouch what we have done with it being able to find and control thermostats and door locks. It should eventually be able to do the same with Music and Source Select devices. As such, the API should be set to Source Switch, and the device type should be one of the eDeviceType_SourceSwitch values. Each Zone should have a root device, and it can be a plain/unused device or you could make the "Name" device the root, and then each of the other devices should be associated as child devices, and that allows for them to appear as a group in the browser. You could then use the name value to list (for example) the volume as "Family Room Volume" rather than "c1z3 Volume". I am not interested in having to look up which controller and which zone everything is just so I can rename 156 devices.
Give it some thought and eMail me if you have questions, but this would be really good if you could make those changes.
Comment