text:
Conflicting bindings

There are two elements with the same keybindings:
modules/editor/evil/config.el has
(map! :textobj "c" #'evilnc-inner-comment #'evilnc-outer-commenter)
and .local/straight/repos/evil-tex/evil-tex.el has
(define-key outer-map "c" 'evil-tex-a-command) and similar to inner.
So when working in TeX files, which one will be active is random. Sometimes visual-inner-c selects inside commands and sometimes inside comments (it is the same for the whole session, which one will be bound is defined when the buffer loads, but non-deterministically, so sometimes I get one and sometimes the other).
Since the tex one comes from a plugin, I would recommend changing the module one (comment) to capital c.
System information:

```
SYSTEM  type       darwin
	config     x86_64-apple-darwin18.7.0
	shell      /usr/local/bin/fish
	uname      Darwin 19.6.0 Darwin Kernel Version 19.6.0: Thu Oct 29 22:56:45 PDT 2020; root:xnu-6153.141.2.2~1/RELEASE_X86_64 x86_64
	path       (/usr/local/opt/openjdk/bin ~/.gem/ruby/2.6.0/bin ~/.npm-global/bin ~/.emacs.d/bin /usr/local/opt/qt/bin ~/.gocode/bin ~/Documents/MATLAB/mosek/tools/platform/osx64x86/bin ~/.cargo/bin ~/bin/flutter/bin ~/.config/yarn/global/node_modules/.bin ~/Library/Android/sdk/tools ~/Library/Android/sdk/platform-tools ~/bin/netbunch ~/bin /Library/TeX/texbin /Library/Frameworks/Mono.framework/Versions/Current/Commands /Applications/VMware Fusion.app/Contents/Public /Library/Apple/usr/bin /opt/X11/bin /usr/local/bin /usr/bin /usr/local/sbin /usr/sbin /sbin /bin /Applications/Emacs.app/Contents/MacOS/libexec /Applications/Emacs.app/Contents/MacOS/bin)
EMACS   dir        ~/.emacs.d/
	version    27.1
	build      Aug 16, 2020
	buildopts  --with-mac --enable-mac-app=/Users/travis/build/railwaycat/homebrew-emacsmacport/build-scripts/emacs-source/tmproot --prefix=/Users/travis/build/railwaycat/homebrew-emacsmacport/build-scripts/emacs-source/tmproot --enable-mac-self-contained --with-modules
	features   NOTIFY KQUEUE ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS MODULES THREADS JSON PDUMPER LCMS2 GMP
	traits     (batch server-running envvar-file)
DOOM    dir        ~/.doom.d/
	version    2.0.9
	build      HEAD -> develop f7293fb67 2020-11-11 20:33:27 -0500
	elc-files  0
	modules    (:completion company (ivy +icons +prescient) :ui doom doom-dashboard doom-quit fill-column hl-todo modeline neotree ophints (popup +defaults) tabs treemacs unicode vc-gutter vi-tilde-fringe window-select workspaces :editor (evil +everywhere) file-templates fold (format +onsave) multiple-cursors snippets word-wrap :emacs (dired +icons) electric (ibuffer +icons) undo vc :checkers syntax grammar :tools ein (eval +overlay) gist lookup lsp magit make pdf rgb tmux :os macos :lang (cc +lsp) (clojure +lsp) common-lisp (csharp +lsp +unity) data (dart +flutter +lsp) (elixir +lsp) (elm +lsp) emacs-lisp (erlang +lsp) (fsharp +lsp) (go +lsp) (haskell +dante +lsp) (json +lsp) (java +meghanada) (javascript +lsp) (julia +lsp) (kotlin +lsp) (latex +lsp +latexmk) (lua +lsp +moonscript) (markdown +grip) nim nix ocaml (org +dragndrop +journal +hugo +pretty) (python +lsp +cython +pyright) qt (ruby +lsp +rails) (rust +lsp) (scala +lsp) (sh +fish +lsp) (swift +lsp) web (yaml +lsp) :app calendar :config (default +bindings +smartparens))
	packages   ((tide) (vue-mode) (zig-mode) (alert) (lsp-julia :recipe (:host github :repo non-jedi/lsp-julia)) (julia-formatter :recipe (:host github :repo ki-chi/julia-formatter :files (julia-formatter.el scripts/server.el))))
	unpin      (n/a)
	elpa       (n/a)
```

Their code is already bound to mode keymaps. This has been bothering me for some time, but being random it is quite hard to pin down what is triggering it. I'll keep an eye open and see if I can find any pattern or anything that may help. You can close the issue if you want, I'll reopen it or fill a new one if I find out what is wrong.


text:
Sub-Header

Article Pages:
Mobile

Desktop

Search Results Page:
Mobile:

Desktop:

Originally posted by @amol-anand in https://github.com/hlxsites/accenture-newsroom/issues/2#issuecomment-1671255194

closing because duplicate

source: gharchive/issue

repo: hlxsites/accenture-newsroom

license_type: permissive

license_source: github-api


text:
Family Pack

https://main--bitdefender--hlxsites.hlx.live/solutions/family-pack#overview
In the section Compare Bitdefender Products, the TS button redirects to the cart, instead of PP as IS.

authoring issues. Added the correct link to TS button.

repo: hlxsites/bitdefender


text:
Firefox issue

When in Firefox, the nav fails to display.

It seems that the CSS pseudo-class has is not supported in FF: https://caniuse.com/css-has

repo: hlxsites/mammotome


text:
Missing wave

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #420
Test URLs:

Before: https://main--moleculardevices--hlxsites.hlx.page/en/assets/tutorials-videos/br/automated-plate-loading
After: https://missing-wave--moleculardevices--hlxsites.hlx.page/en/assets/tutorials-videos/br/automated-plate-loading
AND
Before: https://main--moleculardevices--hlxsites.hlx.page/en/assets/tutorials-videos/br/how-to-set-up-elisa-assay-and-basic-analysis-using-softmax-pro
After: https://missing-wave--moleculardevices--hlxsites.hlx.page/en/assets/tutorials-videos/br/how-to-set-up-elisa-assay-and-basic-analysis-using-softmax-pro
AND
Before: https://main--moleculardevices--hlxsites.hlx.page/resources/citations/axon
After: https://missing-wave--moleculardevices--hlxsites.hlx.page/resources/citations/axon

Note: I added also 2 additional styles for videos-and-webinars theme to make sure there is some space between hero and some space to wave

source: gharchive/pull-request

repo: hlxsites/moleculardevices


text:
Validate NOT and OR syntax on Definition store to allow user to import definition file

https://tools.hmcts.net/jira/browse/RDM-4635
Include validation in definition store to allow definition (excel) file with NOT and OR show condition syntax
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ X] No

Added tests.

repo: hmcts/ccd-definition-store-api

license: MIT


text:
CIV-12777 Part Admit Claimant Dashboard

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-12777
Change description
Added:

Handler for claimant response (claimant)
Script for Part admit Accepted claimant response
Method to return ordinal formatted date
Unit and integration test

Modified:

I have extracted the utils ClaimantResponseUtils.java
from civil/service/docmosis/utils to civil/utils because it is generally used. Consequently some imports have been modified

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ x ] No

Open for review before the end of the sprint

Open to get reviews

repo: hmcts/civil-service


text:
Updating Postgres checks, attempting to use pipeline variables to send messages to threads with each loops in pipeline

Change description
Updating Postgres checks
Attempting to use pipeline variables to send messages to threads with each loops in pipeline.
The first loop sets the header, subsequent loops should send to the thread of the same header

example thread:

repo: hmcts/dtspo-daily-monitoring


text:
[ALS-7200]

Switch to async upload
Allows for 5G+ uploads to S3

async not needed.

repo: hms-dbmi/pic-sure-services


text:
Update scala3-library to 3.2.1

Updates org.scala-lang:scala3-library from 3.2.0 to 3.2.1.
GitHub Release Notes - Version Diff - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala3-library" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-lang", artifactId = "scala3-library" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:n:2

Superseded by #56.

repo: hnaderi/lepus


text:
Intern Selection Process

We should start with the grouping so we can know who and who are working together

Please what's supposed to go on here?

What I would mention here is that the leaders of the group should give room for at least 50% newbies to learn from the experienced.

hi, what is the selection process?, what anbout mobile development beginners?, or any beginner?

There should be a mode for selection

Check the slack channel the selection process is already stated there

Really?

authors: Idadelveloper Idss15 Oluwatobiloba98 Technelly adekniyi dnor-dev


text:
Squeeze page

Contributions
Description
Developed the API endpoint for the Squeeze Page to handle POST requests, collect user information, and send an email template to the user.
Endpoints

Created Endpoint: POST /api/v1/squeeze

Type of Change

[x] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Implementation Details

Created Endpoint: Implemented the POST /api/v1/squeeze endpoint to handle form submissions.
Data Validation: Added validation for incoming data to ensure required fields are provided and the email format is correct.
Response Handling: Implemented appropriate responses for both success and error scenarios:

Success Response:{
  "message": "Your request has been received. You will get a template shortly."
}

Error Response:{
  "message": "Failed to submit your request",
  "status_code": 400
}

Database Storage: Saved user information securely in the database.

Testing

Unit Tests: Written unit tests for backend validation and data handling.
Testing Scenarios: Tested various scenarios for form submissions including successful, invalid data, and server errors.

Challenges and Issues

Database Table Issue:

Problem: The database table provided by the DB maintainers lacked an email field when I forked and cloned the repo.
Solution: Updated the table and migrations on my separate branch to include the necessary email field.
Note: This issue should be addressed and noted during testing.

Email Template Sending Bottleneck:

Problem: The task required sending email templates to the user's email address, but emails could not be sent immediately after the POST request. This necessitated asynchronous processing.
Solution: Utilized Laravel's job queue system to handle email sending asynchronously. However, the existing jobs table in the database was already configured for different purposes, such as job type, job name, and organization details.
Issue: The email functionality does not work due to the jobs table configuration conflicting with the intended use for email queue processing.

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

You have merge conflicts and it doesn't link to your issue

You have merge conflicts and it doesn't link to your issue

I did not even touch that, maybe it's because i did not pull before pushing
I worked on my create branch all through

authors: NgBlaze Ruthiejayjay


text:
Admin UI sometimes won't save Scenario step edits

Not really sure how to reporduce at this time, the behavior seems to be that after some time of using the UI to edit scenario steps, it stops saving them. The green confirmation message won't show up after you click save and when you go back to the scenario later the changes are missing

