Ticket #189 (new enhancement)

Opened 8 years ago

Last modified 8 years ago

Enumeration of supported protocols

Reported by: torbjörn lönnemark <tobbez@…> Owned by:
Priority: minor Milestone: 2.1.3
Component: telldus-core Version: 2.1.1
Keywords: Cc:
Blocked By: Blocking: #190
Platform: All Sensitive:
Verified by Telldus: yes

Description

It would be useful to be able to enumerate the protocols supported by telldusd using the telldus-core library.

This would probably require a bit of work since there doesn't seem to be any code present for this in the daemon at the moment.

Attachments

0001-telldus-core-Add-support-for-protocol-enumeration.patch Download (5.6 KB) - added by torbjörn lönnemark <tobbez@…> 8 years ago.

Change History

comment:1 Changed 8 years ago by micke prag <micke.prag@…>

How whould this be useful? The parameters for each protocol is very unique so there isn't possible to create a generic interface for configuration anyway.

comment:2 Changed 8 years ago by torbjörn lönnemark <tobbez@…>

Sure, they may be unique but they're still (at least at some level) understandable by humans. So even if the values for parameters for every protocol are wildly different, it could be of use to be able to present the user with a list of protocols, and then the available parameters for each of them.

For example, they may choose 'arctech' and be informed that the parameters are 'house' and 'unit', or choose 'group' and be informed that it has the parameter 'devices'. I believe this could add more usability in some contexts, even though the values required by every device differs a lot.

Maybe one could even incorporate some kind of description of parameters that could be retrieved as well (the content currently on  http://developer.telldus.se/wiki/TellStick_conf)? I'm not sure.

In addition, it could possibly be interesting to be able to enumerate supported models per protocol as well.

Of course all of this could be accomplished in the third party software by getting the info from the telldus-core sources, but that would create another dependency, and it would mean that that work would have to be done again everytime protocols/devices/parameters are added.

comment:3 Changed 8 years ago by micke prag <micke.prag@…>

  • Priority changed from major to minor
  • Version set to 2.1.1
  • Verified by Telldus set
  • Milestone set to 2.1.3

comment:4 Changed 8 years ago by micke prag <micke.prag@…>

  • Blocking 190 added

Changed 8 years ago by torbjörn lönnemark <tobbez@…>

Note: See TracTickets for help on using tickets.