Updated to Home Assistant 0.108.2 and modbus not work 
In 107 and earlier it was working OK. Please, fix.
1 Like
This made me laugh.
What FM ???
We never had oneā¦
Though my major problem now is : - I need to change āthisā I think I set it up following onboarding and I think it used to be āhereā
āNo, is not there, we moved it ! and youll now need to remember āthisā new/obscure locationā
Or āyes it used to be in yaml but really you need to use this widget insteadā
I appreciate this is a mammoth task and one of the problems is that there are many ways of doing the same thing, so there is no āone size fits allā solution
I appreciate that a lot of our new members have no wish to get their heads round yaml and more and more will move towards ui (as Taras said) . And that as a boring stick in the mud, I should pull my finger out and embrace the new interfaces.
Me dinosaur, how bout you ?
Hmmmm.!
I could say that mine doubled. ( from 1% to 2%) (924 entities, 192 automations, 313 sensors) what the hell are you running ?
Keep up the good work !! 
1 Like
Thanks for the tip. Same problem, and you fixed it 
Just in case someone is struggling to install home-assistant-frontend==20200407.2, I only could do that increasing swap size. My āserverā originally has only 512MB Mem + 246MB swap, which was not enough.
You know what? If everyone who has a problem rolls back instead of debugging and filing issues to github, how is anything ever going to get fixed?
2 Likes
I agree that debugging is needed but if they are rolling back and they confirm things go back to normal then that means the issue is more code related. Now if they rollback and the issue persists the user knows its something on their end. And i agree they should ALWAYS be filing issues when they encounter them, with the issue template filled out lol.
@nickrout Trueā¦but I have to say that its a little hard to debug when you are unable to load the logs in your UI mate? Rolling back has often been my only option both in the past and again right now.
cat $CONFIG/home-assistant.log
1 Like
Not sure what to do with that? I use a docker install on a QNAP NAS. I have looked in my config folder and found a text file named āhome-assistant.txtā Opened that in VS Code and thats the log. Never knew that cheers!
If/when I see some positive reports on modbus working in upcoming 0.108.x releases Iāll keep that in mind and try again.
Mine seem to be fine.
Like David, mine are also working as expected
Apparently the problem of input_booleans, and other āhelpersā, failing to be restored has been corrected by this PR and is included in the upcoming 0.108.3 release:
https://github.com/home-assistant/core/pull/33973
FWIW, I tested 0.108.0 of Home Assistant Core and experienced no issues with restoring the state of input_booleans and other āhelpersā.
Where is the config saved?
When I search through the files in my config directory, I only see references to it in .storage/config_entries and .storage/entity_registry. Both files change several times a day with what appears to be state information. Thatās not very helpful. I use version control for backup because it lets me make note of what I changed and why. Unfortunately, with configuration information mixed in with state info, Iām left with committing unrelated changes every time I need to back out a change that I decided I donāt like, or tell version control to ignore those files, and then I lose critical configuration info. And yeah, Iāve lost some configuration that way.
I like the UI for quickly learning how to configure something. And for components that only get configured once, itās great. But knowing where the config is stored, and being able to open it in a text editor and copy/paste then make a few changes is much better (for me) for components that need several similar instances. Thatās the second reason Iād like to know where the config is kept, and of the two files I mentioned above, Iāve no idea which might be considered definitive.
Additionally, Iāve occasionally made typos when setting up a component, and sometimes you canāt edit components; you have to delete and start over again. The ability to open a file in a text editor and fix the typo would be a third reason to have this info.
Obviously, if Iāve just missed it in the docs somewhere, a quick link to the relevant doc would be most appreciated.
2 Likes
I dont think there is official support for hue remotes yet. Its probably using the custom one.
Deleted. WeMo working againā¦
My Belkin Wemo still works fine.
1 Like
I updated to 0.108.4 (docker) and z-wave stopped working. Iām seeing a bunch of āOut of frame flow! (0x00). Sending NAK.ā errors in OZW Logs. I tried swapping usb ports for my zwave stick and still no luck.
Has anyone else had a similar issue?
I donāt think so.