| Posted: Tuesday Sep 17th, 2013 08:31 am |
|
1st Post |
broadk
Member
| Joined: | Sunday Jul 4th, 2010 |
| Location: | |
| Posts: | 3 |
| Status: |
Offline
|
back to top
|
Does anyone know which version of the C-Bus firmware (if any) that supports the request_zone_name C-Gate command?
According to the C-Gate manual some alarm panels will respond to a request_zone_name message with a zone_name event. I was hoping to use this feature to avoid the need to keep Comfort and C-Bus toolkit in sync with regards to zone names. This is to improve my Indigo/C-Bus plugin.
Thanks
kieran
|
| Posted: Tuesday Sep 17th, 2013 12:36 pm |
|
2nd Post |
tech07
Administrator
| Joined: | Thursday Jan 29th, 2009 |
| Location: | Singapore |
| Posts: | 106 |
| Status: |
Offline
|
back to top
|
I think that command is not supported in UCM/Cbus now
Why would you need this feature?
|
| Posted: Tuesday Sep 17th, 2013 01:17 pm |
|
3rd Post |
broadk
Member
| Joined: | Sunday Jul 4th, 2010 |
| Location: | |
| Posts: | 3 |
| Status: |
Offline
|
back to top
|
My code currently generates devices in Indigo based on the C-Gate project. However, for integration with Comfort this requires me to replicate all the zone configuration into the C-Bus toolkit. I would rather be able to query Comfort directly via request_zone_name to avoid needing to manage the configuration in two places.
This is not an essential feature but rather simply a nice to have.
Thanks.
|
| Posted: Tuesday Sep 17th, 2013 01:50 pm |
|
4th Post |
tech07
Administrator
| Joined: | Thursday Jan 29th, 2009 |
| Location: | Singapore |
| Posts: | 106 |
| Status: |
Offline
|
back to top
|
I assume your code runs in a computer. Could it pull the zone names from the cclx file?
|
| Posted: Tuesday Sep 17th, 2013 02:00 pm |
|
5th Post |
broadk
Member
| Joined: | Sunday Jul 4th, 2010 |
| Location: | |
| Posts: | 3 |
| Status: |
Offline
|
back to top
|
The plugin itself runs on a Mac and hence the user would likely need to copy the file across. Nonetheless there are many ways to solve this problem and I certainly have a working solution at this time.
I was merely surprised to find this aspect of the specification missing.
|
|
