For no particular reason I stupidly upgraded my perfectly stable 2025.1 to 2025.2 - I should have known better.
I can't access Indigo via Touch on any of my ios devices. No servers are under Bonjour, added IP manually and get "Could not connect to the server" connection failed.
I tried the reflector address in safari "reflector is down"
My entire house is run off of ios devices so I cant control anything anymore.
I don't think I can go back to 2025.1 because one of my most vital plugins (Pioneer), which i updated, requires 2025.2
The desktop client on the Indigo Server works fine
The desktop client on another mac connects and works fine
There are zwave errors and errors on another plugin (Cynical Weather) which I will address in another post
HELP!
2025.2 Didn't Go Well
- jay (support)
- Site Admin
- Posts: 19202
- Joined: Wed Mar 19, 2008 11:52 am
- Location: Austin, Texas
- Contact:
Re: 2025.2 Didn't Go Well
First - shut down the Indigo 2025.2 server and client, then you can restart Indigo 2025.1 and you should be back to normal - we don't upgrade in-place, so that install should continue to work.
To diagnose what's going on with 2025.2, let us know what errors you see when you restart the Indigo 2025.2 server. From the sound of it, it may be that some macOS permissions (local network likely) in the System Preferences -> Privacy & Security section are blocking network access.
To diagnose what's going on with 2025.2, let us know what errors you see when you restart the Indigo 2025.2 server. From the sound of it, it may be that some macOS permissions (local network likely) in the System Preferences -> Privacy & Security section are blocking network access.
Re: 2025.2 Didn't Go Well
When I launch the 2025.1 app on the mac server it warns me that it's not compatible but lets me proceed to the "start local server" and "connect to remote server" dialog
Is it ok to start local server with that warning?
Is it ok to start local server with that warning?
- jay (support)
- Site Admin
- Posts: 19202
- Joined: Wed Mar 19, 2008 11:52 am
- Location: Austin, Texas
- Contact:
Re: 2025.2 Didn't Go Well
I need to see that dialog or the exact wording, but if you see the start local server dialog then yeah.
- jay (support)
- Site Admin
- Posts: 19202
- Joined: Wed Mar 19, 2008 11:52 am
- Location: Austin, Texas
- Contact:
Re: 2025.2 Didn't Go Well
BTW, the Cynical plugins had a bug that broke them when we upgraded to Python 3.13 in Indigo 2025.2. I believe he's fixed that bug.
Re: 2025.2 Didn't Go Well
At first glance I seem to have regained access to the server via Touch for now on 2025.1
There is something in 2025.2 keeping me from accessing the server from my ios devices via Touch or ipad Safari or reflector. What an awful waste of 6 hours, I will revisit this post tomorrow, I've had enough for today.
The only thing that prompted me to do this was to get my plugins up to date and Indigo to the latest version.
Jay, if you have a list of specific questions let me know so I can be ready tomorrow.
Thanks
There is something in 2025.2 keeping me from accessing the server from my ios devices via Touch or ipad Safari or reflector. What an awful waste of 6 hours, I will revisit this post tomorrow, I've had enough for today.
The only thing that prompted me to do this was to get my plugins up to date and Indigo to the latest version.
Jay, if you have a list of specific questions let me know so I can be ready tomorrow.
Thanks
Re: 2025.2 Didn't Go Well
OVERVIEWjay (support) wrote: ↑Sat Aug 08, 2026 6:22 pm First - shut down the Indigo 2025.2 server and client, then you can restart Indigo 2025.1 and you should be back to normal - we don't upgrade in-place, so that install should continue to work.
To diagnose what's going on with 2025.2, let us know what errors you see when you restart the Indigo 2025.2 server. From the sound of it, it may be that some macOS permissions (local network likely) in the System Preferences -> Privacy & Security section are blocking network access.
Indigo Server = MacOS 10.14.6 (static IP)
Indigo 2025.1
RECENT CHANGES
New router (2 weeks ago)
Everything normal w/ new router
New router IPs are different (192.168.254.xx instead of 192.168.1.xx)
WHAT MY GOAL WAS
Update Indigo 2025.1 > 2025.2 now that the Pioneer Plugin supports .2
Update these plugins
• Adapters
• Cynical Cache
• Cynical Weather (many errors in log, will post in Cynical Forum)
• Pioneer Receiver
• Home Assistant Agent (didn’t update, awaiting test release to become public release)
*** one of these updates notified that "CLANG" was needed and I installed
*** is Indigo supposed to notify us some way (text/email/popup) when plugins need updating?
*** Why is it whenever we do an Indigo update the client GUI resizes and reorders all the columns? Is there a way save the previous layout so we don’t have to start over?
WHAT WAS WRONG AFTER 2025.2
• No iOS device using TOUCH was able to connect to the Indigo server
• Safari was not able to connect using the web address (or Chrome)
• The Reflector URL = error "server down" or something to that effect.
• 3 Z-Wave shades offline, client requested DEFINE & SYNC (back online)
• I always remember in the past Touch would discover & connect via Bonjour, I haven’t seen that in a really long time. I was using a manual IP address in 2025.1 without issue, but 2025.2 wouldn’t accept anything I entered and even locked up to where the DONE button didn’t work. I had to quit the app after each failed attempt.
*** I don’t know if this is related, but I almost never access Indigo away from home. About a month ago I needed to check Indigo and couldn’t. I believe it was "reflector server is down" I have a feeling that my reflector has never worked, I just didn’t know.
WHAT WAS CORRECT AFTER 2025.2
• 2025.2 Client on Indigo server Mac was normal (via screen share)
• 2025.2 Client on remote Mac connected fine at IP address
BACK TO 2025.1
When I quit 2025.2 and launched 2025.1 there was an immediate warning that 2025.1 was not compatible. I don't remember the exact wording, I acknowledged and the familiar popup appeared asking "start local server" or "connect to remote server" dialog. Chose "start local server", used the servers IP and everything was working back the way it was in 2025.1
Jay, what would you like me to test?