Indigo Domotics

a few high level suggestions regarding plugin management and in particular "Manage Plugins..." dialog

• make Manage Plugins actions work from mac client.
• one-click install/upgrade.
• offer "upgrade-all" button.
• make clearer correspondence between Plugins menu color/symbols and indicators/actions in Manage Plugins... dialog. Currently, you can't identify unsupported (red) plugins within the dialog, for example.
• provide more data about the plugin in the database, possibly including:
  • # of devices that use the plugin
  • # of actions/triggers/schedules that use the plugin
  • date of last update
  • a quick way to see release notes.
• provide a "remove" action to remove cruft from the list.

longer term, i suggest Plugin Store and Manage Plugins possibly would be better if combined.

Thanks for the feedback, most of this is on our feature request list already.

Hi Jay

Plug ins can be an issues after power failures . I have been able write scripts to reload those that have this issue. I do a have a few plugins that are not going to be updated as your Indigo versions change. Amy way you can have way to uninstall old plug ins in manage plugins pull down menu list.

Regarding power failures , most of the time the reflector is not working till I do a full reboot. Can there be a menu item in the home page that shows status of reflector connection. It would nice to know if it is working before I leave my campus and rely on indigo touch.

Thanks for reading this Jay..

@landry -- this may not be exactly what you're looking for, but it's a light-weight alternative that you may find helpful. The following Python script creates a small menubar app that shows the status of the Indigo reflector connection. I've tested a few situations by dropping my server's Internet connection and it seems to be working as intended (tested on Indigo 2023.1). As always, no warranties. Installation instructions are in the script docstring. Clicking on the menu bar bug will present an option to Quit the app.

Code: Select all

#! /usr/bin/env python3.10
# -*- coding: utf-8 -*-

"""
Create a macOS menu bar bug that shows the status of the Indigo Reflector connection

Save this script to the Indigo Scripts folder at:
    /Library/Application Support/Perceptive Automation/Scripts/reflector.py

Install the `rumps` python library using the Terminal command:
    pip3.10 install rumps==0.4.0

Run the `reflector.py` file as an linked script using an Indigo method of choice. For
example, using a trigger:
    Type: "Indigo Server Startup"
    Condition: Always
    Actions: Server Actions > Script and File Actions > Execute Script > reflector.py

CAUTION: Do not run this script as an embedded script (because Indigo will kill it after
         10 seconds).
NOTE: This is designed to be run on the machine running the Indigo server. It will not
      interrogate the server from another machine/location.
"""

try:
    import sys
    import rumps
except ImportError:
    indigo.server.log(f"You must install the `rumps` library --> pip3.10 install rumps==0.4.0", isError=True)
    sys.exit()

BASE_URL = f"{indigo.server.getInstallFolderPath()}/Web Assets/images/controls/variables/"

class MyApp(rumps.App):

    def __init__(self):
        super().__init__(name="", title="Indigo", icon=None)

    @rumps.timer(60)  # cycle time in seconds
    def change_title(self, sender):

        if not indigo.server.getReflectorURL():
            self.icon = BASE_URL + "Red Green Dot.png"  # Offline
        else:
            self.icon = BASE_URL + "Red Green Dot+true.png"  # Online

if __name__ == "__main__":
    MyApp().run()


landry wrote:

most of the time the reflector is not working till I do a full reboot.

That's very odd - my prior neighborhood had pretty regular power outages (2+ times a month) and the reflector always came back. It can take a while depending on the retry cycle, but it should come back on its own. I wonder if your Mac is having an issue getting the network stack back up and stable after a power outage. In any event, we should attempt to figure out why that's happening so next time it happens report it with any error messages on the Reflector forum.