Thanks for your reply… I got it working by using a new (never used) user name and password but are still not able to get Duck DNS working.
I am having the same issue… Basically a stock installation of Hassio that I’m trying to configure. Here is what I noticed::
Yesterday, I couldn’t access via Firefox browser. Not sure why but Chrome works. Didn’t worry too much about it thinking that it was a fluke.
Tonight, I connected to http://hassio.local:8123 using Chrome, rebooted Hassio from the UI and now:
“This site can’t be reached
hassio.local refused to connect.”
I’ve tried 4 different browsers and multiple machines. I can ping the Pi’s IP with success AND I can see the SAMBA on my network.
The only thing I’m playing with in the config is setting up MQTT- and that is basic from the Hassio store.
any help is greatly appreciated. Spending too many hours on trying to get the configuration working.
Should also mention that I’ve tried a 2nd RPI 3B+ with same results.
Did you try connecting to http://[pi’s ip address]:8123
Did you install duckdns? If so you will need to navigate to https://…
Yes I tried to log in with the PI’s IP address as you suggest. I have not enabled DuckDns yet until I get the system up and working.
I should note, I can also ping the IP of the PI with success on my network…
Am I unique here? I always keep my computer up to date- and yesterday, I did a Java update for the VPN software I use for work…
I don’t think that would have an effect if you are only connecting locally.
Being able to ping the pi is a good sign.
Can you connect from another PC/tablet on the network? That would prove or disprove your theory.
Tried a different PC without success… I have NO idea what caused this.
Through Samba, I commented out the simple change I made to configuration.yaml. I was hoping that I’m not the only person experiencing this.
Hi,
Have you tried re-booting your router?
Are you hardwired or using WiFi?
Keith
Yes- I rebooted the router. I am using a hardwired connection.
The physical port on the router works- I validated that as well as the cable. Also tried swapping out the Pi…
Hi Pete,
I use Chrome exclusively with no issues.
I’m sure it’s not hardware. So you intermittently connect within your firewall?
Keith
Keith-
I’d say its a no connect to the UI at this point and yes this is within my firewall.
I can still reach the PI as I mentioned earlier- I copied the config.yaml out for b/u purposes for example.
Any help is greatly appreciated! I’d hate to start-over out of default… though my learning curve is much less at this point
Thanks,
Pete
If you can get your yaml file you wont have to start from scratch. Can you get the config/home-assistant.log file? Does that shed any light on what is happening?
I was unaware of the log file quite honestly. After investigating the log, it pointed me to an error in config.yaml
I honestly had an extra space in configuration.yaml that caused this.
Thank you all for your help! I’m getting close… and dangerous!
I have the same problem. I set up duck dns as well. everything was working fine and all of a sudden it stopped. (without me making any changes to the files…
How can I get into the config file? any idea please help…
Is SSH or SAMBA still working?
If not you can remove the SD card and read it on a PC. Config file on SD card
Would you post your configuration file so I can take a look.
Thanks for replying so quickly. You guys are great.
The device does show on my mac in the network section but unable to connect.
I set it up and had it running for hardly a week, and it stopped working without me changing a thing.
The trouble shooting I did was.
- Restart Pi3 multiple times
- Disconnect and connected back the LAN cable multiple times
- Checked if the IP of the Pi3 is same as what is assigned in the port forwarding and in DuckDNS. (I didnt change anything in the first place to cause the problem)
I did plugin the SD card into my Mac but was not able to read anything on the SD card so I left it. Looks like tom_I has suggested a way to do that. I will try it and let you guys know the content of the configuration file. If Hass IO is that unstable then I dont think its made for me
That software was for a windows PC not a Mac. I think you should be able to read it without the software if you are using a Mac.
Grab your config/home-assistant.log file as well.
Two other things that are important for stability:
- a 5V power supply capable of supplying 2.5A. A phone charger will probably not do.
- a good quality SD card.
My bad config is below. The issue is on line #88, I deleted the extra line after “expire after 10”
homeassistant:
Name of the location where Home Assistant is running
name: Home
Location required to calculate the time the sun rises and sets
latitude: 0
longitude: 0
Impacts weather/sunrise data (altitude above sea level in meters)
elevation: 0
metric for Metric, imperial for Imperial
unit_system: imperial
Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
time_zone: UTC
Customization file
customize: !include customize.yaml
Show links to resources in log and frontend
introduction:
Enables the frontend
frontend:
Enables configuration UI
config:
http:
Secrets are defined in the file secrets.yaml
api_password: xxxxxxxxx
Uncomment this if you are using SSL/TLS, running in Docker container, etc.
base_url: example.duckdns.org:8123
Checks for available updates
Note: This component will send some information about your system to
the developers to assist with development of Home Assistant.
For more information, please see:
https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
updater:
Optional, allows Home Assistant developers to focus on popular components.
include_used_components: true
Discover some devices automatically
discovery:
Allows you to issue voice commands from the frontend in enabled browsers
conversation:
Enables support for tracking state changes over time
history:
View all events in a logbook
logbook:
Enables a map showing the location of tracked devices
map:
Track the sun
sun:
Weather prediction
sensor:
- platform: yr
Text to speech
tts:
- platform: google
Cloud
cloud:
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
THIS IS FOR THE IOS APP TO WORK!!!
ios:
THIS IS FOR THE MQTT BROKER TO WORK!!!
mqtt:
discovery: true
discovery_prefix: homeassistant
broker: core-mosquitto
port: 1883
username: ‘peter’
password: ‘xxxxxxxxx’
sensor:
- platform: mqtt
name: “Doorbell”
state_topic: “doorbell”
expire_after: 10
switch:
- platform: mqtt
name: “Doorbell Chime”
state_topic: “state/doorbell”
command_topic: “doorbell/commands”
payload_on: “Audio Doorbell”
payload_off: “Silent Doorbell”
retain: true
You need to format your pasted code as per the blue banner at the top of the page.
Which line is line 88, and what was the error?