Wunderground raises error:
2018-03-09 21:32:07 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up platform wunderground Traceback (most recent call last): File “/srv/ha/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py”, line 82, in async_setup SLOW_SETUP_MAX_WAIT, loop=hass.loop) File “/usr/lib/python3.6/asyncio/tasks.py”, line 358, in wait_for return fut.result() File “/usr/lib/python3.6/asyncio/futures.py”, line 245, in result raise self._exception File “/usr/lib/python3.6/asyncio/tasks.py”, line 180, in _step result = coro.send(None) File “/srv/ha/lib/python3.6/site-packages/homeassistant/components/sensor/wunderground.py”, line 647, in async_setup_platform yield from rest.async_update() File “/usr/lib/python3.6/asyncio/coroutines.py”, line 213, in coro res = yield from res File “/srv/ha/lib/python3.6/site-packages/homeassistant/components/sensor/wunderground.py”, line 787, in async_update result = yield from response.json() TypeError: cannot ‘yield from’ a coroutine object in a non-coroutine generator
2018-03-09 21:38:55 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/remote.py", line 127, in default
return json.JSONEncoder.default(self, o)
File "/usr/local/lib/python3.6/json/encoder.py", line 180, in default
o.__class__.__name__)
TypeError: Object of type 'Decimal' is not JSON serializable
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/remote.py", line 133, in default
for child_obj in o]
TypeError: 'decimal.Decimal' object is not iterable
and
2018-03-09 21:40:47 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/websocket_api.py", line 331, in handle
msg = await wsock.receive_json()
File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_ws.py", line 397, in receive_json
data = await self.receive_str(timeout=timeout)
File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_ws.py", line 381, in receive_str
msg = await self.receive(timeout)
File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_ws.py", line 345, in receive
msg = await self._reader.read()
File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/streams.py", line 571, in read
return await super().read()
File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/streams.py", line 533, in read
await self._waiter
File "/usr/local/lib/python3.6/asyncio/futures.py", line 327, in __iter__
yield self # This tells Task to wait for completion.
File "/usr/local/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
future.result()
File "/usr/local/lib/python3.6/asyncio/futures.py", line 238, in result
raise CancelledError
concurrent.futures._base.CancelledError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 381, in start
resp = await self._request_handler(request)
File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_app.py", line 310, in _handle
resp = await handler(request)
File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_middlewares.py", line 88, in impl
return await handler(request)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/static.py", line 68, in staticresource_middleware
return await handler(request)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/real_ip.py", line 27, in real_ip_middleware
return await handler(request)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/ban.py", line 68, in ban_middleware
return await handler(request)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/auth.py", line 52, in auth_middleware
return await handler(request)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/view.py", line 100, in handle
result = await result
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/websocket_api.py", line 210, in get
return await ActiveConnection(request.app['hass'], request).handle()
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/websocket_api.py", line 393, in handle
await self._writer_task
File "/usr/local/lib/python3.6/asyncio/futures.py", line 329, in __iter__
return self.result() # May raise too.
File "/usr/local/lib/python3.6/asyncio/futures.py", line 243, in result
raise self._exception
File "/usr/local/lib/python3.6/asyncio/tasks.py", line 180, in _step
result = coro.send(None)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/websocket_api.py", line 243, in _writer
await self.wsock.send_json(message, dumps=JSON_DUMP)
File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_ws.py", line 263, in send_json
await self.send_str(dumps(data), compress=compress)
File "/usr/local/lib/python3.6/json/__init__.py", line 238, in dumps
**kw).encode(obj)
File "/usr/local/lib/python3.6/json/encoder.py", line 199, in encode
chunks = self.iterencode(o, _one_shot=True)
File "/usr/local/lib/python3.6/json/encoder.py", line 257, in iterencode
return _iterencode(o, 0)
File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/remote.py", line 136, in default
return json.JSONEncoder.default(self, o)
File "/usr/local/lib/python3.6/json/encoder.py", line 180, in default
o.__class__.__name__)
TypeError: Object of type 'Decimal' is not JSON serializable
2018-03-09 21:45:25 ERROR (MainThread) [homeassistant.components.websocket_api] WS 1576122704: Client exceeded max pending messages [2]: 512
Thanks, it look likes it has something to do with that pull. i have linked my issue and logging in the pull request. hoping on a soon release. ios app isn’t working all anymore.
seems to be happening in normal browser also. Can’t open any more. same errors.
downgraded to 0.64.3 and everything is working again. seems to be a huge bug in 0.65.
Tried upgrading 3 times. confirms 0.65 installation, completes configuration check, and then restart. nothing afterwards. No errors, no frontend loading. System is running because I can operate via dashboard, but nothing on the homeassitant frontend.
It looks like there is a state that is storing a Decimal in the state machine. The linked issue is not your issue. Are you using the SQL sensor ? Could you check your startup logs to see if there any other errors and open an issue for that?
I question the decision to set the minimum version to 3.5.3, with the current ubuntu LTS only distributing 3.5.2 is there a technical reason for 3.5.3 or was it just chosen
Just looked through the PR, noticed that it was becuse you decided to go with what debian stable had. Going to have to hold off on this update until the Ubuntu Repos update or when 18.04 is released(the more likley option because of how close it is, Ubuntu wont bother to update repos during this period)
3.5.3 comes with https://bugs.python.org/issue28613 which is a big improvement for asyncio. Also, Ubuntu LTS is like 2 years old but have a PPA available to add a newer Python if necessary.
Yes, checking the ones at the top of google, they all seem to only package the interpreter not pip or any of the python tools needed to install home assistant
I have upgrade to 0.65
google_assistant at entity_config not support type: anymore therefore, many of input_boolean that I use to put type: switch end up with config error. Cannot turn on/off input_boolean anymore.
If this configuration part is in HA side. Please support the type: to be usable in entity_config for google_assitant.
You’re approaching this the wrong way. type is a hack and should never have been added. Just because something works doesn’t mean it should be part of Home Assistant. Instead, normal support for input boolean by the OnOff trait should be added which I did here: https://github.com/home-assistant/home-assistant/pull/13030
I’m noticing an issue - I’m missing states and other menus on the left only when I enable an http password for HASS. Running on Ubuntu 17.10 with python 3.6. HASS 0.65 - if I disable the http password - all goes to normal.
tts.google_say doesn’t work:
Error executing service
Traceback (most recent call last):
File “/usr/lib/python3.6/site-packages/homeassistant/core.py”, line 1010, in _event_to_service_call
yield from service_handler.func(service_call)
File “/usr/lib/python3.6/site-packages/homeassistant/components/media_player/init.py”, line 402, in async_service_handler
yield from getattr(player, method[‘method’])(**params)
File “/usr/lib/python3.6/asyncio/futures.py”, line 332, in iter
yield self # This tells Task to wait for completion.
File “/usr/lib/python3.6/asyncio/tasks.py”, line 250, in _wakeup
future.result()
File “/usr/lib/python3.6/asyncio/futures.py”, line 245, in result
raise self._exception
File “/usr/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/lib/python3.6/site-packages/homeassistant/components/media_player/init.py”, line 693, in play_media
raise NotImplementedError()
NotImplementedError
Is there a possibility to also return the sensor domain into traits for thermostatTemperatureAmbient and thermostatHumidityAmbient usage for sensors? The pre 0.65 required mapping the entity to climate type however that has been removed.
We can’t. Implementing a Google Assistant trait means you implement all corresponding commands too. There are new traits being added all the time and we will add support as they come out. I wouldn’t be surprised if a sensor trait was on its way. With the new architecture this should be very straightforward to add.
Have you tried setting up a Generic Climate component with your sensor and a placeholder switch? That should work, but I’m not sure and can’t test at the moment.
Im staying on 0.64.3 for the time being as I have a fair about of sensors already exposed for temp and humidity. I’ll have a read up on generic climate but I feel like it will be alot of work arounds to acheive it, perhaps a custom component just to expose sensors with temp and humidity.
edit: Just had a quick read and it might be possible to do a generic per room with a dummy switch as you said. One consideration though is that it only seems to use a single temp sensor. Would be nice to use both a temp and humidity sensor as targets to a single generic thermostat. I might give it a go later.
Good day, I removed the sql sensor, updated to 65.1 and it worked. no errors. I then added the sensor back restarted and got this: “2018-03-10 09:48:49 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: Object of type ‘Decimal’ is not JSON serializable” and the frontend would not load. removed the sensor again, restarted and all fine.
2018-03-10 16:35:08 ERROR (MainThread) [homeassistant.components.remote] Error while setting up platform xiaomi_miio
Traceback (most recent call last):
File “/usr/src/app/homeassistant/helpers/entity_platform.py”, line 82, in async_setup
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/local/lib/python3.6/asyncio/tasks.py”, line 358, in wait_for
return fut.result()
File “/usr/local/lib/python3.6/asyncio/futures.py”, line 243, in result
raise self._exception
File “/usr/local/lib/python3.6/asyncio/tasks.py”, line 180, in _step
result = coro.send(None)
File “/usr/local/lib/python3.6/asyncio/coroutines.py”, line 212, in coro
res = func(*args, **kw)
File “/usr/src/app/homeassistant/components/remote/xiaomi_miio.py”, line 77, in async_setup_platform
device = ChuangmiIr(host, token, lazy_discover=False)
TypeError: init() got an unexpected keyword argument ‘lazy_discover’
I have same issue. wunderground is broken…
OK: I figured it out… just get new fixed files from “dev” branch on homeassisant git and replace below files:
The same bug affects about 10 other sensors, so just replace the “init.py” and “your broken sensor.py”
until they merge “dev” branch into main and issue an update to HA.
Waiting for the Docker RPi3 image to be updated to 0.65.1. How long does this usually take compared to the „standard“ image homeassistant/home-assistant?
I have a similar issue with SabNZB sensor component. Was working fine in 0.65, and have updated to 0.65.1, but the issue is still there, though Wunderground is working again.
2018-03-11 00:32:21 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up platform sabnzbd
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity_platform.py", line 82, in async_setup
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File "/usr/lib/python3.5/asyncio/tasks.py", line 400, in wait_for
return fut.result()
File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
raise self._exception
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/sensor/sabnzbd.py", line 152, in async_setup_platform
if not (yield from async_check_sabnzbd(SabnzbdApi, base_url, api_key)):
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/sensor/sabnzbd.py", line 62, in async_check_sabnzbd
yield from sab_api.check_available()
File "/srv/homeassistant/lib/python3.5/site-packages/pysabnzbd/__init__.py", line 43, in check_available
with aiohttp.ClientSession() as session:
File "/srv/homeassistant/lib/python3.5/site-packages/aiohttp/client.py", line 742, in __enter__
raise TypeError("Use async with instead")
TypeError: Use async with instead
Also, another error I have that has popped up since 0.65 is the following. No idea what it’s about.
@cjsimmons Thanks for the sanity check! I have definitely confirmed that removing the http password fixes the issue.
@DavidFW1960 - I’ve tried it on 2 win 10 machines with both chrome and edge - same issue - also showing same from android phone as well.
Edit: Just installed 65.1 - no help with http password and menus so far.
Ok - another oddity around this - removed http password so it would go back to normal until this is sorted out. Checked with Chrome from Win 10 laptop - all is fine. No password - menu looks good.
Check from same laptop with IE 11 (not edge) - get password prompt (which I confirmed in chrome was off and double checked config file in HASS). Menu is now messed up in IE just like Chrome when password is enabled. Cleared IE cache - no difference. Refresh page again - no password prompt now (no changes made in HASS) - but menu is still messed up. Edge however on same latptop shows ok and no password prompt when I access HASS.
Also - the screenshot/gif shown in the post for changing the light name does not appear to be working for me (at least so far) - my 65.1 instance is on a test box with one yeelight it discovered via wifi, I can turn on.off/change my yeelight with this HASS instance. However - I don’t see the cog wheel when I click on the light to be able to change the name, Am I missing something or is this just because the yeelight isn’t supported for the name change from the front end or something along those lines?
One question, I’m running hass on synology container in docker. Before upgrade it used to use about 700MB of ram, but after upgrade to 0.65.1 it uses over 2GB of RAM! I cleaned container couple times it didn’t help. Anybody noticed that?
I am also trying to upgrade python from 3.5.2 (default Ubuntu) to 3.5.5 but can’t figure out. Tried using PPA no luck it says it has already.
If someone can provide step by step details for Ubuntu 16.04 LTS how to do this will help a lot many people like me.
If I figure out will update this post with the steps.
Thansk
The same basic process applies - build Python from source, and install it. Then call the new version explicitly (eg python36 rather than just python3).
That’s the point of LTS, having a stable environment for server usage.
16.04LTS is still supported and well updated.
There should be a LTS soon (18.04 announced on Apr 26th) and this is the way to go for users having an LTS, not adding other packages from external sources.
People using LTS and sticking to it, including me, do that on purpose. I have other services on other VMs with 17.10, but Home Assistant is controling my home, some security devices, I don’t want the system to be a risk.
So I posted an issue earlier about my iOS device tracker setting my status as not_home. I thought it was only in the iOS app, but seems to be happening in Safari too. Also, the pull out menu items on the left are lower case, and some are missing entirely.
If I refresh the iOS app or Safari, it fixes it temporarily until it times outs.
Appreciate it.
I will try and see how it goes because I have Home Assistant running with ssl using letsencrypt certificate so I will have to see anything else I will have to do.
Thanks a lot.
2018-03-11 14:41:32 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.cast
2018-03-11 14:41:32 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.ps4
2018-03-11 14:41:32 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.vlc
2018-03-11 14:41:33 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.cast
2018-03-11 14:41:33 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.lg_netcast
2018-03-11 14:41:35 WARNING (MainThread) [homeassistant.components.media_player.cast] Can’t set up chromecast on 192.168.1.35: Could not connect to 192.168.1.35:8009
2018-03-11 14:41:35 WARNING (MainThread) [homeassistant.components.media_player] Platform cast not ready yet. Retrying in 30 seconds.
nothing wrong in the logs. OMG. I restart 4 times then come back.
Hi
Having issues with kodi after upgrading to v65
tried 65.1.and 65.2 still same issue
Returned to 64.3 and no issue.
logs below
Sun Mar 11 2018 17:44:53 GMT+1000 (E. Australia Standard Time)
kodi: Error on device update!
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/jsonrpc_websocket/jsonrpc.py”, line 117, in wait
yield from self._event.wait()
File “/usr/local/lib/python3.6/asyncio/locks.py”, line 271, in wait
yield from fut
File “/usr/local/lib/python3.6/asyncio/futures.py”, line 327, in iter
yield self # This tells Task to wait for completion.
File “/usr/local/lib/python3.6/asyncio/tasks.py”, line 250, in _wakeup
future.result()
File “/usr/local/lib/python3.6/asyncio/futures.py”, line 238, in result
raise CancelledError
concurrent.futures._base.CancelledError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “/usr/local/lib/python3.6/site-packages/jsonrpc_websocket/jsonrpc.py”, line 42, in send_message
response = yield from pending_message.wait(self._timeout)
File “/usr/local/lib/python3.6/site-packages/jsonrpc_websocket/jsonrpc.py”, line 118, in wait
return self._response
File “/usr/local/lib/python3.6/site-packages/async_timeout/init.py”, line 35, in exit
self._do_exit(exc_type)
File “/usr/local/lib/python3.6/site-packages/async_timeout/init.py”, line 80, in _do_exit
raise asyncio.TimeoutError
concurrent.futures._base.TimeoutError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “/usr/src/app/homeassistant/helpers/entity_platform.py”, line 188, in _async_add_entity
await entity.async_device_update(warning=False)
File “/usr/src/app/homeassistant/helpers/entity.py”, line 325, in async_device_update
yield from self.async_update()
File “/usr/src/app/homeassistant/components/media_player/kodi.py”, line 440, in async_update
‘albumartist’, ‘showtitle’, ‘album’, ‘season’, ‘episode’]
File “/usr/local/lib/python3.6/site-packages/jsonrpc_websocket/jsonrpc.py”, line 48, in send_message
raise TransportError(‘Transport Error’, message, exc)
jsonrpc_base.jsonrpc.TransportError: (“Error calling method ‘Player.GetItem’: Transport Error”, TimeoutError())
I’m also slightly annoyed about this decision because the latest LTS version of a major distribution is likely to be widely used for those who care about stability, but I recognise that I can’t expect anyone else to not keep progressing because of my choices.
Hi, are here someone with Netatmo Weather Station or Camera and dont they have any double entities?
I have double entities from the beginning of HA version 0.63. Now I am on ver 0.65 and still have double entities.
Also I dont have entities.yaml file in my config directory. Should it be generated by HA automatically?
How do I fix this?
Something has changed in google_assistant after latest release ?? Getting the following error
- Invalid config for [google_assistant]: [type] is an invalid option for [google_assistant]. Check: google_assistant->google_assistant->entity_config->sensor.temperature_158d0001fa985e->type. (See /config/configuration.yaml, line 116). Please check the docs at https://home-assistant.io/components/google_assistant/
Code it refers to
google_assistant:
project_id: PROJECT
client_id: ID
access_token: TOKEN
agent_user_id: [email protected]
api_key: KEY
exposed_domains:
- switch
- light
- group
- climate
entity_config:
sensor.temperature_158d0001fa985e:
type: climate
expose: true
name: Living Room
EDIT: I guess its a breaking change its referring to?
Google Assistant integration: It is no longer possible to override the domain that Home Assistant uses for an entity. This was bound to go wrong when we would test supported features for different domains. Also removed support for disguising temperature sensors as thermostats. We should follow the traits that Google offer us and not offer things that will only work half. (@balloob - #12959) (google_assistant docs) (light docs) (breaking change)
How can we get around it or what do I need to change it to?
Yeah it does… I removed the line in exposed_domain and commented out the entire entity_config and HA comes back up… Should I just remove the “type: climate” line and will google still be able to tell me temperature? Is that still achievable?
Can anyone confirm of using input_boolean with google_assistant project is still available. I get error cannot connect like Mr. its when he put type: climate in entity_config.
For those looking for a Ubuntu solution I tried a clean install of 16.04 LTS in a LXC container with a PPA install of Python 3.6. Creation of a python virtual environment failed and a regular HA install required any additional python packages to be installed manually with pip. However, I still could not fix all my issue so I tried out 17.10 which worked flawlessly. I am running HA isolated on my home lab with a LXC container in Proxmox so this decision does not impact anything else. However, it seems odd for people to worry about running 17.10 vs. 16.04 LTS when HA is 0.x, you stability is going to be more at risk with HA than a non LTS ubuntu release.
i am still on 0.65 experiencing the known issues (weatherunderground and so on) but i still don`t have the update to 0.65.2 available in hassio. Is this normal ? What can i do to check if there is an issue with the update process?
It is normal. The images have to be built before they are available. I see 0.65.1 is available now, but now 0.65.3 is out so probably need to wait a bit longer im afraid. Or build it yourself
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 aiohttp
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?
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!
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.
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?
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.
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.
It sucks a bit sometimes when something changes but I find it best just to suck it up and embrace the change and use the ‘new’ way. That way, if something changes down the track, you won’t suddenly find something is totally broken that you forgot about. This is one of the reasons I abandoned using my all-in-one install as it was depreciated and that’s just a recipe for grief down the road. (Like when python changes become mandatory for instance)
