Hue Lights discussion

[sandconformgorgecloud]

Yes, thanks about Z-Wave, I made a mistake about Insteon, was more considering Z-Wave. But it's too expansive. I'll consider it for finally but my heating system with Indigo but I'll keep my X10 for the moment. I worry a lot to buy something if it's not working a lot better than now. Anyway, thanks to say it again, that's true Indigo works with all of them and that's really cool!

[macshield]

It looks like you're not clicking the "Start/Finish" button before going to the Hue hub and pushing the center button on the hub. Clicking the "Start/Finish" button generates a "username". Pushing the center button on the hub pairs the hub with the "username". Clicking the "Start/Finish" button after pushing the hub center button confirms the registration. So, to be more specific:

1. Open the Hue Lights plugin configuration window.
2. Enter the hub IP address.
3. Click the "Start/Finish" button (don't do anything else after clicking that button).
4. Immediately go to the Hue Hub and push the center button.
5. Immediately return to the Indigo client which should still have the Configure Hue Lights window open.
6. Click the "Start/Finish" button. This should complete the pairing.
7. Click the "Save" button.

If you still have trouble, enable debugging, go through that entire process again, and paste in the entire debugging log from the point where you enabled it into your reply (preferably within the [ code ] and [/ code ] tags so it formats properly).[/quote]


Thanks for the help. After trying your instructions I kept getting the same error. I had the plugin working before but the Hue hub changed ip's on me and that is when all the trouble began. Instead of waisting your time in trying to help me I decided to reinstall indigo and the hue plugin from scratch. That seems to have fixed the problem. Plugin is now working correctly. Thank you for the help and this great plugin.

[nsheldon]

I'm glad you were able to get it working and that you're enjoying the plugin.

[ckeyes888]

Nathan, thanks for the info on the bulb status within Indigo., really helps a lot.

Carl

[nsheldon]

Glad it helped Carl.

[ckeyes888]

Having an issue since upgrading to b11 that whenever I make any change to the
Hue bulb settings, ramp, color etc. the Indigo client crashes.

Running 10.5.8

Anyone else seeing this?

Thanks,

Carl

[nsheldon]

Odd. Don't have a 10.5.x box to test it on. Oldest OS I have right now is 10.7. Are you seeing client crashes with other plugin configuration changes (Smartphone Radar, Find My iDevice, Airfoil, iTunes, etc)?

[ckeyes888]

So far just the Hue plugin crashes it. Doesn't crash too consistently though.
I was changing the ramp rate in a number of Actions when it started crashing.
If I just do one or two and go on to something else it doesn't crash.
Definitely an odd one.

No issues with it's functions at all.

Thanks,

Carl

[nsheldon]

Do you see anything unusual in the debug logs for Hue Lights?

[ckeyes888]

I changed a ramp rate on in one action and got it to crash.
Here's the log:


Hue Lights Debug Validating action config for type: setRGB, device: Torchiere Hue
Hue Lights Debug Values:
UiValuesDict : (dict)
blue : 20 (string)
brightness : 100 (string)
description : set hue bulb RGB levels to 70, 50, 20 with ramp rate 5.0 (string)
details0 : (string)
green : 50 (string)
hue : 230 (string)
intro1 : (string)
labelBlue : (string)
labelBrightness : (string)
labelGreen : (string)
labelHue : (string)
labelRate : (string)
labelRed : (string)
labelSaturation : (string)
rate : 2 (string)
red : 70 (string)
saturation : 100 (string)
Indigo Cocoa client disconnected
Indigo Cocoa client connected


Carl

[nsheldon]

Thanks for the debug info. I wasn't able to reproduce the crash using Indigo 6b11 (server and client) on Mac OS X 10.7.5. I do remember older versions (5 and maybe 6, not sure) of the Indigo client crashing every once in a while when making a plugin configuration change and clicking the Okay button in the trigger or action group dialog before the Edit Action Settings button turned back to gray. So, the actions I took in the past were roughly:

1. From Indigo Cocoa client either on the same or a remote machine connected to IndigoServer, open a trigger or action group and bring up a plugin action (it could be any plugin, but I suspect it happened more with plugins that do more complex validation). Click the "Edit Action Settings" button.
2. Make changes to the settings as needed and click the "Save" button in the action settings dialog.
3. Sometimes after clicking "Save" the "Edit Action Settings" button will still be highlighted in blue as if you'd clicked it but hadn't yet let go of the mouse button. If you then click the "OK" button in the Trigger or Action Group dialog before the "Edit Action Settings" button returns to the un-clicked gray color, the Indigo client would crash (ahem... "unexpectedly quit").

This would happen every once in a while but was rare enough that I couldn't be sure what was causing it and didn't have enough information to give to Perceptive Automation as a reproducible bug. I'm not even sure it still does it under 10.7.5. The "Edit Action Settings" button still occasionally hangs at the clicked blue color when making settings changes, but it's pretty rare for me and hasn't caused a client crash in a while. My gut feeling is that, after clicking the "Save" button in the settings dialog, IndigoServer is waiting for the plugin to return something from the validateActionConfig Python method (in the plugin code). Sometimes, if the plugin is busy gathering data from, say, the runConcurrentThread method, it may not immediately return from the validateActionConfig method and there's some kind of client-server synch issue going on where the client is still waiting for confirmation and either never receives it from the server or the server returned it sooner than the client was expecting. I've found that, when the "Edit Action Settings" button is still blue, clicking any blank gray space in the Trigger or Action Group dialog will "wake up" the client, setting the button back to gray, at which point clicking the "OK" button will not crash the client. It's an odd work-around, and I'm not sure it's something that can be addressed through plugin changes or Indigo changes. Since I've seen this in other plugins (including bundled plugins from PA), I suspect is's an intermittent bug that they either don't know about or haven't gotten to yet.

[ckeyes888]

Thanks a bunch! I think you've nailed it. If after the edit settings dialog is saved and you click
on OK while it's still gray, you will "exit unceremoniously" from your client.
As you suggested, if after your edit and the OK is grayed out you click on most anything but the OK button it will turn blue and not "exit" when clicked.

It's very reproducible for me.

Thanks,

Carl

[jay (support)]

Carl, please zip up this entire folder and mail it to indigo DASH support AT perceptiveautomation DOT com:

/Library/Application Support/Perceptive Automation/Indigo 6/

Note, that's the Library folder at the top level of your hard drive, not the one in your user folder. It's probably going to be pretty big. If you have issues mailing it, send me an email to the above address and we'll work something else out.

[nsheldon]

Though I have nothing to support it, I'm wondering if the ability to reproduce this might be related to system performance. I used to see this crash more often with my old Core 2 Duo Mac mini running 10.7.5 and Indigo 5 and 6 (early beta). After upgrading the Mac mini to a much newer 2.6 GHz i7 with SSD, I don't remember encountering this many times, if at all (though the new mini is running 10.8.4 with the latest Indigo 6, so that may also factor in). Just a thought.

[jay (support)]

My production server is running on a very old Core Duo (original Macbook Pro) running 10.6 and I can't reproduce it there either. I'm wondering if you guys have some common system extension that's somehow jumping into the Cocoa frameworks somewhere and causing it. If I can't reproduce it with Carl's folder then I may get you both to run a system information report and see if I can find any common 3rd party things that might be doing it.