How long of time are we talking? The JWT token expires after a day.
Check the response to the PUT requests in the network tab of your browser; like so:

in the span of 10s of minutes, definitely not a day

Its also intermittent, some moments later the save action will work again

I haven't been able to reproduce this behavior. Can you post some more details about which versions of gargantua and admin-ui you're using and the environment in which you installed the app? Also post the HTTP response to a failed request and/or the corresponding logs when the edit fails to save.

after further debugging, I suspect it might be because of latin charset in my scenario steps...specifically curly quotes vs straight. The error messages can be seen on the JS console, but the UI doesn't report the error, just silently fails.

Closing in favor of #25

authors: ebauman hall wjimenez5271

repo: hobbyfarm/admin-ui


text:
Add log and env_log packages, resolves #20

Description
This PR introduces the log and env_logger packages to handle logging for the source code. These packages adds several useful macros such as info!, debug!, err! etc which can be used for logging of different kinds. To view the logs one must run test or the main program with the RUST_LOG flag set to the appropriate level, for instance RUST_LOG=gemini=info cargo run.
Alternate Designs
N/A
Benefits
Allows logging for debug etc without disturbing the user.
Possible Drawbacks
N/A
Applicable Issues
#20

Codecov Report

Merging #21 into master will decrease coverage by 3.08%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
- Coverage   98.87%   95.78%   -3.09%
==========================================
  Files           3        3
  Lines          89       95       +6
==========================================
+ Hits           88       91       +3
- Misses          1        4       +3

Impacted Files
Coverage Δ

src/main.rs
100% <ø> (ø)
:arrow_up:

src/resources.rs
100% <100%> (ø)
:arrow_up:

src/generators/names.rs
94.66% <40%> (-3.91%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 29f1ec8...14af326. Read the comment docs.

authors: codecov-io holmgr

repo: holmgr/gemini

license: mit

license_source: bigquery


text:
HoloViz Roadmap 2023

This issue is meant to be commented by the HoloViz contributors, maintainers and steering committee members.
In order to define the HoloViz roadmap for the next 6-12 months we would like to collect what would be your personal roadmap, i.e. what you think should be the most important goals for HoloViz and what you would like to work on?
Please insert only 1 comment (edit it later if you need to) before the 3rd of July 2023.

No matter which website or repo a user has landed on, guide them quickly and easily to the right tool for their job, i.e. the right library and the right API for that library.

Will be discussed July 3rd

Put HoloViz more to the front: making it clear on each project website that they are part of HoloViz, linking more to holoviz.org, improving the holoviz.org story of what can be done with the intersection of the HoloViz packages (panel+hvplot/geo/holoviews+datashader(+bokeh)), improving the interoperability between the HoloViz packages (aka viz dashboards made easy).
Following the work on Panel, keeping on improving the docs by completing Panel's work (API docs) and proceeding to hvPlot's overhaul
On a personal level, I'd like to spend a lot more time maintaining hvPlot (which fits with 1. and 2.)

Improve the structure of Panel's technical reference material (primarily the API reference and component gallery sections-#4305)
Improve guidance on tool selection as part of the getting started experience on HoloViz.org (#351)
Reduce energy barriers to first-time contributions. For instance, improving/coordinating contributor guides or getting the complete docs build time down to seconds. IMO, dramatically prioritizing this point would benefit all aspects of HoloViz.
Start applying the Panel docs format to hvPlot and HoloViews

Datashader:

Complete the matrix of support for all Reduction classes and as many of the following as make sense: work on GPU, work using Dask, antialiasing, contained within a by reduction, contained within a where reduction. Ref https://datashader.org/api.html#reductions
Simplify the Reduction code which currently has many very similar functions in append and combine functions. This should reduce the code complexity and the number of numba functions. May be able to cache the numba functions.
Improve the documentation is line with recent changes to Panel, in particular by adding smaller How To Guides for specific tasks.

HoloViews:

Code: Keep on improving the code. I would like to look at the code in-depth and make plans to remove some part that is not tested or is no longer used.
Test: Update the test to use pytest with fixtures, not unittest.TestCase.
Test: Support running the tests in random order so it is possible to parallelize the tests.
Test: To improve or at least better understand how to change the plotting backend in the test suite. It could be related to the previous point.
Type hints: Begin adding type hints to HoloViews.
DEV: Update development infrastructure to use Hatch. I want to begin this transition as soon as possible.
DEV: Look into CI's build, docs, and tests concerning the warnings emitted but often ignored.

So, in general, improvements behind the scene.

I have been following HoloViz and its component libraries for several years and was originally drawn back to use it, specifically because of the Panel Tabulator component.
I need a FREE OSS highly-functional, high-performance Python-interactive table widget for Pandas to replace QGrid.  I liked Qgrid because it was highly functional, fast & big data scalable for 1M+ rows, preserved state after user interaction, was fully addressable as a Python object and many other features (sort columns, filters, groupby and many other Pandas).  Qgrid code ran in Flask, Jupyter Notebook and Django and other Python full-stack web frameworks.  QGrid was developed by Quantopian on top of SlickGrid.  However, Quantopian ran out of money and closed down; eventually Quantopian followers gave up maintaining Qgrid.   The R community has had HTMLtable for many years, offering high-quality, high-functionality table widgets "that just work".
Aggrid is a popular proprietary commercial alternative to Qgrid that is being heavily promoted by Streamlit (now a Snowflake property).   Streamlit is freemium software.  Aggrid is expensive (Starting at...$$$999 Per Developer).  Aggrid is still not very mature v0. for the open-source version.  Aggrid is a Javascript / Angular framework, very functional.  Many features have not been surfaced to Python.  The most important Aggrid features (row selection, groupby, and others) are locked to monthly or enterprise subscriptions.   The Streamlit community promotes Aggrid heavily through YouTube demos.
You can see more about the JavaScript hacks required to add free functionality to aggrid here:  Streamlit Ag-Grid
"Since AgGrid is a JavaScript-based grid, the background properties of columns or cells can be changed by adding JavaScript code to the Python code. I am adding the JsCode library to be able to use JS code in the Grid."
If Panel Tabulator offers a FOSS full-function alternative to Aggrid, it will lead to much greater adoption of the rest of Holoviz.
My vote is to focus on enhancing Tabulator to be a good strong FREE alternative ("competitor") to aggrid, and get fully functional as a simple-to-use component in Jupyter Notebook, Flask, Django and other tools.
With demos like PyGWalker from Kanaries.  PyGWalker is pretty cool.  Tabulator with other Holoviz widgets could equal or surpass PyGWalker.
I am willing to help with applications of Tabulator, but we have to get it wrapped into a Streamlit component to jump on the Streamlit bandwagon.  I found a Chinese port of Streamlit Component wrapper for Tabulator but it does not work completely.  I will post a link to it as soon as I re-find it.

For me the most important is removing the friction of getting started with Panel, hvPlot, param, HoloViews, ... in that order.
It is primarily about improving

Documentation
Fixing bugs
Support on Discourse and Discord
Communication on social media.
Speed/ Performance

authors: Hoxbro MarcSkovMadsen droumis ianthomas23 jbednar maximlt richlysakowski

repo: holoviz/holoviz


text:
Grouped/dodged bar charts not working as documented

ALL software version info
MacOS Big Sur, M1
Python 3.10.10
JupyterLab v3.5.2
hvplot 0.8.3
bokeh 3.1.1
Description of expected behavior and the observed behavior
I'm trying to make a dodged bar chart like the one in https://hvplot.holoviz.org/reference/pandas/bar.html#basic-bar-plots but the output is always stacked, never dodged
Complete, minimal, self-contained example code that reproduces the issue
I just downloaded this notebook https://hvplot.holoviz.org/reference/pandas/bar.html#basic-bar-plots and did run-all:

No errors in the console.

Indeed, seems to be a regression in Bokeh 3.x. See also https://github.com/holoviz/holoviews/issues/5726

authors: nicolaskruchten philippjfr

repo: holoviz/hvplot


text:
Unknown state

Hi there,
I've also discovered that my BEKO B5WFU78435WB (7002340002) it has one new task that HomeWhiz doesn't not recognize. Right now the washing machine is "washing" but Home Assistant shows "unknown" task
How can I get the "tasks" from HomeWhiz phone app and see what's wrong?

Hi 👋,
could you share some debug logs?
Thanks!

Hi there,
Yes, here we go:  homewhizz.log

Pretty much something isn't right in my washer_substate too. I've got washer-dryer and old versions of your Addon worked fine (before the breaking change).
Version 0.6 randomly was changing washer_substate but mainly stayed in "remove the laundry".
The latest version is constantly stuck on "washing finished, remove laundry" while all other options and sensors are flawless. See the screenshot

F999 9226 1840 7970 4793 37
It works correctly if I unplug the washing machine from the mains and plug it in again. For the following washing then the substate is reported fine, another washing after this fine and then after a day I do another washing and the substate is always "remove laundry".
I haven't used the app for a year and I am unable to test if the app reads the same status as.. For some reasons the app doesn't let you see the progress of washing unless you chose "download program". It used to do it before, I'm sure.

@cnecrea I decoded all the messages from your logs.
State: None
Substate: None
State: program_wool_handwash
Substate: None
State: program_mix
Substate: None
State: program_mix
Substate: None
State: program_drum_clean
Substate: None
State: program_drum_clean
Substate: washer_substate_program_started
State: program_drum_clean
Substate: washer_substate_program_started
State: program_drum_clean
Substate: washer_substate_washing
State: program_drum_clean
Substate: washer_substate_washing
State: program_drum_clean
Substate: washer_substate_washing
State: program_drum_clean
Substate: washer_substate_prewash
State: program_drum_clean
Substate: washer_substate_prewash
State: program_drum_clean
Substate: washer_substate_prewash
State: program_drum_clean
Substate: washer_substate_prewash
State: program_drum_clean
Substate: None
State: program_drum_clean
Substate: None
State: program_drum_clean
Substate: None
State: program_drum_clean
Substate: None
State: program_drum_clean
Substate: None
State: program_drum_clean
Substate: washer_substate_paused
State: program_delicates
Substate: None
State: program_wool_handwash
Substate: None
State: program_eco_40_60
Substate: None
State: program_cottons
Substate: None
State: None
Substate: None

The only "None" states, which should translate to unknown in Home assistant, are at the beginning and at the end. And those should be, according to the app, washing?

I'll close this issue for now as there haven't been any updates in some time.

authors: Mikescotland TechHummel cnecrea


text:
Switch order of ValueNotification and Value update so that the notification includes the latest value

In #154 the order of operations for creating the ValueNotification was wrong and led to the value that came in the notification being returned as the value that we was previously in the state (see https://github.com/home-assistant/core/issues/47432). This fixes the order of operations.
I could use some help writing some good test cases for this one, I don't think we have enough given all the issues that have occurred as we try to fix this

@kpine can you take a look at this and see if it makes sense since you spotted this immediately?

I was wondering, why is value modified at all? Isn't it needed just to get the metadata? These notifications are supposed to be events or stateless values, not value updates.

To test this I'd create a Value instance on the node and then create an event coming in with new data. The ValueNotification data should then be created with the Value instance data as base but be updated with the new data from the event. So we need to make sure that we can assert that difference when creating the initial Value and event data

I was wondering, why is value modified at all? Isn't it needed just to get the metadata? These notifications are supposed to be events or stateless values, not value updates.

Yes, it doesn't sound like the Value state should be updated when reading the docs about ValueNotification event:
https://zwave-js.github.io/node-zwave-js/#/api/node?id=quotvalue-notificationquot

Is there any pre-existing method to do this?
value_notification.update(value.metadata)
I imagine value.metadata doesn't exist yet...

ah, perhaps it does...
so maybe this value_notification.metadata.update(value.metadata)

value_notification.metadata.update(value.metadata.data)

Just tested on my prod setup, this works, and resolves https://github.com/home-assistant/core/issues/47432

value_notification.metadata.update(value.metadata.data)

To test this I'd create a Value instance on the node and then create an event coming in with new data, that should trigger a ValueNotification event. The ValueNotification data should then be created with the Value instance data as base but be updated with the new data from the event. So we need to make sure that we can assert that difference when creating the initial Value and event data

So it looks like my tests are missing a value in the args part of the value notification event, and I don't test the value explicitly. If I were to add it with a different value from the Values value, and then check it, would that be sufficient?

To test this I'd create a Value instance on the node and then create an event coming in with new data, that should trigger a ValueNotification event. The ValueNotification data should then be created with the Value instance data as base but be updated with the new data from the event. So we need to make sure that we can assert that difference when creating the initial Value and event data

So it looks like my tests are missing a value in the args part of the value notification event, and I don't test the value explicitly. If I were to add it with a different value from the Values value, and then check it, would that be sufficient?

actually, the Value in my test data doesn't even have a value, so if I add a value to the notification, we can guarantee it's coming from the notification event if the ValueNotification has a value

value_notification.metadata.update(value.metadata.data)

The problem with this approach is that ValueNotification.endpoint is None. There are two ways to solve this:

Update the entire value_notification.data. This may have unintended side effects but not sure.
Update the endpoint property to return 0 by default. I think this is safe because every value has to be on an endpoint, doesn't it?

I think the endpoint is not included from the ValueNotification, so the endpoint shouldn't be included in the HA event?

I think the endpoint is not included from the ValueNotification, so the endpoint shouldn't be included in the HA event?

The notification is for a value that does have an endpoint. There's a third option, see my upcoming commit

Looks good!
FYI, my scene activation and basic set events do include endpoint from the server.

authors: MartinHjelmare jcam kpine raman325


text:
Adding support for deployment_key for git_pull addon

The main idea is to allow the user to provide a private key which will be used typically as "deployment_key".
The json will be something like:
{ (...)
  "deployment_key": [
"-----BEGIN RSA PRIVATE KEY-----",
"MIIEpAIBAAKCAQEArNTRDaU1nQ/Fcb5VttyxTuEEpf+W3tNe6QMVswAXAirDh4Do",
"WTC1/IFae89jId5FckmFOszskAqoCLjI6ZrnxP3ZLW7yVsDn7TkI0iR21DdJ/fSU",
(...)
"-----END RSA PRIVATE KEY-----"
],
  "deployment_key_protocol": "rsa"
}

The multiline is a bit messy, but seems the more comfortable way to make copy&paste. The alternative is to add \n for each line and remove the lines and the json becomes unreadable.
Note that deployment_key_protocol is optional and defaults to rsa. The idea is to allow the user to allow any of the typically supported ssh protocols for identities, which are:

dsa
ecdsa
ed25519
rsa

I don't consider the ~/.ssh/identity, which appears in the man pages, but I have never seen it nowadays. I assume most people will do ssh-keygen and just forget about the protocol (rsa seems to be the default in all the ssh packages I have ever used). All the aforementioned protocols are suffix to ~/.ssh/id_<suffix> so that is simply used as the file name.
If this PR sounds good, I am ready to add the documentation for it.

We can also use /share/keys if you think that make more sense and add a options to set the name, like we use on google_assistant or snips?

I didn't like the idea to require Samba in order to use that. Because that is the only method I have seen that can be used in order to upload a file like a key. But if you think is better I can change.
The deployment key doesn't change (typically is set and forgotten) so a bit messy initial setting may not be so bad.

For me, it dosn't matter. It should be user friendly as it is possible. So if you prefere this, it is okay.
You can also use scp/sftp with ssh add-on to access to share. If you know a nice webinterface for data handling (like file station from synology) we can add it as add-on.
Anyway, you are free to handle that as file or as options. For me is both okay :+1:

Do we neef also the openssh client?

I think that the current workaround for multiline-private-key-into-config-json is good enough. It should be enough for my scenario, and I assume that it will be a common case for people having private repos somewhere (either cloud or "in premises").
Last two commits should address your comments.

Please update also the website

"repository": "match((?:git|ssh|https?|git@[-\\w.]+):(\/\/)?(.*?)(\\.git)(\/?|\\#[-\\d\\w._]+?))",
This needs to improve, because some of us aren't using github, for instance mine is gitlab@git.domain.com:group/repo.git
I'd suggest a regexp which can match anything word before @.

@jonkristian I think that you meant to comment on home-assistant/hassio-addons#198
Because that line that you are quoting is from that PR, not this one. I was very confused at first...

@alexbarcelo So sorry about the confusion. Should I move my comment?

authors: alexbarcelo jonkristian pvizeli

repo: home-assistant/hassio-addons


text:
Fix typo: BUILT_TYPE -> BUILD_TYPE

Sidenote: have issues been disabled intentionally for this repo?

I build a new release in 10min

authors: pschmitt pvizeli

repo: home-assistant/hassio-build


text:
Alert window doesn't has correct title or button

When the frontend uses the JavaScript alert(), it shows an alert to the user with the wrong title and a missing caption for the OK button (button does work).

@gmatyszczak does this also fix the %s or should I open a new issue for that?

I couldn't reproduce the issue with %s. Could you provide steps? Or retest it on your side?

Cannot reproduce either anymore. Perfect !

authors: balloob gmatyszczak

repo: home-assistant/home-assistant-android


text:
Cast groups unavailable

Home Assistant release with the issue:
0.66.0.beta1
Last working Home Assistant release (if known):
0.65.6
Operating environment (Hass.io/Docker/Windows/etc.):
Raspbian GNU/Linux 9 (stretch)
Component/platform:
media_player.cast
Description of problem:
Since update to the latest beta version, my cast groups are unavailable now and then. However, the single devices of the groups can be controlled, but not the groups itself. I encountered this issues typically in the morning. When restarting HASS, all cast devices and groups are available, again.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
discovery:
media_player:
  - platform: cast

Traceback (if applicable):

Additional information:

Hmmm, thanks for reporting this 👍
Seems a lot like https://github.com/home-assistant/home-assistant/issues/13483 and probably due to the groups changing their "elected leader". Could you also enable debug logs as mentioned in the comment in there? It would really help.

Maybe back to the original elected leader? :)

Hmmm, that might be it, but I have not idea how that could affect the socket client. Oh gosh, this is getting interesting... 😂

@dshokouhi The problem is that not only the host (or IP address) of the device that is the "elected leader" or the device that accepts all commands changes, but also the port number. And that dynamically, so there's no way that a user can list the cast members in their configuration.
btw, from what I know now, the issue is not related to the discovery aspect of the cast integration. In fact, we discover elected leader changes just fine. The issue seems to be somewhere in the disconnect from old leader + connect to new leader code.

Oh wow nice to hear you guys seem to have pinned down the issue :) if you need any help testing I am sure myself and others would be glad to help.

