A Bug Report - Report problems you encounter while using the software such as significant changes to functionality, security vulnerabilities, crashes, data loss, application performance issues, or inconsistencies with the user interface.

Enhancement Request - add a new feature or enhance an existing feature such as missing functional capabilities, graphical improvements, or modifications to the user experience. Include a detailed explanation of what you are unable to accomplish and reasons why this enhancement would be beneficial.

But most importantly please include, detailed instructions on what steps caused the bug. I can not stress too strongly that a good bug report really needs to include the steps that will reproduce the issue. If I can reproduce the issue, I can isolate what is causing the issue, and resolve it faster...

2) Not sure if this is by design but I wanted to point out the following:I have created Monitored Device Group A & BIt appears that if I have added Device X to both groups only one group (A for example) will reflect any updates. Once again this isn't a work stoppage since I can conditionally account for devices in both groups. However, moving forward, if possible, it would be nice to have Device X monitored in both Groups A & B. Let me know if you need further clarification on this.

Hmmm... I understand, but I'm not sure that it's anything that I will be able to change soon. The one underlying assumption in Switchboard, is that the device is in a single Monitored group.

I'll be looking into the device numbering issue, Friday night... And I'll see if something might be able to be done with the multiple Monitored groups

Would this be an option? Creating a parent group to monitor child groups:Device Group ADevice Group BDevice Group C (Monitors changes in A&B)

I did create a test group and placed my two other groups in it and it did collect data when I triggered a physical device in either group A or B to include:DeviceID_Last_TriggeredDeviceName_Last_TriggeredLast_TriggeredLast_Updated

The key state that I would need monitored would be Devices_Triggered = true/false. So if any device in Device Group A or Device Group B were on, the variable would be true and if everything was off in the child groups then it would be false. The idea is as I add more 'zones' in my home I can just add the Group name for that zone to be monitored instead of having one massive group with every device.

Another issue is that I am unable to pass the name of a device to a variable.

For my action group I am using "insert device state into variable", and the device is "Doors" (the switchboard device group). I then attempt to assign DeviceName_LastTriggered into a variable I've created called lastDoorOpened. This is where things break: The plugin apparently does not pass a value. lastDoorOpened remains null.

Traceback (most recent call last): File "plugin.py", line 631, in deviceUpdated File "plugin.py", line 545, in trigger_zone File "plugin.py", line 562, in send_emails<type 'exceptions.KeyError'>: key com.schollnick.indigoplugin.switchboard not found in dict

Weird. I haven't seen this, but I'll look into this. I don't use the email feature that often.

Do you have a custom email defined? If so, try turning it off and see if that makes a difference. I just looked at the code, and really don't see any reason you should be receiving a crash from it. I'll have to try to duplicate the issue.

Another issue is that I am unable to pass the name of a device to a variable.

For my action group I am using "insert device state into variable", and the device is "Doors" (the switchboard device group). I then attempt to assign DeviceName_LastTriggered into a variable I've created called lastDoorOpened. This is where things break: The plugin apparently does not pass a value. lastDoorOpened remains null.

Switchboard hasn't been updated in quite a while, since there hasn't been much call for improvements.... Or at least I haven't thought of any, and feedback has been quite limited.

This very much maybe a feature added after it's release, and I haven't updated it to support it.

I'll dig around and see if I can track down where to support that.

Okay, I just glanced through the developers docs, and this is a feature that has to be enabled at the programmers level. I'll see if I can track down the email issue, and add the substitution code this weekend.

Hey Ben, you're awesome. I'll be sure to donate again. Just in terms of the work you're doing, the email stuff isn't so important to me since I can use the "notification" method in any action group to provide that functionality instead. Rather, passing the device info as part of the switchboard is going to be amazing. So if you have any time, that's the one to do.

@jay from indigo: consider taking note of this, indigo itself would really benefit from this being a core device rather than a plugin from ben

Hey Ben, you're awesome. I'll be sure to donate again. Just in terms of the work you're doing, the email stuff isn't so important to me since I can use the "notification" method in any action group to provide that functionality instead. Rather, passing the device info as part of the switchboard is going to be amazing. So if you have any time, that's the one to do.

@jay from indigo: consider taking note of this, indigo itself would really benefit from this being a core device rather than a plugin from ben

Drop me a line at Benjamin AT schollnick DOT net, and I'll send you a alpha/beta that I have added substitution to. I've been busy working on too many real world concerns (anyone looking for a Python programmer? Especially if you are willing to allow telecommuting?), so I haven't had a chance to really crank up with Indigo v6.1 updates....

I've been busy working on too many real world concerns (anyone looking for a Python programmer?)

I've been thinking about the same thing. Whether there were someone willing to be a benefactor to allow me to be able to work on this stuff full-time. There just don't seem to be enough hours in the day to do all the things I want to do (endless list, really) and the real-world job is just too time consuming!

Dave

I came here to drink milk and kick ass....and I've just finished my milk.