i cant see the media folder in FTP, anyone else have this issue?
just updated to 0.116.1 and all of my yeelights are now showing as Unavailable
@gambit2552 The same for me. All Yeelights are unavailable. I have tried to remove yeelight integration in configuration.yaml and install from UI and it does not work either. They appear in integrations but not in all entities of the developer tool. They cannot be used because they are not in home assistant. Please fix it asap in the next update
yeelight also down
Hmmm…yeah, sorting out my lovelace yaml seems to have solved the issue with vertical-stack
Big thanks!!
I see a similar problem after upgrade to 0.116
sqlalchemy.exc.IntegrityError: (MySQLdb._exceptions.IntegrityError) (1062, "Duplicate entry '19744628' for key 'PRIMARY'")
[SQL: INSERT INTO events (event_id, event_type, event_data, origin, time_fired, created, context_id, context_user_id, context_parent_id) VALUES (%s, %s, %s, %s, %s, %s, %s, %s, %s)]
[parameters: ((19744628, 'state_changed', '{}', 'LOCAL', datetime.datetime(2020, 10, 9, 2, 12, 28, 31937, tzinfo=<UTC>), datetime.datetime(2020, 10, 9, 2, 12, 28, 569438, tzinfo=<UTC>), 'e12aa7ba09d411eb9afed9eb6a285667', None, None), (19744599, 'state_changed', '{}', 'LOCAL', datetime.datetime(2020, 10, 9, 2, 12, 26, 569276, tzinfo=<UTC>), datetime.datetime(2020, 10, 9, 2, 12, 27, 197492, tzinfo=<UTC>), 'e04b79a609d411eb88ca951a8a542c20', None, None))]
(Background on this error at: http://sqlalche.me/e/13/gkpj)
I guess I have to roll back to 0.115.6
You could delete the database (.db2), it will build a new one
I believe this isn’t because type isnt a valid option for views. It’s because it actually is now a valid option for views:
It allows developers to create custom view layouts but, because horizontal-stack is not a view layout (it’s a card), it is giving that error.
Actually for me it does not work in Safari… but indeed I checked with Chrome and it there! Waiting for update then 
cache problem with safari??
Hi
I have a question about updating in automations because some automations where I specified brightness with a certain value stopped working for me. This happened when I switched from 115.6 on 116.0
What is meant here?
“State conditions with attribute specified: When testing against a non-string attribute value, you now need to specify the value in your configuration in the same type as it is in the attribute (instead of as a string).”
I thought the problem would resolve itself if I upgraded from 116.0 to 116.1, but instead I got a new problem. My Yeelight devices are no longer detected. 1S Color Bulbe and Meteorit… Unfortunately, I can’t provide log entries, because I did a restore back to 115.6.
Hi @aceindy and thanks for your reply.
I moved on to 0.116.1 and the problem seemed to have disappeared.
However, as I use SQLite there is no .db2 to delete (am I right?)
I’ve been holding off on that resource, because I’ve never really known what this does… what other arguments could we use, besides the ‘octave-cli’ mentioned in the documentation?
the source doesn’t list any options;
edit
I’ve tried it anyways 
not having a clue what this means:
It is a bug introduced in 0.116.1. A fix is already merged for 0.116.2.
CC: @Gav_in @guiguiabloc @TheBisk @mirekmal @tron @Msv1
Sorry for the hassle.
Nope, cleared the cache. And it was working fine with 0.116…
am completely misunderstanding the fact we should now be able to use entity_globs in our history, logbook and recorder configs?
using this:
entity_globs:
- sensor.*_power_daystart
- sensor.*_usage_daystart
- sensor.*_calibrated_temperature
- sensor.*_actueel
- sensor.*_state
- sensor.*_totaal
- sensor.calculated*
- sensor.l1*
- sensor.l2*
- sensor.l3*
- sensor.teller1*
- sensor.teller2*
- sensor.zp*
- sensor.solaredge_*
- sensor.speedtest*
in an included file in all 3, and all I see are flatliners since:
using this for recorder, used as main filter for the full system. Nothing included here will be recorded and pass to history and logbook:
db_url: !secret db_url
purge_keep_days: 5
include:
!include logged_entities.yaml
exclude:
event_types:
- service_removed
- service_executed
- platform_discovered
- homeassistant_start
- homeassistant_stop
- feedreader
- service_registered
- call_service
- component_loaded
- logbook_entry
- system_log_event
- automation_triggered
- script_started
- timer_out_of_sync
domains:
- alarm_control_panel
- alert
- automation
- binary_sensor
- camera
- climate
- counter
- cover
- device_tracker
- geo_location
- group
- input_boolean
- input_datetime
- input_number
- input_select
- input_text
- light
- media_player
- proximity
- remote
- scene
- script
- sensor
- sun
- switch
- timer
- updater
- variable
- weather
- zone
and only include the entities in the ‘logged_entities.yaml’ which is also the only include for my logbook.yaml and history.yaml.
Hey, when did this happen?
NICE, finally easy to change the IP