I'm still trying to find out what exactly caused this, but If you'd like to help 😬, it would be good to know whether with the following configuration the issue still happens (with discovery: disabled).
media_player:
  - platform: cast
    scan_interval: 1234567890

I personally am not seeing the issue with my setup with that config, but it would be good to get some data from others too. This configuration should not really affect anything and the cast integration should still work (without the new semi-polling mode I introduced in the linked PR). If the error doesn't appear with that configuration, it would mean that we know the code change that caused this, but I still have no idea why the connections drop.

Ok I have disabled discovery for google_cast, and applied the same config for the media_player component.  Will reply back if I notice the issue.

@OttoWinter the issue came back overnight, one of my groups is currently unavailable and the other one went unavailable over night and became available again.

@dshokouhi Ok. At least that rules out one possible explanation... Thanks very much!

I'd be happy to help test as well if there's are any new updates,

I just closed my issue after troubleshooting and determining that cast groups are causing my problems, and that this issue probably relates to mine.
If I include cast groups in global or cast discovery, then I lose the ability to cast to all but a few of my cast-enabled devices when Home Assistant starts up.  If I explicitly define just the individual devices and exclude cast groups, then everything works fine.  As a point of clarification, when I say "lose the ability to cast", I mean that when I hit the cast icon in Pandora, Spotify, or Google Play Music, I only get the devices with very old firmwares as options (Sony Speaker with Chromecast Built-In and an Insignia Alarm Clock with Chromecast Built-in).  None of the Chromecast Audios, Google Homes, Nvidia Shields, nor any of the associated groups show up.
I've attached a log.
home-assistant test2.log

I'm also seeing this behaviour today, running Home Assistant 0.67.1:

