That’s not going to be any good because the script is looking for it in your local directory. As I say, I’m a bit lost really, there must be a reason it’s looking specifically there but I don’t understand the architecture and structure so I’m fumbling blind really, just hoping that using generic Linux principles will get us through, but it’s not working quite so well after our initial success 
Well you have made a massive effort, for which I am very grateful.
In the end, it seems that I just keep ending up with the home assistant directory where it is not supposed to be
Worst case for me is that I guess I can just leave it open, or reload if my computer goes off. Hopefully it will still auto-discover any items, and I can at least see what is connected.
You’re welcome, anytime 
Yeah, I mean if it is was me now I’d be googling ways to run a command in the background on login on a mac, and then try to use one of those methods to set it going. Circumvent that install script basically. 
Marc
Seem to have it working now. Found another post which suggested the following:
cd ~/Library/
mkdir LaunchAgents
hass --script macOS install
It worked!
Once again, many thanks for putting up with a “Mike” and all of your efforts - to be honest, you got me most of the way there.
1 Like
Ace - glad you’re sorted
I’ll update the instructions when I get a sec to reflect the omissions we’ve discovered
Marc, if you are still willing to talk to me.
Back with another “Mike” issue
Trying to add an MQTT broker, and one of the steps seems to be to add to my configuration.yaml file
After looking at various sites, I am still unclear on how to actually open this file.
Sorry - we really are back to basics
Mike
Heh, no worries.
You seem to be looking at some ‘old’ guides re mqtt.
Presuming you set up a broker, say mosquitto, on your machine with a user called ‘homeassistant’ and a password of ‘mfsocialisamazing’, to get your homeassistant to talk to it just click configuration on the sidebar, then integrations, add, find mqtt in the list and click on it. Type your machine’s ip address, your username and password for the mqtt broker, tick the ‘use discovery’ box and click go (or save, or OK, or whatever the button says).
Job done
1 Like
Thanks again Marc
Unfortunately, as with everything I do on a computer, I have run into problems, which are probably blindingly obvious to most, but not those with a negative IT IQ
As far as I can tell, mosquitto is now installed. Text on the terminal is:
mosquitto version 1.6.8 starting
Config loaded from /usr/local/etc/mosquitto/mosquitto.conf.
Opening ipv6 listen socket on port 1883.
Opening ipv4 listen socket on port 1883.
Assuming this is correct, and no more steps are required (maybe a big assumption), if I then go to the home assistant front end and try to add as an integration, I need to enter the broker, port, username and password
I tried a broker name of brew or home-brew (where I downloaded the mosquitto broker) but it is unable to connect. I assume the username is my directory - michaelgross - which is the terminal prompt.
I was not asked to create a password during the mosquitto installation process, so do I create one now on the home assistant web page?
On various sites, there are reference to having to restart home assistant after changes - is this part of my problem? If I do need to restart, is the following command the most appropriate:
sudo systemctl restart home-assistant.service
Or do I simply log out on the web page and then log in again?
If it were not for travel restrictions, I think I would be better off just paying you to come to Hong Kong to do all this for me!
Marc, hold that thought. Looks like it has worked now - at least it now shows
MQTT:127.0.0.1
in the “configured” section of Integrations
Ha, I don’t think paying for travel halfway round the world is proportionate, but that said one can never have too many holidays 
Yeah, sounds like you are all set up. If you go in to developer tools and click on mqtt at the top there is a rudimentary debug area for mqtt.
In the bit at the bottom put a # and press start listening (# means everything), and then in the topics at the top type test/test and in the payload type isitworking
Press send, and you should see it appear below (in a formatted fashion) having been sent to, and subsequently read from the mqtt broker.
After this you should set up a test mqtt sensor, which you can affect the state of by sending messages in the developer tools panel
Maybe still a problem.
Pressed Publish (which I assume is the same as Send)
It comes back with:
Message 0 received on test/test at 7.43pm
Underneath it says (greyed out):
QoS 0 - Retain:false
Or does it just mean it is working - and I simply have nothing connected (which is the case)
Yeah that’s fine, that means the message has gone to the broker and homeassistant can read it back. The greyed out bits at the bottom are options we could have sent with the message to tell the broker to save the message, but we didn’t because we are just testing.
Magic
On to the next problem - sorry installation…
1 Like
Hi there (particularly Marc if you are still talking to me)
Have decided to start over with a Raspberry Pi. Waiting for delivery to get started.
I am planning to use Home Assistant in another country (where I have a small business). I was wondering how difficult it would be if I set up the system in my home country, and then try to move everything overseas, and then add the devices and potential automations.
Am I in for a world of pain? I possibly could set it up in the overseas country, but that would mean a very significant delay, as I am probably not able to travel there for a number of months, so would prefer not to do this - unless my first option is just stupid !
No, that’s easy enough. Set it up, and then you can either
-
set up the location it’s going to be during onboarding
-
set where you are, and then when you move the device change the location in Configuration > General
If you then set it up with addons that allow for remote access such as duckdns (or use the Nabu Casa cloud) and remote editing such as VSC then you can remotely administer the system from home.
Obviously you’ll need to be a little bit careful not to break anything if you don’t have access locally, but the risk is fairly minor if you work methodically, especially now ‘safe mode’ is available, as if you break something in the configuration it will still start.
Brilliant, thank you. So when I set the original network, duckdns etc, there are not a lot of other bits of code that I have to manually change when I move to the new overseas router - very good to know
Cheers again
Mike
Indeed, duckdns addon will automatically send the new ip to the duckdns service when you boot it in the new location.
So it will just be the physical ‘home’ location that needs to be updated (or set during onboarding), which can be done via the interface.
Then you can carry on as though it’s sat right next to you tbh.