After installing Indigo Widget 1.3.2 today in my preview build of MacOS X 10.8, Mountain Lion, I was unable to enter either the IP address of my local Indigo server, or my credentials, so I was unable to access Indigo.

The Indigo Widget is no longer supported - though the source is there in the widget itself so you might be able to figure out what's wrong.

We recommend using the web interface instead.

Also note: we generally don't support beta OS versions. Bug reports are certainly welcomed for those that are testing OS releases but just be aware that if there are any fatal issues you'll likely be stuck until we release a compatible version.

I've just installed MacOS X 10.8 (GM) on my iMac, and can confirm that the Indigo Widget 1.3.2 reports an error when attempting to connect to the home Indigo server running on the local network. I appreciate your saying that the widget is no longer supported, but the web interface is annoying when run from Dashboard, since it immediately switches out of Dashboard to Safari on the Desktop. The widget immediately worked conveniently from within Dashboard with no drama. I'm assuming there is some technical reason why this extremely convenient desktop Mac utility no longer works, and if the Indigo app itself weren't so excellent, I'd look for an alternative for controlling my home's INSTEON devices. As it is, I now basically use the iOS INSTEON app to control my stuff manually.

I also liked the look of the Indigo Widget. The web interface is functional, but pretty crude looking.

There are technical reasons why we're no longer supporting the widget but in practical terms it's mainly about demand. I can count on one hand the number of people that used it regularly (when we did support it) so it's not worth cost to maintain it.

As I said above, the source is completely accessible so maybe someone else would like to take a stab at getting it to work.

I'll accept that you don't want to assign any resources to fix this very useful widget, but unless it broke, I don't know how you'd know how many people were using it. I used it daily. It was convenient to use, dynamically updated on the spot, and looked good. As a long time Apple customer (and of Perceptive Automation as well), the user experience is important to me. That's why I use products that are a joy to use, vice just functional. The web interface to Indigo is ugly, not to put too fine a point on it.

Be that as it may, it's your product and company's brand. I'm just voicing my displeasure with your decision.

Thanks for replying...

Just upgraded to Mountain Lion also, and find out the widget doesn't work. I've read the posts here and I must say I'm disappointed that the widget will not be updated. I use it on a daily basis. I work from home and I'm at my computer most of the day. It really helps not having to fish my iPhone out of my pocket just to turn off/on lights etc. Having the widget on the dashboard is fast, convenient, and very helpful. I wish you'd reconsider fixing the widget.

I'm still a 4.X Indigo user and was considering upgrading to version 5. However, I've got to think about this a bit now that the widget is not working. Also, it seems that it's been almost 2 years since the iPhone app has been updated as well.....

Please understand we have very limited resources here and have to carefully prioritize what features we are working on. Everyone has their "must have" feature, and unfortunately they are all different. The Widget wasn't developed by either of us, it hasn't been updated in years (it never has supported anything besides dimmers/relays), and at this point it is a very low priority for us to bring it back up to speed. And consider all the different ways Indigo let's you control a light: Safari (or any browser) via our built-in WebServer, Indigo Touch (native iOS app), Mac Indigo client, AppleScript, python scripts, and interactive python shell.

We would much rather spend our time working on higher-priority requested features, like an Indigo Touch update, improvements to the Indigo Web UI, or improvements to the plugin architecture. I think the vast majority would agree that is more important than the Widget.

Lastly, as Jay said the Widget includes its own source (HTML/CSS/AppleScript). So if some enterprising individual wants to bring it back up to speed then they are more than welcome to do so.

To get around this problem i’ve created a control page with the functions I wanted on dashboard, opened it in Safari, then used the “Open in dashboard” option to make a dashboard widget of those functions… so far it’s been working great!

That is a great (and very flexible) solution. Thanks for suggesting it.

I preferred the widget because it stayed in the Dashboard, and refreshed there. I do have a Safari clip in Dashboard, but when you click on a function, it immediately leaves the Dashboard and switches to Safari, a process that takes several seconds, compared to immediate action and refresh within the widget.