Back home and my HA is still up and running, but Remote UI still not working for me. When I go to the configuration setting it’s currently showing
Remote access is being prepared. We will notify you when it's ready.
Anyone got any ideas how to get this working again?
You have to wait for a few minutes while the config (SSL certificate etc) are being prepared.
Cheers. It was working at the start of the day though (I should have reiterated that in my new post rather than just replying to my first one). Then it just stopped working earlier today and never came back (many hours).
I’ve just looked in my log file and there were loads of errors relating to the Upnp component, making it very hard to spot any other issues. I’ve disabled that and restarted HA. My remote access immediately started working again!
Despite I am one of active contributor, I usually upgrade my production system bi-monthly, unless there is an important update related the component I am using. Of course I have many testing configuration for development purpose.
It worked earlier in the day for me, but now I just get “data loading” and nothing.
Yes I know, but what im saying, is the ENTITY for my AURORA light, changed FROM aurora TO nanoleaf
Made a minor update for a breaking change, and updated to 90.1 with no issues. Nice work devs.
Is this error related to the MQTT changes:
No matching payload found for entity: Door Sensor 2 RF_Bridge with state_topic: tele/sonoff/RESULT
My binary_sensor looks like this:
- platform: mqtt
state_topic: "tele/sonoff/RESULT"
name: 'Door Sensor 2 RF_Bridge'
value_template: "{{value_json.RfReceived.Data}}"
payload_on: '34A90A'
payload_off: '34A90E'
device_class: door
qos: 1I for one really appreciate the releases every 2 weeks, because they always bring some awesome feature or other…
I wonder what will happen when HA reaches 1.0, though. No idea if this is being planned, but given that currently the betas are more like alphas and the .0 releases are more like betas, maybe something could be done like Ubuntu, whereas some versions are more like “LTS” releases.
For example, the versions right before truly major changes (like the Lovelace default or the User support one). Of course, there’s nothing stopping someone from just staying on that particular version, but maybe it might help if it could come with not just a .1 or .2 bugfix release, but go all the way to .5 or .6 like a couple of versions did and thus have it be more “solid” for those staying behind.
I think someone said recently that releases will just be incremental and not necessarily reach version 1.0. Eventually, 0.90, for example, might just be release 90 or something like that.
After 0.99 the next number from a versioning perspective is 0.100.
Are you implying that 1.0 will never come then since there will always be a 0,100000000…
eventually
In the state of the Union balloob stated (repeated in a recent podcast) that 1.0 will come when it is possible to fully configure a system via the GUI (not all features and options but a minimally working system) - without any YAML work (always will remain an option though). It does not follow that the release after 0.99 will be 1.0. Balloob also said he believes we are very close to this now.
From what I’m seeing, the new time of flight sensor requires a direct i2c connection to the device running HA, is that correct? Is there an way to make it work remotely?
If version 1.00 comes after 0.99, then the “1.” has no meaning, it’s just another number like any other. Instead, software often uses some form of Semantic Versioning. So no one knows what number 1.0 comes after. 1.0 will come when the requirements for 1.0 (as defined by Paulus and friends) are complete.
Attach it to an esp device, espurna supports it. https://github.com/xoseperez/espurna
It could be a good thing to suggest to OttoWinter to include in esphome.
Upgrading from 89.2 seemed to work fine but then all of my zigbee devices ended up losing connectivity after a day or two. ZHA has been incredibly solid for me up to this point. Anyone have any ideas or tips that I may have missed in the notes on anything that needs to be done after upgrade?
It’s an old change in HA, people are still waiting for that PR to be rolled back… without a hope :\
You don’t HAVE to update every time there is a release. If what you have works, then just leave it alone. Come back in 6 months or so and spend a weekend updating to whatever is current then.
HA is great in that new features that allow me to do more and more with home automation are being added at a rapid pace. This rapid pace is allowing them to get out of the “enthusiast” mode and into more user friendly mode.
And they already have a published release cycle: It’s every two weeks on Wednesdays. You should never be “surprised”