The more-info dialog shows the details of the bottom group, but the state of the top group is identical. I also have the individual Chromecast Audio units in my Home Assistant setup and it seems one of them (Garoeda I) was unavailable for about half a minute. This caused the two groups (that include that specific Chromecast Audio) to become and remain unavailable.
This is what syslog logged on my Raspberry Pi 3:
pi@Ra:~ $ cat /var/log/syslog | grep unavailable
Apr 22 17:13:41 Ra hass[13460]: #033[32m2018-04-22 17:13:41 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.garoeda_i, old_state=<state media_player.garoeda_i=off; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-22T04:38:21.736327+02:00>, new_state=<state media_player.garoeda_i=unavailable; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-22T17:13:41.211439+02:00>>#033[0m
Apr 22 17:13:42 Ra hass[13460]: #033[32m2018-04-22 17:13:42 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home_audio, old_state=<state media_player.home_audio=off; friendly_name=Home Audio, supported_features=21437 @ 2018-04-22T04:38:21.754878+02:00>, new_state=<state media_player.home_audio=unavailable; friendly_name=Home Audio, supported_features=21437 @ 2018-04-22T17:13:42.196000+02:00>>#033[0m
Apr 22 17:13:47 Ra hass[13460]: #033[32m2018-04-22 17:13:47 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home_audio_with_bathroom, old_state=<state media_player.home_audio_with_bathroom=unavailable; friendly_name=Home Audio with bathroom, supported_features=21437 @ 2018-04-22T15:47:52.989243+02:00>, new_state=<state media_player.home_audio_with_bathroom=off; friendly_name=Home Audio with bathroom, supported_features=21437 @ 2018-04-22T17:13:47.477800+02:00>>#033[0m
Apr 22 17:13:47 Ra hass[13460]: #033[32m2018-04-22 17:13:47 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home_audio, old_state=<state media_player.home_audio=unavailable; friendly_name=Home Audio, supported_features=21437 @ 2018-04-22T17:13:42.196000+02:00>, new_state=<state media_player.home_audio=off; friendly_name=Home Audio, supported_features=21437 @ 2018-04-22T17:13:47.500569+02:00>>#033[0m
Apr 22 17:14:16 Ra hass[13460]: #033[32m2018-04-22 17:14:16 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.garoeda_i, old_state=<state media_player.garoeda_i=unavailable; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-22T17:13:41.211439+02:00>, new_state=<state media_player.garoeda_i=off; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-22T17:14:16.308174+02:00>>#033[0m
Apr 22 17:14:16 Ra hass[13460]: #033[32m2018-04-22 17:14:16 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home_audio_with_bathroom, old_state=<state media_player.home_audio_with_bathroom=off; friendly_name=Home Audio with bathroom, supported_features=21437 @ 2018-04-22T17:13:47.477800+02:00>, new_state=<state media_player.home_audio_with_bathroom=unavailable; friendly_name=Home Audio with bathroom, supported_features=21437 @ 2018-04-22T17:14:16.640050+02:00>>#033[0m
Apr 22 17:14:16 Ra hass[13460]: #033[32m2018-04-22 17:14:16 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home_audio, old_state=<state media_player.home_audio=off; friendly_name=Home Audio, supported_features=21437 @ 2018-04-22T17:13:47.500569+02:00>, new_state=<state media_player.home_audio=unavailable; friendly_name=Home Audio, supported_features=21437 @ 2018-04-22T17:14:16.659293+02:00>>#033[0m

And this is what happened according to Home Assistant:
2018-04-22 17:13:41 WARNING (Thread-6) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-04-22 17:13:42 WARNING (Thread-8) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-04-22 17:13:51 ERROR (Thread-10) [pychromecast.socket_client] Failed to connect. No retries.
2018-04-22 17:14:11 ERROR (Thread-6) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-04-22 17:14:12 ERROR (Thread-8) [pychromecast.socket_client] Failed to connect: timed out. aborting due to stop signal.
2018-04-22 17:14:16 ERROR (Thread-11) [pychromecast.socket_client] Error reading from socket.
2018-04-22 17:14:16 ERROR (Thread-12) [pychromecast.socket_client] Error reading from socket.
2018-04-22 17:14:16 WARNING (Thread-11) [pychromecast.socket_client] Error communicating with socket, resetting connection
2018-04-22 17:14:16 WARNING (Thread-12) [pychromecast.socket_client] Error communicating with socket, resetting connection
2018-04-22 17:14:16 ERROR (Thread-11) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-04-22 17:14:16 ERROR (Thread-12) [pychromecast.socket_client] Failed to connect, retrying in 5.0s

My configuration for the Cast component is basic:
- platform: cast

Did some further testing today and have included the logs and some screenshots.  The first screenshot is my casting choices when cast groups are turned off in Home Assistant, but all other cast devices are turned on (meaning I'm selecting them individually with their host ip address).  Everything shows up, including the groups.
The "home assistant log test6" is when I turned groups on by:
platform: cast
While Home Assistant was running, I also restarted the router and then restarted every single cast device individually.  All that should be evident in the log.  None of that worked as you can see in screenshot 2, which is my list of casting choices.  The Sony speaker and the Insignia Alarm clock, both running much older versions of chromecast software are the only devices present.  The groups you see are groups that contain one or both of those two devices.
I then commented out platform: cast to remove the groups, but kept my individual selections by host, ie:
###platform: cast

platform: cast
   host: 192.168.85.141
   name: Living Room

Just like screenshot 1, all my device and groups now show up as cast targets.  I included "home assistant log test7" with these conditions to compare against test6.

home-assistant test6.log
home-assistant test7.log

Can you cast to your devices from, say, your phone, when they show as unavailable in Home Assistant?  While I didn't post any screenshots, I too am seeing devices and groups become unavailable.  I've always assumed the two issues were related.  However, if you're still able to cast to a device / group that's unavailable in Home Assistant, then I agree I may have a different issue.

I will have to test that when my Cast groups are unavailable the next time, as they have suddenly gone back to their off state almost 2 hours ago:

Syslog:
pi@Ra:~ $ cat /var/log/syslog | grep unavailable
Apr 23 02:17:23 Ra hass[13460]: #033[32m2018-04-23 02:17:23 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home_audio, old_state=<state media_player.home_audio=unavailable; friendly_name=Home Audio, supported_features=21437 @ 2018-04-22T17:14:16.659293+02:00>, new_state=<state media_player.home_audio=off; friendly_name=Home Audio, supported_features=21437 @ 2018-04-23T02:17:23.181650+02:00>>#033[0m
Apr 23 02:17:23 Ra hass[13460]: #033[32m2018-04-23 02:17:23 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home_audio_with_bathroom, old_state=<state media_player.home_audio_with_bathroom=unavailable; friendly_name=Home Audio with bathroom, supported_features=21437 @ 2018-04-22T17:14:16.640050+02:00>, new_state=<state media_player.home_audio_with_bathroom=off; friendly_name=Home Audio with bathroom, supported_features=21437 @ 2018-04-23T02:17:23.219506+02:00>>#033[0m
Apr 23 02:17:43 Ra hass[13460]: #033[32m2018-04-23 02:17:43 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.garoeda_i, old_state=<state media_player.garoeda_i=off; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-22T17:14:16.308174+02:00>, new_state=<state media_player.garoeda_i=unavailable; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-23T02:17:43.591443+02:00>>#033[0m
Apr 23 02:17:59 Ra hass[13460]: #033[32m2018-04-23 02:17:59 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.garoeda_i, old_state=<state media_player.garoeda_i=unavailable; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-23T02:17:43.591443+02:00>, new_state=<state media_player.garoeda_i=off; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-23T02:17:59.393369+02:00>>#033[0m

Home Assistant log:
2018-04-23 02:17:43 WARNING (Thread-6) [pychromecast.socket_client] Heartbeat timeout, resetting connection

Please test to see if they are available as cast targets regardless of status.  What I've found is that whether they are "off" or "unavailable", they will not show up as available to cast to from Pandora, Google Play Music, or any other app that has cast capability.  I'd love to have validation of that behavior.

Please test to see if they are available as cast targets regardless of status.  What I've found is that whether they are "off" or "unavailable", they will not show up as available to cast to from Pandora, Google Play Music, or any other app that has cast capability.  I'd love to have validation of that behavior.

It's very weird.  Regardless of the media player status within Home Assistant, I can tell a Google Home to play a song on any of the individual Chromecast Audios or Google Homes and it will do so.  If I try tell it to play to a cast group, however, only one set of speakers will play, which I assume is the leader of the group.  And if I open Pandora or Google Play Music and hit the Cast icon, none of the individual devices or groups show up as options (except - as noted in an earlier comment - the older firmware devices with Chromecast built-in from Sony and Insignia.  Those are solid).
As a reminder, this behavior is only when I have Home Assistant running with platform: cast discovering the groups.  If I allow it to only discover the individual cast players, then everything works fine both in Home Assistant and in Pandora, Google Home, etc.

In addition to unavailable I just noticed unknown as well.

@dshokouhi Are you using cast groups in Home Assistant?  I've found if I remove them, then the unavailable issue goes away (unfortunately, so too does a bunch of functionality).  Could you test by  removing cast groups and see if you get to:

@benjamin1492 this bug is only about cast groups so removing them to test is not an option.  They need to work which is why we are troubleshooting this.

Understood.  I'll wait on the resolution to this one, and if it doesn't fix my problem, I'll reopen my other case.  For now, I'll leave ya'll alone to get the cast groups fixed.

I am having an issue where none of my cast components show up in home assistant anymore even if I use discovery.

So my problem is definitely different.  Running the beta, I was able to get all the devices to A) show as available in Hass, and B) show as cast targets.  But that only lasted for about 15 minutes before I was back to A) only the leader playing when cast group selected, and B) having no cast targets for GPM or Pandora.  The 15 minutes to failure is an improvement...used to be instantaneous as soon as I started Hass.

@benjamin1492 have you tried removing/unplugging devices one by one to see if one of them is a factor?

Just chiming in because I'm seeing the same thing.   My group will randomly go "unavailable" a few times a day, and then a few hours later it goes back to available again.   I only have two devices in the group, so it seems plausible that when the leader selection is changed, it toggles between the two devices.   At this moment, it's showing as unavailable in HA, but I'm able to use the group with Pandora

Hi, so I had another look at this problem today to see what could be causing this. One potential problem is that the disconnection logic is currently not perfect and we don't wait until the previous socket has truly disconnected when re-establishing a connection. This doesn't seem like something that could cause this error to me but I'm running out of potential causes.
I've update the cast integration a bit to resolve above issue. If someone wants to help, copy this file to <config_dir>/custom_components/media_player/cast.py. I'm not sure if it would solve the issue but it would at least be worth a try.

I've been running that 4/28 version for about a day and it hasn't solved the problem, but subjectively, I think it may a little different.   It went unavailable three times today, but both were only for a minute or so (rather than hours like I think it was before)

@psfales Thanks for testing! I think 30 seconds to 60 seconds are more or less expected and there's not much we can do to cut this time down:

