Help with understanding initial fields

Could some kind soul help me understand the fields that are needed? I find the documentation a bit vague on the matter and I'm having problems getting this working.
(For those that can't see the attachment, I'm asking about the URL, Access Token and Username Credentials.)

First question is - are you SURE you need to use this plugin? What are you doing with it?

1. Not auto-discovered. Default is "localhost:8123". If it's something else, it was picked up from a previous install. Needs the IP address or hostname of the HA server.
2. See #1. You need to GET this string from HA.
3. The MQTT port is standardized. You would only change this if you're running your MQTT broker on a non-standard port.
4. Whatever your username/password is for the MQTT Broker. If using the Indigo MQTT Broker plugin, these are blank.

Thanks Joe. Very much appreciate your reply. I'll try those pointers.

I'm finding MQTT to be a bit of a black box and it's a little difficult to know where to start. No doubt once I've used it for a while, I'll be amazed at my former naivety!

I repeat - are you SURE you need to use this plugin?

So, some progress...

I updated the fields (though unsure about the access token, there is a long entry there for that though). There seems to be some comms:

On Indigo I'm getting:

3 Nov 2023 at 14:43:00
HassBridge Connecting to the MQTT Server...
HassBridge Error Exception trapped: [Errno 8] nodename nor servname provided, or not known
HassBridge Error Error in plugin execution UiClosed1:
File "plugin.py", line 153, in closedPrefsConfigUi
File "plugin.py" ', line 133, in _update_perfs
File "plugin.py" , Line 230, in _connect_to_matt_broker
File "/Library/Application
File Library/Application Suport/Perceptive Automation/Indigo 2023. 1/wins/assBride. indigougin/Contents/Server plugin/bs/pao/at/client.py Line 987, in remotect
File "/Library/Application Support/Perceptive Automation/Indigo 2023.1/Plugins/HassBridge.indigoPlugin/Contents/Server Plugin/libs/paho/matt/client.py", line 3522, in _create_socket_connection
File "/Library/Frameworks/Python. framework/Versions/3.10/lib/python3.10/socket.py", line 824, in create_connection
File "/Library/Frameworks/Python. framework/Versions/3.10/lib/python3.10/socket.py", line 955, in getaddrinfo
type: [Errno 8] nodename nor servname provided, or not known

And on the MQTT log on HA, I get...

[14:38:19] INFO: Starting NGINX for authentication handling...
s6-rc: info: service legacy-services successfully started
[14:38:20] INFO: Starting mosquitto MQTT broker...
2023-11-03 14:38:20: Warning: Mosquitto should not be run as root/administrator.
2023-11-03 14:38:20: mosquitto version 2.0.17 starting
2023-11-03 14:38:20: Config loaded from /etc/mosquitto/mosquitto.conf.
2023-11-03 14:38:20: Loading plugin: /usr/share/mosquitto/go-auth.so
2023-11-03 14:38:20: ├── Username/password checking enabled.
2023-11-03 14:38:20: ├── TLS-PSK checking enabled.
2023-11-03 14:38:20: └── Extended authentication not enabled.
2023-11-03 14:38:20: Opening ipv4 listen socket on port 1883.
2023-11-03 14:38:20: Opening ipv6 listen socket on port 1883.
2023-11-03 14:38:20: Opening websockets listen socket on port 1884.
2023-11-03 14:38:20: mosquitto version 2.0.17 running
2023-11-03 14:38:20: New connection from 127.0.0.1:37220 on port 1883.
2023-11-03 14:38:20: Client <unknown> disconnected due to protocol error.
[14:38:21] INFO: Successfully send discovery information to Home Assistant.
[14:38:21] INFO: Successfully send service information to the Supervisor.
2023-11-03 14:39:23: New connection from 172.30.32.1:51445 on port 1883.
2023-11-03 14:39:23: New client connected from 172.30.32.1:51445 as 2zmbzglLXXirA4qvpkkgK2 (p2, c1, k60, u'homeassistant').
2023-11-03 14:42:01: New connection from 172.30.32.2:44106 on port 1883.
2023-11-03 14:42:01: Client <unknown> closed its connection.
2023-11-03 14:44:01: New connection from 172.30.32.2:59826 on port 1883.
2023-11-03 14:44:01: Client <unknown> closed its connection.
2023-11-03 14:46:01: New connection from 172.30.32.2:52006 on port 1883.
2023-11-03 14:46:01: Client <unknown> closed its connection.
2023-11-03 14:48:01: New connection from 172.30.32.2:53906 on port 1883.
2023-11-03 14:48:01: Client <unknown> closed its connection.

Seems to make connection but then close itself out? Anyone have any pointers for me?

I'm not going to provide any more feedback until you answer the question above.

I'm sorry Joe, I missed your important question! No, I'm not sure I need to use it!!

I wanted to play a bit with Home Assistant. I'm very happy with Indigo and control 20+ zwave devices and 60+ zigbee devices. I'm finding that the indigo reflector is often down so I thought I'd try controlling my zwave devices via HA. but setting up the zwave devices all over again in HA is a real pain. Thus I thought I'd try this plugin to open up zwave device control via HA through to Indigo. Open to be being persuaded otherwise!

Fix your reflector issue, don't try to use HA as an intermediary. As you can see, this is not a trivial plugin to configure, and you have to do the setup on the HA side too. The ONLY reason this plugin was updated to Python3 was for existing users who depended on it. I do NOT recommend anyone new to use this.

Home Assistant is useful to Indigo users because there are MANY integrations in HA that do not have equivalent Indigo plugins. If you NEED one of those integrations, fine. Use Home Assistant Agent to bring them into Indigo. I do not recommend using HA for anything else (in conjunction with Indigo).

I just looked at your post history, and don't see anything about reflector issues. Maybe you should start with a post here: viewforum.php?f=10

[jay (support)]

I'm finding that the indigo reflector is often down

Our hosted reflector server is rarely down (I think we've had two occurrences this year, both were resolved within hours). I just looked through all of your forum posts this year and found no reports of reflector issues. I also looked through our support email archives and we have never received an email from the email address associated with this forum account.

If you are having issues you need to post or otherwise contact us so we can help figure out what's going on. The vast majority of users have no systemic reflector issues.

FYI, I just checked your reflector and it's up right now.

Okay. Thanks Joe and Jay. I consider myself duly warned!

I'll hold off on playing around with the HA stuff for the moment and concentrate on the reflector issue.