Have you tried seeing or googling whether you can enable/disable mDNS on your network router? I’m not experiencing this issue and you’re already participating in the github issue which will be more useful in pin pointing your specific troubleshooting requirements.
Yep, same with one of my thermometers.
1 Like
Do you know how to report this bug to devs? I do not.
I have found that many problems with chromecast is fixed by rebooting the chromecast device.
Go here https://home-assistant.io. Click “help”. Scroll down. There is a heading with the first word being “Bugs”. Just below that it refers you to the github issues trackers.
For me Alexa integration via custom skill is broken after 0.109,
reverting to 0.108.9 made alexa work again.
I’m getting “somethings wrong, enable/disable the skill via the alexa app”
even though the test in the lambda function is working properly.
Aexa working fine here with the skill as defined in the docs…
Just tested it, events are received:
Ereignis 3 ausgelöst 12:19:
{
"event_type": "hue_event",
"data": {
"id": "hue_smart_button_3",
"unique_id": "00:17:88:01:06:06:66:86-01-fc00",
"event": 1003,
"last_updated": "2020-05-04T10:19:31"
},
"origin": "LOCAL",
"time_fired": "2020-05-04T10:19:33.041845+00:00",
"context": {
"id": "b8cb6a3c8a724bbeb159d4a83b804573",
"parent_id": null,
"user_id": null
}
}
Ereignis 2 ausgelöst 12:19:
{
"event_type": "hue_event",
"data": {
"id": "hue_smart_button_3",
"unique_id": "00:17:88:01:06:06:66:86-01-fc00",
"event": 1001,
"last_updated": "2020-05-04T10:19:30"
},
"origin": "LOCAL",
"time_fired": "2020-05-04T10:19:31.061022+00:00",
"context": {
"id": "0ce8180a381d4009860ea508882c658f",
"parent_id": null,
"user_id": null
}
}
Ereignis 1 ausgelöst 12:19:
{
"event_type": "hue_event",
"data": {
"id": "hue_smart_button_3",
"unique_id": "00:17:88:01:06:06:66:86-01-fc00",
"event": 1002,
"last_updated": "2020-05-04T10:19:21"
},
"origin": "LOCAL",
"time_fired": "2020-05-04T10:19:23.039600+00:00",
"context": {
"id": "9739e31002674b7b922409da989e51bb",
"parent_id": null,
"user_id": null
}
}
Ereignis 0 ausgelöst 12:19:
{
"event_type": "hue_event",
"data": {
"id": "hue_smart_button_3",
"unique_id": "00:17:88:01:06:06:66:86-01-fc00",
"event": 1000,
"last_updated": "2020-05-04T10:19:21"
},
"origin": "LOCAL",
"time_fired": "2020-05-04T10:19:22.068114+00:00",
"context": {
"id": "2840622e76e3449ab5451c52f517b349",
"parent_id": null,
"user_id": null
}
}
Guess I’ll create a bug report.
Great! Please make sure the state mapping for that device is noted there (like, 1003 code is X, 1002 code is Y, …), and the model name (used to filter and show the triggers for each remote). I think it’s “Hue Smart button”, but I’m not sure. It is listed on the devices table, column “model”.
With that info, it should be very easy to add it to HA 
First, thanks a lot to all contributors: HA keeps on improving thanks to your hard work and dedication, thank you so much for that.
However, I have to lodge yet another complaint about the new weather card. Sorry, but this is really painful. See below the before and after situation, it says it all, this is not an improvement, apart from the debatable beauty of the icons (I don’t even mention the visibility issues raised by several users):
- I want to have more than three days of forecast
- I want the condition/state more prominent than the place name
- I want more info like wind speed/direction and humidity
- I want precipitation level per day in the forecasts
Thanks to seriously consider either adding an option to select the design, or to revert the changes, please.
2 Likes
I have already solved it, I post my solution in case it helps someone. Searching, I found a forum that said that there are routers that do not pass mDNS messages between the wired network and the wifi. My server is wired, and when connecting the server wifi, Cast devices reappeared. Anyway I will investigate in case it is a problem of my LAN configuration with fixed IP.
Thank you!
now , my second synology is now also discovered, i never configured it before, since i have 2factor auth enabled on that one, since its exposed to internet
does anyone know if now HA supports multi factor auth? i still see it as not supported on the docs page, allthough i remember a PR somwhere, that its now possible to use 2 factor, but cant find that PR anymore … maybe it was a PR in the python-synology library
Try to configure it and see if it works? 
no it doesnt, but maybe it needs to be done by config, with a manual line or something
ok, think i found the PR? seems its possible to use 
allthough the documentation says its still unsuported
confused …
edit: tested; 2FA is working, so docs pages are outdated
Sounds like a PR is in order eh? 
seems its being worked on
see here :
and
Here you go (quick prototype using new weather card, bar-card and a bit of markdowns). I also tried to recreate some other components used by weather-chart-card, succeeded partially. If you remove bars and current conditions section it will look mostly as you desire… drawback - it will always have 5 days of forecast, while stock weather card might change to 3…
cards:
- entity: weather.dark_sky
name: Zielonka
show_forecast: true
type: weather-forecast
- cards:
- cards:
- animation:
speed: 2
state: 'off'
color: var(--cyanish)
direction: up
entities:
- entity: sensor.dark_sky_daily_max_precip_intensity_0d
entity_row: true
height: 70
max: 2
name: ' '
positions:
icon: 'off'
indicator: 'off'
minmax: 'off'
name: 'off'
value: 'off'
type: 'custom:bar-card'
unit_of_measurement: mm
width: 20%
- content: >
<center>{{
(states('sensor.dark_sky_daily_max_precip_intensity_0d') | float
*24) | round(1)}} mm</center>
type: markdown
horizontal: false
type: 'custom:vertical-stack-in-card'
- cards:
- animation:
speed: 2
state: 'off'
color: var(--cyanish)
direction: up
entities:
- entity: sensor.dark_sky_daily_max_precip_intensity_1d
entity_row: true
height: 70
max: 2
name: ' '
positions:
icon: 'off'
indicator: 'off'
minmax: 'off'
name: 'off'
value: 'off'
type: 'custom:bar-card'
unit_of_measurement: mm
width: 20%
- content: >
<center>{{
(states('sensor.dark_sky_daily_max_precip_intensity_1d') | float
*24) | round(1)}} mm</center>
type: markdown
horizontal: false
type: 'custom:vertical-stack-in-card'
- cards:
- animation:
speed: 2
state: 'off'
color: var(--cyanish)
direction: up
entities:
- entity: sensor.dark_sky_daily_max_precip_intensity_2d
entity_row: true
height: 70
max: 2
name: ' '
positions:
icon: 'off'
indicator: 'off'
minmax: 'off'
name: 'off'
value: 'off'
type: 'custom:bar-card'
unit_of_measurement: mm
width: 20%
- content: >
<center>{{
(states('sensor.dark_sky_daily_max_precip_intensity_2d') | float
*24) | round(1)}} mm</center>
type: markdown
horizontal: false
type: 'custom:vertical-stack-in-card'
- cards:
- animation:
speed: 2
state: 'off'
color: var(--cyanish)
direction: up
entities:
- entity: sensor.dark_sky_daily_max_precip_intensity_3d
entity_row: true
height: 70
max: 2
name: ' '
positions:
icon: 'off'
indicator: 'off'
minmax: 'off'
name: 'off'
value: 'off'
type: 'custom:bar-card'
unit_of_measurement: mm
width: 20%
- content: >
<center>{{
(states('sensor.dark_sky_daily_max_precip_intensity_3d') | float
*24) | round(1)}} mm</center>
type: markdown
horizontal: false
type: 'custom:vertical-stack-in-card'
- cards:
- animation:
speed: 2
state: 'off'
color: var(--cyanish)
direction: up
entities:
- entity: sensor.dark_sky_daily_max_precip_intensity_4d
entity_row: true
height: 70
max: 2
name: ' '
positions:
icon: 'off'
indicator: 'off'
minmax: 'off'
name: 'off'
value: 'off'
type: 'custom:bar-card'
unit_of_measurement: mm
width: 20%
- content: >
<center>{{
(states('sensor.dark_sky_daily_max_precip_intensity_4d') | float
*24) | round(1)}} mm</center>
type: markdown
horizontal: false
type: 'custom:vertical-stack-in-card'
horizontal: true
type: 'custom:vertical-stack-in-card'
- type: divider
- cards:
- content: >
<ha-icon icon="mdi:water-percent"></ha-icon> {{
states('sensor.netatmo_pogodynka_ogrod_humidity') }} %
<ha-icon icon="mdi:gauge"></ha-icon> {{
states('sensor.netatmo_pogodynka_parter_pressure') }} mbar
type: markdown
- content: >
<ha-icon icon="mdi:weather-sunset-up"></ha-icon> {{
as_timestamp(strptime(states('sensor.dark_sky_sunrise_0d'),
'%Y-%m-%d')) | timestamp_custom('%H:%M') }}
<ha-icon icon="mdi:weather-sunset-down"></ha-icon> {{
as_timestamp(strptime(states('sensor.dark_sky_sunset_0d'),
'%Y-%m-%d')) | timestamp_custom('%H:%M') }}
type: markdown
- content: >
<ha-icon icon="mdi:water-percent"></ha-icon> {{
states('sensor.dark_sky_wind_bearing') }}
<ha-icon icon="mdi:gauge"></ha-icon> {{
states('sensor.dark_sky_wind_gust') }} m/s
type: markdown
horizontal: true
type: 'custom:vertical-stack-in-card'
type: 'custom:vertical-stack-in-card'
10 Likes
There are conflicting version dependencies between components aiohomekit and pyChromecast
The component aiohomekit has a dependency on zeroconf version 0.24.* (e.g. only 0.24.* “allowed”), while the component pyChromecast has a dependency on zeroconf >0.25.1.
So hopefully it is just a question of aiohomekit has not specified its dependecies “correctly”?!
1 Like
I’m surprised @nickrout . I did not know any of the integrations were editable after creation. I certainly have not discovered how to edit one, and I’ve been looking.