It takes 10-15 seconds until we receive the mDNS message with the new host.
Then we need to disconnect from the old chromecast. Can take up to 5-10 seconds depending on the amount of data waiting to be transferred and so on.
Finally, we need to connect to the new host. Can take 10+ seconds. Especially while the new host is still setting up to receive connections.

Unfortunately, it hasn't stayed so good.   It went unavailable at 5:30 this morning and stayed unavailable for 2.5 hours until I rebooted

Oh noes :/ Reopening then...
Unfortunately, I won't be able to work on this for the next week and a half though because I'm in the process of studying for my final exams 📚

Certainly understand about your schedule.   When you have time, I'm curious....  Is it possible to tell when the elected leaders changes, or which device it is at any given time?   I think it would be interesting to confirm that the group going unvailable (or return to available) is correlated with a leader change.

There's no real visual way to see that from the front-end. But if you have debug logs enabled you can see a Disconnecting from previous chromecast message in there when a leader change is detected.

I experience this problem I'm pretty new to Homeassistant but am a developer. Let me know if you need anything!

I also have this problem. Not a developer but happy to test/help where I can.

I just realized that I have another chromecast devices (not group) that became unavailable prior to the chromecast group, 3 mins after the single device became available again, the group went unavailable.
The kitchen devices unavailablitiy is not restricted to chromecast, when it's unavailable in chromecast, it's not reachable from any other apps either. "All"s problems is howeber only limited to chromecast. Let me know if I can helt in any way :)

Same goes for me and the time a group takes to become unavailable seems totally random. I went away for a week so no music was played via other devices and on my return all groups were available. Unsure if a total fluke or due to not casting from other devices there was no need to elect a new group "leader". I presume Home Assistant was casting TTS weather alerts etc because i forgot to switch them off.

@JIOB, did you check your history? i'd be really curious to kno if not
interacting with it caused it to hold stable
On Fri, May 18, 2018 at 5:15 AM JIOB notifications@github.com wrote:

Same goes for me and the time a group takes to become unavailable seems
totally random. I went away for a week so no music was played via other
devices and on my return all groups were available. Unsure if a total fluke
or due to not casting from other devices there was no need to elect a new
group "leader". I presume Home Assistant was casting TTS weather alerts etc
because i forgot to switch them off.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/13530#issuecomment-390188171,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEuJQHrfPVcCjQ3uWSxKLDI_pSNvpWk1ks5tzrtNgaJpZM4TADhw
.

I didn't check at the time and its since been overwritten. If the same situation occurs again prior to a fix ill ensure i've got a log to share.

Not my proudest work, but I just did this as a cludge:
- alias: 'All unavailable for 3 minutes'
  trigger:
    platform: state
    entity_id: media_player.all
    to: 'unavailable'
    for:
      minutes: 15
  action:
    service: homeassistant.restart

homeassistant reboots whenever the group is unavialable for more than 15 minutes. I have a feeling this will come back and bite me in the ass...

I am actually wondering if maybe the cast platform can create a service call that allows us to basically "reload" the groups like what happens during a home assistant restart.  A hass restart is the only way to bring the groups back maybe there is a way to trigger the rediscovery of just the cast groups when they become unavailable?  I think I saw some platforms use unloading like hue maybe something similar can be triggered here?  Sorry if I am shooting in the dark just trying to help offer ideas/suggestions :)

I have been thinking the same, but not sure if it has to be a service, it should just do it if the groups lose connection in that case.

It's because of mess with configuration.
I had same problem, I checked all my configuration an there was some parts that I correct them. Then I removed the database and restart the machine. It's been about 10 days that I don't have that problem anymore.

I agree with @dshokouhi and @kristoffernolgren it would be nice if some logic could be built in to restart the service when a group/groups become unavailable.
@aliaghil which parts of your configuration did you correct? My configuration now only contains..
  - platform: cast

In my configuration I had this code in sensors:
`
sensor:

platform: systemmonitor
resources:

type: since_last_boot
type: processor_use
type: memory_free
type: disk_free
arg: /

platform: template
sensors:
time_template:
friendly_name: Time
value_template: '{{ as_timestamp(now()) | timestamp_custom("%d/%m   %H:%M", True) }}'
since_last_boot_template:
friendly_name: Up Time
value_template: >
{%- set s = states.sensor.since_last_boot.state.split('.')[0] -%}
{{ s }}

platform: version
name: version
and I changed it to:
sensor:

platform: systemmonitor
resources:

type: since_last_boot
type: processor_use
type: memory_free
type: disk_free
arg: /

platform: template
sensors:
time_template:
friendly_name: "Time"
value_template: '{{ as_timestamp(now()) | timestamp_custom("%d/%m   %H:%M", True) }}'
since_last_boot_template:
friendly_name: "Up Time"
value_template: >
{%- set s = states.sensor.since_last_boot.state.split('.')[0] -%}
{{ s }}

platform: version
name: "Version"
`
In my sensors wherever there was friendly_name: I used quotation mark for it.

After version 0.60 developers add cloud component, and I add it to my configuration, but didn't use it, even I didn't login to it. I think the problem was because of this, after I confined it, and logged in to it, the problem gone.

in configuration.yaml i had this:
`
homeassistant:
customize_glob: !include config/customize_glob.yaml
packages: !include_dir_named config/packages/
frontend:
extra_html_url:

/local/custom_ui/state-card-custom-ui.html
I disabled that two.
homeassistant:

customize_glob: !include config/customize_glob.yaml
packages: !include_dir_named config/packages/
frontend:
extra_html_url:
- /local/custom_ui/state-card-custom-ui.html
`

I was using separated config
I found it out, these files shouldn't go in the config folder  config/config
automations.yaml
entity_registry.yaml
known_devices.yaml
scripts.yaml
secrets.yaml
I bring them back to root config folder config

the last one
I update all my automation with Automation editor.

@aliaghil are you saying that those steps have permanently fixed your instance of the cast component?

