Indigo Domotics

I am not sure how feasible it might be, however when you open a device to edit it would be really handy to have indigo pull all the available device parameters into one place with descriptions and check boxes or entry fields so one does not have to know the index number.

Radjin~

depending on the device that depends on the author of the device. some are pre-defined by Matt/Jay other are defined by people that develop plugins.

In the DEVICE / EDIT screen you see everything that the device /plugin programmer has made available to be edited. There is likely some logic behind the screen Ie which fields to show if you select model a vs model b.. etc.


if you type into an action script menu (you find that under in action/ server/ scripts
indigo.server.log(unicode(indigo.devices["theDevicenameHere"])) ( keep the " )
you will see all info stored by indigo about the device like this:

Code: Select all

batteryLevel : None
buttonGroupCount : 0
configured : True
description : cookieName=orange
deviceTypeId : MotherCookie
displayStateId : statusDisplay
displayStateImageSel : None
displayStateValRaw : 72.3°F
displayStateValUi : 72.3°F
enabled : True
energyAccumBaseTime : None
energyAccumTimeDelta : None
energyAccumTotal : None
energyCurLevel : None
errorState :
folderId : 913782042
globalProps : MetaProps : (dict)
     com.karlwachs.mother : (dict)
          BatteryIgnore : TRUE (string)
          BatteryQueryWait : 600 (string)
          MotionIgnore : FALSE (string)
          MotionQueryWait : 900 (integer)
          PresenceIgnore : FALSE (string)
          PresenceQueryWait : 4 (integer)
          PresenceQueryWait1 : 120 (string)
          TemperatureIgnore : FALSE (string)
          TemperatureQueryWait : 240 (string)
          address : mTEa9t2G1yu6Q9MeYTNTBzZINW5Qt3A4 (string)
          displayField : Temperature (string)
          pullPush : false (bool)
id : 1135721941
lastChanged : 2015-05-18 19:36:30
model : Cookie
name : orange
pluginId : com.karlwachs.mother
pluginProps : emptyDict : (dict)
protocol : Plugin
remoteDisplay : True
states : States : (dict)
     Battery_LastEventDate : 2015-05-03 14:21:07 (string)
     Battery_LastStatusChange : 2015-05-03 14:21:07 (string)
     Battery_ignore : true (string)
     Battery_level : 2964 (string)
     Motion_LastEventDate : 2015-05-03 00:19:12 (string)
     Motion_LastStatusChange : 2015-05-03 00:19:12 (string)
     Motion_data_0 : 0 (string)
     Motion_data_1 : 52 (string)
     Motion_data_2 : 300 (string)
     Motion_data_3 : 30 (string)
     Motion_ignore : false (string)
     Motion_profile : WalkStandard (string)
     Motion_queryWait : 900 (string)
     Motion_string : {u'durationSeconds': 300, u'durationWalkSeconds': 30, u'numberSteps': 52} (string)
     Presence : 2 (string)
     Presence_LastEventDate : 2015-05-05 14:46:39 (string)
     Presence_LastStatusChange : 2015-05-05 13:37:24 (string)
     Presence_ignore : false (string)
     Presence_queryWait : 4 (string)
     Presence_string : {u'body': u'Present', u'code': 200} (string)
     Signal : -61 (string)
     Temperature : 72.32 (string)
     Temperature_LastEventDate : 2015-05-18 19:33:42 (string)
     Temperature_LastStatusChange : 2015-05-18 19:33:42 (string)
     Temperature_ignore : false (string)
     Temperature_ui : 72.3°F (string)
     statusDisplay : 72.3°F (string)
subModel :
supportsAllLightsOnOff : False
supportsAllOff : False
supportsStatusRequest : False
version : 0

Karl

ps there is also the menu option but that is similar to the device edit, just a different form factor for smaller changes.

That's a lot of information. Perhaps I should refine my post thus:

It would be very handy if Indigo aggregated all editable parameters for a particular device and added check boxes or drop-downs to choose valid entries without resorting to scripting or researching index codes.


I didn't mean to have a complete data sheet for the device although I can see how that would be useful. I was referring to editable parameters only.

Radjin~

It would be very handy if Indigo aggregated all editable parameters for a particular device and added check boxes or drop-downs to choose valid entries without resorting to scripting or researching index codes.

If I am understanding what you are asking, that isn't all that practical -- there are many more plugin device types than built-in device types and each plugin defines its own editing screen for devices and the plugin configuration itself. There is usually a reason that a plugin developer does not expose certain properties for editing -- either they are generated/configured from others, read from a configuration file, pulled from the hardware/service itself, etc. This would be plugin specific and thus Indigo provides the tools for the plugin developers to expose what they wish / are able to expose. Allowing users to edit any property would make debugging a MASSIVE headache and, frankly, would discourage further plugin development.

Your best bet would be to inquire with the developer (Indigo Domotics or plugin developer) if there are additional items that you would like to see exposed for modification.

Adam

I am talking about hardware devices not plugins. Examples: LED state, dimming speed, time to return to off in a multi-sensor for motion.

Radjin~

Added to feature request wish list.

+ 1