Can Confirm upgrading to 65.3 has resolved issue with Kodi
Have the same error too as below. Also ran into a 404: HTTP error on first restart due to some component not able to install. On second restart, all came back fine. Is the below error critical?
Building wheels for collected packages: aiohttp
Running setup.py bdist_wheel for aiohttp ... error
Complete output from command /srv/homeassistant/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-jpfysjo7/aiohttp/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /tmp/tmpqs7xcqk1pip-wheel- --python-tag cp35:
usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: -c --help [cmd1 cmd2 ...]
or: -c --help-commands
or: -c cmd --help
error: invalid command 'bdist_wheel'
----------------------------------------
Failed building wheel for aiohttp
Running setup.py clean for aiohttp
Failed to build aiohttpIt is entity_registry.yaml and not entities.yaml. Remove all the entries on Netatmo and you will be fine.
Iâve had html5 notifications fail on 65.3 - it said âplease set up the html5 platformâ
I rolled back to 64.3 and theyâre working again. Nothing else Iâve changed
Hi! Just updated Hassio to 0.65.3 and having issues in frontend.
I have duplicate switches panels. The switches themselves work fine, but their state is correctly shown only in one of the duplicate panels, e.g. I turn on smart plug, it shows as on in both panels briefly, then one of them reverts to off while the other shows on. Has anyone encountered anything like this?
Try just to reload the ui with F5
Lol, that really helped!
Funny thing is, I tried rebooting the system 2 times, tried looking though config.yaml for possible mistakes.
And somehow never thought about F5âŚ
Thanks!
you should file a bug if that is the case.
Yeelight not working properly after upgrade 0.65.3 able to off the bulb not able to on again.and duplicate bulb too.
But I donât have entity_registry.yaml on my config folder.
I just updated to 0.65.3 (from 0.63.3) and I encounter one major issue with Telegram Bot.
When I started a chat with my bot, it keep on triggering the same automation. This is what I have in my configâŚ
##########################################################
# Telegram Bot
##########################################################
telegram_bot:
- platform: webhooks
api_key: !secret telegram_api_key
allowed_chat_ids:
- !secret telegram_chat_id_user1
- !secret telegramgroup_chat_id
parse_mode: html
##########################################################
# Automation
##########################################################
automation:
- alias: 'Telebot Start'
initial_state: 'on'
trigger:
- platform: event
event_type: telegram_command
event_data:
command: '/jarvis'
- platform: event
event_type: telegram_command
event_data:
command: '/start'
- platform: event
event_type: telegram_text
event_data:
text: 'jarvis'
- platform: event
event_type: telegram_text
event_data:
text: 'Jarvis'
action:
- service: telegram_bot.send_message
data_template:
message: 'What do you want {{ trigger.event.data.from_first }}?'
title: ''
target: '{{ trigger.event.data.chat_id }}'
disable_notification: true
keyboard:
- "/alarm_clock, /timer"
- "/device_control, /device_status"
- "/send_message"
- "/tell_me, /show_me"
- "/control_security"
- "/lock_door, /unlock_door"
If I send jarvis to my bot, it will keep on replying âWhat do you want [my name]?â. Only way to stop this is to turn off automation.telebot_start via the Services page under Developer Tools. However, it will happen again after I restart HA.
Thanks. I guess I will move back to 0.63.3 until it is fixed.
After downgraded to 0.63.3, my xiaomi_aqara components no longer works. I lost all my sensors. I have no choice now but to re-update to 0.65.3. Between my sensors and Telegram bot, I guess it is better to keep the sensors. It is pity I have to sacrifice Telegram bot in order to update to 0.65.3. If I knew it, I would remain at 0.63.3. My advice to all who havenât update to 0.65 is DO NOT UPDATE if you are using Telegram Bot (webhooks method)!
Another thing about this version that I donât get it is the new component; Light Group. I have already grouped my lights using the âoldâ normal group feature and then I tried the new Light Group. I cannot find any benefits or difference between them. Both work exactly the same with the same speed. May I know in what scenario do we need to use this new group component? Will HA introduce similar group for other domains such as switch, fan, input_booleans, etc⌠Is it even necessary?
It works for me
Light group supports all the service operations for lights, but filter out parameters that are not suitable for a contained device.
Since the light group is within the Light domain, you can use itâs entity is everywhere a light eintity is possible
For example you can send a color change request to a light group and all capable lights will follow.
may i know which one are you referring to? xiaomi_aqara or telegram bot?
I donât have a group with mixture of lights with different capability (RGB and non RGB) to test but I have a group of RGB lights and it works exactly like how you describe it.
The telegram bot
Are you using platform: webhooks or platform: polling?
UPDATE: Anyway, I have tested with platform: polling and it works. I guess the issue is only with webhooks. I will now use polling for my Telegram bot for now.