@JIOB yes. I update hassio to 0.71.0 and unfortunately the problem come back again :(
I'm going to downgrade it to v0.70.1 and see what's going on...

Just updated HomeAssistant to 0.72.0 and it forced me to reconfigure my Google cast devices. Anybody know if the change has the ability to fix this issue? Will post back if i find anything.

I also updated to 0.72.0 and got the dialog about forcing me to reconfigure
Google Cast.   But I don't understand what this means.    It apparently
created a file in the config directory called ".config_entries.json" which
has an entry for "Google Cast."   But other than that one-time interaction
I don't see any change in behavior.  "Google Cast" does not appear anywhere
in the UI and all the Chromecast, Chromecast Audio, and audio groups that
were there before are still lthere.
On Sun, Jun 24, 2018 at 6:28 AM, JIOB notifications@github.com wrote:

Just updated HomeAssistant to 0.72.0 and it forced me to reconfigure my
Google cast devices. Anybody know if the change has the ability to fix this
issue? Will post back if i find anything.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/13530#issuecomment-399749490,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKyoCsrJK8dEx3GKnh19WWJhmAk19vjBks5t_3fbgaJpZM4TADhw
.

After updating to 0.72.0 and using the new UI config method, I am still experiencing this issue. So it doesn't look like the new config method fixed the issue.

I am having the same issue here with 0.72.
Individual devices work, by group gets dropped. I do not recall having this issue before
The HA log shows the issue happening first two nights ago @2:38am, which seems to somehow recovered (stopped reporting errors in the log) , and similar errors last nigh @2:27am , which have not recovered yet

2018-07-05 02:38:17 ERROR (Thread-10) [pychromecast.socket_client] Error reading from socket.
2018-07-05 02:38:17 WARNING (Thread-10) [pychromecast.socket_client] Error communicating with socket, resetting connection
2018-07-05 02:38:17 ERROR (Thread-10) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-05 02:38:22 ERROR (Thread-10) [pychromecast.socket_client] Failed to connect. No retries.
2018-07-05 02:38:39 WARNING (Thread-8) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-05 02:38:54 ERROR (Thread-8) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-05 02:41:58 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-05 02:42:05 ERROR (Thread-9) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-05 03:05:35 WARNING (Thread-7) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-05 03:05:38 ERROR (Thread-7) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-05 03:29:43 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved

2018-07-06 02:27:17 ERROR (Thread-191485) [pychromecast.socket_client] Error reading from socket.
2018-07-06 02:27:17 WARNING (Thread-191485) [pychromecast.socket_client] Error communicating with socket, resetting connection
2018-07-06 02:27:17 ERROR (Thread-191485) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-06 02:27:22 ERROR (Thread-191485) [pychromecast.socket_client] Failed to connect. No retries.
2018-07-06 02:27:45 WARNING (Thread-8) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-06 02:27:52 ERROR (Thread-8) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-06 02:51:57 WARNING (Thread-7) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-06 02:52:04 ERROR (Thread-7) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-06 02:52:15 ERROR (Thread-481327) [pychromecast.socket_client] Error reading from socket.
2018-07-06 02:52:15 WARNING (Thread-481327) [pychromecast.socket_client] Error communicating with socket, resetting connection
2018-07-06 02:52:15 ERROR (Thread-481327) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-06 04:35:58 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-06 04:36:01 ERROR (Thread-9) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-06 07:41:15 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting

I use Chromecast Audio groups extensively and use playing/off state changes to trigger many automations. (volume setting, turning off and on connected amps etc).
Here's a log from last night, which shows the groups becoming unavailable at 22:36, coming back 61s later, then going unavailable again 1s later. The groups recover during the night.
There are two groups, "All" and "Downstairs". "sony" is the A/V receiver with cast built in. 'sony_2' is the songpal component of same device. I doubt that's relevant, other than to show that songpal and pychromecast both report unavailable at roughly the same times.
Casting GPM to the CCA 'bedroom' begins at 22:23 and ends at 23:22.

2018-07-11 22:23:36 INFO bedroom -> 'idle'
2018-07-11 22:23:36 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service_data=entity_id=media_player.bedroom, volume_level=0.15, service_call_id=1975828368-6972, service=volume_set, domain=media_player>
2018-07-11 22:23:36 INFO (Thread-21) [pychromecast.controllers] Receiver:setting volume to 0.1
2018-07-11 22:23:36 INFO bedroom -> 'playing'
...
2018-07-11 22:34:33 INFO bedroom -> 'playing'
2018-07-11 22:36:01 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.60', port=8009, uuid='afb73d06-77f7-39df-d206-0b98b58be99d', model_name='STR-DN860', friendly_name='Sony')
2018-07-11 22:36:04 WARNING (Thread-53) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-11 22:36:06 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.60', port=42904, uuid='02005ffe-7f5c-4512-b118-50e1d4f87cdc', model_name='Google Cast Group', friendly_name='All')
2018-07-11 22:36:06 DEBUG (Thread-53) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-11 22:36:06 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.60', port=42760, uuid='c790e2bc-dae8-439b-8ab9-408266d10422', model_name='Google Cast Group', friendly_name='Downstairs')
2018-07-11 22:36:06 WARNING (Thread-52) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-11 22:36:06 DEBUG (Thread-52) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-11 22:36:06 INFO downstairs -> 'unavailable'
2018-07-11 22:36:06 INFO all -> 'unavailable'
2018-07-11 22:36:11 WARNING (Thread-24) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-11 22:36:11 DEBUG (Thread-24) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-11 22:36:11 INFO sony -> 'unavailable'
2018-07-11 22:36:36 ERROR (Thread-53) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-11 22:36:36 ERROR (Thread-52) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-11 22:36:41 ERROR (Thread-24) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-11 22:37:19 INFO sony_2 -> 'unavailable'
2018-07-11 22:37:55 INFO sony_2 -> 'off'
2018-07-11 22:37:55 DEBUG (Thread-52) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-11 22:37:55 INFO all -> 'off'
2018-07-11 22:37:55 DEBUG (Thread-24) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-11 22:37:55 DEBUG (Thread-53) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-11 22:37:55 INFO sony -> 'off'
2018-07-11 22:37:55 INFO downstairs -> 'off'
2018-07-11 22:37:56 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.60', port=8009, uuid='afb73d06-77f7-39df-d206-0b98b58be99d', model_name='STR-DN860', friendly_name='Sony')
2018-07-11 22:37:56 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered chromecast ChromecastInfo(host='10.100.39.92', port=42904, uuid='02005ffe-7f5c-4512-b118-50e1d4f87cdc', model_name='Google Cast Group', friendly_name='All')
2018-07-11 22:37:56 DEBUG (MainThread) [homeassistant.components.media_player.cast] Discovered chromecast with same UUID: ChromecastInfo(host='10.100.39.92', port=42904, uuid='02005ffe-7f5c-4512-b118-50e1d4f87cdc', model_name='Google Cast Group', friendly_name='All')
2018-07-11 22:37:56 DEBUG (MainThread) [homeassistant.components.media_player.cast] Disconnecting from chromecast socket.
2018-07-11 22:37:56 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered chromecast ChromecastInfo(host='10.100.39.92', port=42760, uuid='c790e2bc-dae8-439b-8ab9-408266d10422', model_name='Google Cast Group', friendly_name='Downstairs')
2018-07-11 22:37:56 INFO all -> 'unavailable'
2018-07-11 22:37:56 DEBUG (MainThread) [homeassistant.components.media_player.cast] Discovered chromecast with same UUID: ChromecastInfo(host='10.100.39.92', port=42760, uuid='c790e2bc-dae8-439b-8ab9-408266d10422', model_name='Google Cast Group', friendly_name='Downstairs')
2018-07-11 22:37:56 DEBUG (MainThread) [homeassistant.components.media_player.cast] Disconnecting from chromecast socket.
2018-07-11 22:37:56 INFO downstairs -> 'unavailable'
2018-07-11 22:38:01 DEBUG (MainThread) [homeassistant.components.media_player.cast] Connecting to cast device ChromecastInfo(host='10.100.39.92', port=42760, uuid='c790e2bc-dae8-439b-8ab9-408266d10422', model_name='Google Cast Group', friendly_name='Downstairs')
2018-07-11 22:38:01 INFO (Thread-20) [pychromecast] Querying device status
2018-07-11 22:38:01 DEBUG (MainThread) [homeassistant.components.media_player.cast] Connecting to cast device ChromecastInfo(host='10.100.39.92', port=42904, uuid='02005ffe-7f5c-4512-b118-50e1d4f87cdc', model_name='Google Cast Group', friendly_name='All')
2018-07-11 22:38:01 ERROR (Thread-20) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-11 22:38:01 INFO (Thread-6) [pychromecast] Querying device status
2018-07-11 22:38:01 ERROR (Thread-6) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-11 22:39:20 INFO bedroom -> 'idle'
2018-07-11 22:39:20 INFO bedroom -> 'playing'
...
2018-07-11 23:22:37 INFO bedroom -> 'playing'
2018-07-11 23:22:51 INFO (Thread-11) [pychromecast] Quiting current app
2018-07-11 23:22:51 INFO (Thread-11) [pychromecast.controllers] Receiver:Stopping current app '2872939A'
2018-07-11 23:22:51 INFO bedroom -> 'off'
2018-07-11 23:37:14 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered chromecast ChromecastInfo(host='10.100.39.60', port=42904, uuid='02005ffe-7f5c-4512-b118-50e1d4f87cdc', model_name='Google Cast Group', friendly_name='All')
2018-07-11 23:37:14 DEBUG (MainThread) [homeassistant.components.media_player.cast] Discovered chromecast with same UUID: ChromecastInfo(host='10.100.39.60', port=42904, uuid='02005ffe-7f5c-4512-b118-50e1d4f87cdc', model_name='Google Cast Group', friendly_name='All')
2018-07-11 23:37:14 DEBUG (MainThread) [homeassistant.components.media_player.cast] Connecting to cast device ChromecastInfo(host='10.100.39.60', port=42904, uuid='02005ffe-7f5c-4512-b118-50e1d4f87cdc', model_name='Google Cast Group', friendly_name='All')
2018-07-11 23:37:14 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered chromecast ChromecastInfo(host='10.100.39.60', port=42760, uuid='c790e2bc-dae8-439b-8ab9-408266d10422', model_name='Google Cast Group', friendly_name='Downstairs')
2018-07-11 23:37:14 INFO (Thread-3) [pychromecast] Querying device status
2018-07-11 23:37:14 DEBUG (MainThread) [homeassistant.components.media_player.cast] Discovered chromecast with same UUID: ChromecastInfo(host='10.100.39.60', port=42760, uuid='c790e2bc-dae8-439b-8ab9-408266d10422', model_name='Google Cast Group', friendly_name='Downstairs')
2018-07-11 23:37:14 DEBUG (MainThread) [homeassistant.components.media_player.cast] Connecting to cast device ChromecastInfo(host='10.100.39.60', port=42760, uuid='c790e2bc-dae8-439b-8ab9-408266d10422', model_name='Google Cast Group', friendly_name='Downstairs')
2018-07-11 23:37:14 INFO (Thread-4) [pychromecast] Querying device status
2018-07-11 23:37:15 DEBUG (MainThread) [homeassistant.components.media_player.cast] Connection successful!
2018-07-11 23:37:15 INFO all -> 'off'
2018-07-11 23:37:15 DEBUG (MainThread) [homeassistant.components.media_player.cast] Connection successful!
2018-07-11 23:37:15 INFO downstairs -> 'off'
2018-07-12 02:23:21 WARNING (Thread-30) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-12 02:23:21 DEBUG (Thread-30) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-12 02:23:21 INFO lounge_mini -> 'unavailable'
2018-07-12 02:23:36 DEBUG (Thread-30) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-12 02:23:36 INFO lounge_mini -> 'off'
2018-07-12 02:23:38 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.89', port=8009, uuid='e957ad8e-8b83-0f38-97ae-89c501ce6e34', model_name='Google Home Mini', friendly_name='Lounge Mini')
2018-07-12 02:45:48 WARNING (Thread-29) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-12 02:45:48 DEBUG (Thread-29) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-12 02:45:48 INFO office -> 'unavailable'
2018-07-12 02:45:55 ERROR (Thread-29) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-12 02:46:00 DEBUG (Thread-29) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-12 02:46:00 INFO office -> 'off'
2018-07-12 02:46:03 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.94', port=8009, uuid='a0721def-786f-a924-c5cd-75cd5a7f569d', model_name='Chromecast Audio', friendly_name='Office')
2018-07-12 03:15:51 WARNING (Thread-28) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-12 03:15:51 WARNING (Thread-27) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-12 03:15:51 DEBUG (Thread-28) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-12 03:15:51 DEBUG (Thread-27) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-12 03:15:51 INFO chromecast_lounge -> 'unavailable'
2018-07-12 03:16:07 DEBUG (Thread-28) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-12 03:16:07 INFO chromecast_lounge -> 'off'
2018-07-12 03:16:10 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.91', port=8009, uuid='dd9ff914-24cf-86ad-5ed1-85ce9ac1af8e', model_name='Chromecast', friendly_name='Chromecast Lounge')
2018-07-12 04:05:28 WARNING (Thread-26) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-12 04:05:28 DEBUG (Thread-26) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-12 04:05:28 INFO bedroom_home -> 'unavailable'
2018-07-12 04:05:35 ERROR (Thread-26) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-12 04:05:41 DEBUG (Thread-26) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-12 04:05:41 INFO bedroom_home -> 'off'
2018-07-12 04:05:42 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.90', port=8009, uuid='5e2fc371-10e9-ea49-23b4-216a51072fc7', model_name='Google Home', friendly_name='Bedroom Home')
2018-07-12 04:51:47 WARNING (Thread-32) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-12 04:51:47 DEBUG (Thread-32) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-12 04:51:47 INFO bedroom -> 'unavailable'
2018-07-12 04:51:55 ERROR (Thread-32) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-12 04:52:00 DEBUG (Thread-32) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-12 04:52:00 INFO bedroom -> 'off'
2018-07-12 04:52:04 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.93', port=8009, uuid='b5fda076-4ba4-1565-9f3d-8f98ddfcb78c', model_name='Chromecast Audio', friendly_name='Bedroom')
2018-07-12 04:56:25 WARNING (Thread-25) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-12 04:56:25 DEBUG (Thread-25) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-12 04:56:25 INFO kitchen -> 'unavailable'
2018-07-12 04:56:39 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.92', port=8009, uuid='24ddbab5-3d2c-aebf-805c-e866fa3c2458', model_name='Chromecast Audio', friendly_name='Kitchen')
2018-07-12 04:56:41 DEBUG (Thread-25) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-12 04:56:41 INFO kitchen -> 'off'

Since switching to hassio I have the problem too:

Any news on this issue?

Still not working for me with the latest version :(

@OttoWinter @balloob - Is anyone actively working on this issue?  This has been broken for months.  I used to have automations to play music and announcements to certain groups.  But casting to groups is anything but reliable.  My logs are full of pychromecast failure to connect errors.  What can we do to help test/debug?

Yeah, absolutely nothing has changed since this was first reported (neither better nor worse). :(

I have a far from ideal workaround for triggering automations while casting to speaker groups.  I'm using the Unifi WAP component to monitor the bytes flowing to Chromecast Audio's.  If one spikes above 20000, then the amp supplying power to the speakers it feeds turns on.  There's usually a delay of 5-20 seconds given the polling frequency, but it's otherwise tolerable.  Also, if there are no spikes on any of the Chromecasts for 10 minutes, then the corresponding amp is (hopefully) turned off.   This is only for cast groups...casting to individual Chromecast Audio's is much more straightforward.  Also, to make this work, I had to convert all of the Chromecast Audio's from wired to wireless because the Unifi controller doesn't track bytes for wired devices.  I haven't noticed any issues going to wireless, but I'd really prefer to keep them wired.
While this is a passable work around, it is only about 60% effective.  The speakers always turn on, but only turn off after 10 minutes about half the time.  I haven't figured out why yet, so I have an automation that turns off all the amps at midnight.

Thanks, I'll check that out then. I like the idea of the broadcast not killing any music that was playing.
As since cast groups stopped working, I just listed out my cast devices within my script/automation as a work around for now.
alias: TTS Test
sequence:

data:
entity_id: media_player.basement_speakers, media_player.basement_assistant,
media_player.garage_assistant, media_player.pole_barn_assistant
volume_level: 0.6
service: media_player.volume_set
data:
entity_id: media_player.basement_speakers, media_player.basement_assistant,
media_player.garage_assistant, media_player.pole_barn_assistant
message: This is a test message. Is the volume loud enough?
service: tts.google_say

I too would like to know where things are at with this issue. I used to have automations fire when certain groups were playing etc. They've been useless for months.

Agree this is still an issue. Now I am even starting to get this with certain cast devices.

I have the same problem

Wish there was a way to vote on issues, this is such a pain, having to reboot HA nightly to keep Chromecast groups somewhat operational.

My server shuts down over night and starts up the next morning. The groups
are often already non-functional by the time I get home from work!
On Thu, Sep 20, 2018 at 11:01 AM joydashy notifications@github.com wrote:

Wish there was a way to vote on issues, this is such a pain, having to
reboot HA nightly to keep Chromecast groups somewhat operational.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/13530#issuecomment-423102075,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQNwbRzGtM6FyPjMn9UnszZ3-4qDxLq0ks5uc1l1gaJpZM4TADhw
.

My server shuts down over night and starts up the next morning. The groups are often already non-functional by the time I get home from work!
…
On Thu, Sep 20, 2018 at 11:01 AM joydashy @.***> wrote: Wish there was a way to vote on issues, this is such a pain, having to reboot HA nightly to keep Chromecast groups somewhat operational. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#13530 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AQNwbRzGtM6FyPjMn9UnszZ3-4qDxLq0ks5uc1l1gaJpZM4TADhw .

My HA also reboots when it needs to use Chromecast groups and detects they are Unavailable. This of course introduces a delay in the functionality. It's a sucky workaround!

Give 0.78.1 a try

Give 0.78.1 a try

Looks promising! Will update soon.

already on 0.78.1 and looks like it fixed my issue. got instances of unavailable issues on my 3 cast groups and they went from off to unavailable to off in seconds.

Updated to 0.78.1 yesterday evening.  This morning woke up to 2 of my 4 groups Unavailable... and one of my individual chromecast audios, as well.  Had to restart HA to re-connect to them.

I also still have the issues with 0.78.1.

Also still having the same problem with 0.78.1

@awarecan
Thanks for your help with this.  If you need anything in addition to what I've attached, please let me know.  I'd be glad to help any way I can in getting this resolved.
Here's my config:
# Chromecast Audios

  - platform: cast
    name: Den
    host: 192.168.85.130

  - platform: cast
    name: Kitchen
    host: 192.168.85.145

  - platform: cast
    name: Dining Room
    host: 192.168.85.146

  - platform: cast
    name: Living Room
    host: 192.168.85.144

  - platform: cast
    name: Patio
    host: 192.168.85.173

  - platform: cast
    name: Master Bedroom
    host: 192.168.85.142

  - platform: cast
    name: Master Bathroom
    host: 192.168.85.149

  - platform: cast
    name: Master Closet
    host: 192.168.85.147

  - platform: cast
    name: Playroom
    host: 192.168.85.141

  - platform: cast
    name: Office
    host: 192.168.85.143

  - platform: cast
    name: "Sloane's Speaker"
    host: 192.168.85.125

  - platform: cast

#Google Home
  - platform: cast
    name: Office Home
    host: 192.168.85.160

  - platform: cast
    name: Master Bedroom Home
    host: 192.168.85.115

  - platform: cast
    name: "Sloane's Alarm Clock"
    host: 192.168.85.205

  - platform: cast
    name: Kitchen Home
    host: 192.168.85.118

  - platform: cast
    name: Den Home
    host: 192.168.85.128

#Chromecast Videos
  - platform: cast
    name: Den Chromecast
    host: 192.168.85.100

  - platform: cast
    name: Den Shield
    host: 192.168.85.204

  - platform: cast
    name: Playroom Shield
    host: 192.168.85.203

And here's the output from logger with focus on logger:
home-assistant.log

I can also confirm that https://github.com/home-assistant/home-assistant/pull/16732 has not fixed this.
Which makes sense, as that fix refers to it being a problem for 15 days, but I have had this problem for much longer. Current issue is also much older.

@benjamin1492, 0.78.1 would not resolve your issue since you are configuring host IP address manually.
However, the #16786 may help to fix your problem, I rewrote the device connection logic for your case.

78.1 did not help me either.    It lasted about a day, but now I have both my group and my cast devices showing as unavailable.

I created a new PR #16804, not sure if it will help, but you can try.
#16786 caused more problem than fixed, I closed it.

0.78.3 - same problem - group unavailable

Running 0.78.3 this is my log when the cast group 'Home' got unavailable. The cast devices are setup by the discover feature, no IP component configuration:
018-09-24 13:00:48 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered chromecast ChromecastInfo(host='192.168.178.39', port=42673, uuid='a1883456-632f-4b0b-a2c6-fa6a246f1010', manufacturer='', model_name='Google Cast Group', friendly_name='Home') 2018-09-24 13:00:48 DEBUG (MainThread) [homeassistant.components.media_player.cast] Discovered chromecast with same UUID: ChromecastInfo(host='192.168.178.39', port=42673, uuid='a1883456-632f-4b0b-a2c6-fa6a246f1010', manufacturer='', model_name='Google Cast Group', friendly_name='Home') 2018-09-24 13:00:48 DEBUG (MainThread) [homeassistant.components.media_player.cast] Disconnecting from chromecast socket. 2018-09-24 13:00:48 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home, old_state=<state media_player.home=off; friendly_name=Home, supported_features=21437 @ 2018-09-24T08:56:49.289521+02:00>, new_state=<state media_player.home=unavailable; friendly_name=Home, supported_features=21437 @ 2018-09-24T13:00:48.276523+02:00>> 2018-09-24 13:00:49 DEBUG (Thread-15) [pychromecast.socket_client] Sending: Message urn:x-cast:com.google.cast.tp.connection from sender-0 to receiver-0: {'type': 'CLOSE', 'origin': {}} 2018-09-24 13:00:49 DEBUG (Thread-15) [pychromecast.socket_client] connection listener: 70432210 (CastStatusListener) 2018-09-24 13:00:49 DEBUG (Thread-15) [homeassistant.components.media_player.cast] Received cast device connection status: DISCONNECTED 2018-09-24 13:00:49 DEBUG (MainThread) [homeassistant.components.media_player.cast] Connecting to cast device ChromecastInfo(host='192.168.178.39', port=42673, uuid='a1883456-632f-4b0b-a2c6-fa6a246f1010', manufacturer='', model_name='Google Cast Group', friendly_name='Home')

@awarecan under new PR #16804 the groups still don't come back as per this issue.

Confirmed here, as well.

Since #16804 only addressed issue of start up hanging in manual configure scenario, rest logic reverted back to 0.77. So if you have group unavailable issue before, you still have it now.
I don't have "group" myself, so I won't be able to reproduce or debug that issue, so I am afraid I won't be able to help much.

@awarecan this is where you suggest people to buy you two Google Homes so you can create a group 👍

If a donation towards a Ghome Mini or so would help get this bug fixed, I'm in. This is by far my biggest issue with HA right now.

If a donation towards a Ghome Mini or so would help get this bug fixed, I'm in. This is by far my biggest issue with HA right now.

I would be in as well.

I'm in as well, but want to add my two cents on how to proceed.  As background, I have a very robust Google cast implementation:  10 Chromacast Audios, 4 Google Homes, an Insignia alarm clock, and a Sony speaker with Chromecast built-in.  Ever since Google updated the firmware in Nov-17, this has been a problem.  However, none of the Chromecast Built-in devices that remain on old firmware such as the Sony speaker or Insignia alarm clock are impacted.  My suggestion is that each of us willing to send equipment to awarecan for this project send something different:  a full size Google Home, a Google Home Mini, a Chromecast Audio, and at least 2 Chromecast built-in devices.  This would allow awarecan to build a variety of different groups to test the code - group of all built-ins, group of Google devices, and a mixed group.
This integration has been a graveyard for many a capable Home Assistant developer just because of it's overall complexity.  This approach will give us the best shot at finally getting this thing resolved.  I'd even be willing to throw a $100 bounty out there for a final fix, in addition in addition to a Google Home.
Awarecan:  You mission should you choose to accept it is to fix the Cast platform for good.  Shoot me an address and I'll get a Home en route.

I  have only one google home mini and it regularly (after a few hours) goes to unabailable until I restart HA. Is this the same issue or is this fixed with #16804?

Still having this issue on Home Assistant 0.79.3

@awarecan Is there anything we can do to help? Donations, devices, etc? I agree with most people here this desperately needs to be corrected once and for all and I know many of us are willing to help in anyway we can.

Dear, someone working on this problem ???

Same problem in Home Assistant 0.80.2

Yeah still experiencing this on 0.80.2

Has no one tried reverting whatever component changed back in March? Nothing has been fixed regarding this issue since it cropped up back then.

@j0barr this issue has nothing to do with any changes.  The issue has been present since day 1 of Google Cast Groups being available and integrated into HA.  It has to do with how the leader of the group (which is comprised of all the devices in the group) is elected.  If the leader changes (happens relatively frequent), the group goes unavailable.  You can see this with netdisco.  More than likely a dev will have to do a big rewrite in order to address this issue.

That's odd if nothing has changed because I swear it was working for me back with version 65.

You can easily revert back to that version and test.  Or set up a dev environment and only add the cast devices.  You will see that the groups go unavailable.  Trust me, I've been involved in this issue since day 1.

Issue goes back way further than that.  https://github.com/home-assistant/home-assistant/issues/7782 is when I first started tracking the problem.

Looked into this for a bit, going to see if the latest version of zeroconf would fix this. Zeroconf is used for pychromecast which is used for the Cast component.
Two fixes from their changelog interest me:
Switched from netifaces to ifaddr (pure Python)
ServiceBrowser entries are being refreshed when 'stale' now
https://github.com/jstasiak/python-zeroconf/blob/master/README.rst
The current version used by pychromecast is 0.17.7

@bryanyork Nope, that is unrelated. The issue is that when the cast group changes its elected leader we are currently not re-connecting to the new elected leader in the way the chromecast expects. We do get the callback from zeroconf that it has changed the leader. And we currently do try to disconnect from the old leader and re-connect to the new one. However, something in that process is behaving in a way that the chromecast doesn't expect, and though many hours of debugging I haven't been able to resolve the problem yet. This issue is particularly hard to diagnose because it just happens randomly every few hours, so if you test something you always have to wait that amount of time for the change to trigger again.

I've noticed that restarting HA always fixes this problem. What is it about restarting HA that causes this to be fixed, at least temporarily?
Is it possible we could make the software mimic whatever a reboot does to get around the issue?
I'd tried adding an automation to reboot if cast groups become unavailable but that became unreliable too as sometimes HA wouldn't come back,

I've noticed that restarting HA always fixes this problem. What is it about restarting HA that causes this to be fixed, at least temporarily?

I'm with Shadex12, a restart will fix it.  I was using cast groups as a alarm warning, but with them disappearing (going unavailable) I have temporaily reverted to a single speaker.
Can't add much to the discussion except to add my encouragement for a fix.

I am on Hassio 0.82.1 and my groups were also "unavailable" after some time in the middle of the night.

I have two groups. Each of them were "off" from 22:47 to 02:19. (2018.12.04)
Then they were "unavailable" from 02:19 to 03:08. (2018.12.05)
Then again they went to status "off" from 03:08 to 04.57. (2018.12.05)
Then they went unavailable until now: 04:57 to 22:04.

Logs on hassio:
https://paste.ubuntu.com/p/J6Nt3pSzH9/
If I can help in any way let me known.

Same issue here on HA 0.84.2.
Groups change to unavailable every other day and refuses to come back, restarting HA always does the trick.

Non here either (0.86.2)

I'm affected by the issue as well.
I'm looking for a workaround until the issue is resolved.
I've seen that restarting Home Assistant does solve the issue, so something is capable of healing this 'unavailable' status in HA.
Does anyone know how to reproduce this without a complete restart ?
My idea would be to create an automation which does something like:
If
no cast devices are running
and
at least 1 cast group is 'unavailable'
then
reload the chomecast integration (-> heal)
Any idea on which service/function to use ?

This should be fixed in beta 0.88.0b0
Please give it a try!
To provoke errors, try restarting casts that are members of an audio group, either through the Google Home app or by simply power cycling.
Note: It's normal that the group goes offline and comes back a few times as group leadership may be handed over several times if the restarted unit is the preferred group leader.
In case it's still not working, a complete HA log - from starting HA until group is no longer - is needed for debugging.
Logger options in configuration.yaml
logger:
  default: info
  logs:
    homeassistant.components.cast: debug
    homeassistant.components.cast.media_player: debug
    pychromecast: debug
    pychromecast.discovery: debug
    pychromecast.socket_client: debug
    zeroconf: debug

Hi,
I pulled Home assistant Dev 0.89 in a docker container (fresh config, host networking) and used discovery to autoconfigure my chromecasts and groups.
They are discovered but all 'unavailable'.
The attached log shows "Failed to connect" errors.
https://paste.ubuntu.com/p/4BRQ3hhQBC/

@masterz666 That should be fixed in beta 0.88.0b2

@emontnemery I'm on 0.88.0b0 since Thursday and didn't had this issue since then. Seems like it really fixed it (at least for me) 🎉
Thanks for you work! 👍

on 0.88b2 I sometime have this in the log. is this expected ?
 [Chromecast salon:8009] Heartbeat timeout, resetting connection

I don't want to jump the gun but I think the new pychromecast update may have solved this issue!  And mainly due to a experimental commit.  https://github.com/balloob/pychromecast/pull/268.  Crossing fingers but this is very promising!

@edif30, @soldag  Thanks for the feedback! balloob/pychromecast#268 is included in HA 0.88 via #21097 so I'll go ahead and close this issue.

@masterz666 The print means HA lost the connection to a chromecast. At least for me, chromecasts are not extremely stable and reboot now and then, so yes, I'd say its expected.

Does anyone on this thread have a Sony or Insignia speaker with Chromecast Built-in?  If so, have you noticed them causing any issues after updating to the new pychromecast?  The new version still isn't working for me, which I think makes me the exception based on the recent feedback.  I'm now trying to troubleshoot my cast install, and starting with the less common devices.

semi-unrelated:
@ttaidapos can you post your yaml for those media player cards that you posted pics of?
Thanks.

For what it's worth.  I'm on 88.2 and the group casting still going strong!  Still have a plethora of errors though.
Line 718: 2019-03-03 04:58:09 WARNING (Thread-12) [pychromecast.socket_client] [Baby display:8009] Heartbeat timeout, resetting connection 	Line 1807: 2019-03-04 02:01:09 WARNING (Thread-2) [pychromecast.socket_client] [Living Room Speaker:8009] Heartbeat timeout, resetting connection 	Line 1828: 2019-03-04 02:22:58 WARNING (Thread-7) [pychromecast.socket_client] [Office display:8009] Heartbeat timeout, resetting connection 	Line 1829: 2019-03-04 02:28:16 WARNING (Thread-9) [pychromecast.socket_client] [Kitchen Speaker:8009] Heartbeat timeout, resetting connection 	Line 1830: 2019-03-04 02:28:23 WARNING (Thread-6) [pychromecast.socket_client] [Bedroom Speaker:8009] Heartbeat timeout, resetting connection 	Line 1836: 2019-03-04 02:34:31 WARNING (Thread-15) [pychromecast.socket_client] [Bathroom Speaker:8009] Heartbeat timeout, resetting connection 	Line 1873: 2019-03-04 03:17:51 WARNING (Thread-12) [pychromecast.socket_client] [Baby display:8009] Heartbeat timeout, resetting connection 	Line 1894: 2019-03-04 03:42:43 WARNING (Thread-5) [pychromecast.socket_client] [Soundbar Speaker:8009] Heartbeat timeout, resetting connection 	Line 1944: 2019-03-04 04:36:27 WARNING (Thread-10) [pychromecast.socket_client] [Dining Room Speaker:8009] Heartbeat timeout, resetting connection 	Line 1988: 2019-03-04 05:26:33 WARNING (Thread-14) [pychromecast.socket_client] [Kitchen display:8009] Heartbeat timeout, resetting connection

semi-unrelated:
@ttaidapos can you post your yaml for those media player cards that you posted pics of?
Thanks.

It's a lot and I take no credit for it.  I have modified it the yaml a lot.  here it is and best of luck!
https://pastebin.com/RbWJVNhH

I lose cast groups still with 0.97.2...

authors: JIOB OttoWinter Roemer Shadex12 Spartan-II-117 Wonkavator accelle17 ajfriesen aliaghil allmoney awarecan backcountrymountains balloob benjamin1492 bryanyork darylsargent dshokouhi e1miran edif30 eeepsylon emontnemery fanaticDavid fillwe frankhommers gezonthenet grangemd harry19023 iorifly j0barr josephkiser04 joydashy kalkih kdjordjev kristoffernolgren masterz666 psfales rgruebel smoke007 soldag ttaidapos

repo: home-assistant/home-assistant


text:
0.67.0b1 - BT mac addresses get prefixed with double underscore in known_devices.yaml

Home Assistant release with the issue:

0.67.0b1
Last working Home Assistant release (if known):
Unknown
Operating environment (Hass.io/Docker/Windows/etc.):

Docker
Component/platform:

Bluetooth device tracker
Description of problem:
BT devices are getting a double underscore in the mac address in known_devices.yaml
mac: BT__00:11:22:AA:BB:CC
This causes an error as it thinks that the second underscore is part of the mac address
Correct mac address...
mac: BT_00:11:22:AA:BB:CC
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:
When removing the rogue underscore, or making any other changes in known_devices.yaml the device is rediscovered again, with a double underscore again

Confirming the same behaviour running 0.67b1 in hassio. When a device is added as a new one, it shows up in known_devices.yaml as:
my_iphone:
  hide_if_away: false
  icon:
  mac: BT__40:xx:xx:xx:xx:DB
  name: my iPhone
  picture:
  track: true

If I change my existing device but suffix BT with an extra _ the bluetooth device tracker gives the following error:
[homeassistant.components.device_tracker.bluetooth_tracker] Error looking up Bluetooth device
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/homeassistant/components/device_tracker/bluetooth_tracker.py", line 92, in update_bluetooth
    result = bluetooth.lookup_name(mac, timeout=5)
  File "/usr/lib/python3.6/site-packages/bluetooth/bluez.py", line 59, in lookup_name
    raise BluetoothError ("%s is not a valid Bluetooth address" % address)
bluetooth.btcommon.BluetoothError: _40:xx:xx:xx:xx:DB is not a valid Bluetooth address

Can, however confirm, that bluetooth tracker works if you delete your previously added BT-devices and let it recreate them in known_devices.yaml.

This issue is directly related to this PR: https://github.com/home-assistant/home-assistant/pull/12458

Appears to be working correctly again in 0.67.0


text:
Tap on slider on mobile triggers two state changes/events/messages

Home Assistant release with the issue:
v 0.78.3
Description of problem:
When using home assistant on a mobile (probably also on a tablet) tapping a slider, for example for brightness, triggers two times the same state change/event/message.
In my specific case I'm using MQTT and it results in 2x the same MQTT message being published.
When moving the slider and then releasing it only a single state change/event/message is created/sent.

This sounds like a frontend issue.

/move to home-assistant/home-assistant-polymer

authors: fabaff simonvanderveldt