zomfg / home-assistant-prismatik Goto Github PK

Started getting this error after updating Home Assistant to 0.110.0:

Source: components/light/__init__.py:451
Integration: Light (documentation, issues)
First occurred: May 20, 2020, 11:30:47 PM (2 occurrences)
Last logged: May 20, 2020, 11:31:09 PM

Light is deprecated, modify PrismatikLight to extend LightEntity

Thank you very much for your addon. Unfortunatly I cant get it to work.
Homeassistant Version: 2020.12.1
Prismatik Version: 6.0.0.104

`Logger: homeassistant.components.light
Source: helpers/entity_platform.py:231
Integration: Licht (documentation, issues)
First occurred: 7:38:06 (1 occurrences)
Last logged: 7:38:06

Setup of platform prismatik is taking longer than 60 seconds. Startup will proceed without waiting any longer.`

Homeassistant Config:
`light:

• platform: prismatik
  host: 192.168.178.59
  name: "Prismatik"
  profile_name: homeassistant`

Is there any way for prismatik to keep on screen grabbing after changing the brightness in home assistant. Personally I don't have any interest in setting my backlight in a single color. I just want to be able to adjust the brightness of my backlight with HA. Currently prismatik locks up after changing the brightness and it won't continue screen grabbing until switching from profile. Is there any way for prismatik to keep on screen grabbing after changing the brightness?

Hi,

I was wondering if it was possible to be able to get the list of profiles from prismatik and be able to change it in homeassistant.

thanks!

Hi @zomfg!
Thank you very much for this hass component and the good install tutorial!

I noticed that my prismatik instance icon randomly and regularly changes into a lock icon on the taskbar and the leds are "stuck" until i restart prismatik.
I think homeassistant updates / pings the prismatik instance or does something in the background (no automation is involved).
This is only comes up when the prismatik api socket is enabled.

Awesome integration. Thank you for this!

When I change a color in HA it stays on my screen for 60 seconds and then the LEDs go dark.

The profile is still saying hass so it's still locked, etc. I can manually switch it to my desktop one (Adalight) to re-gain my Screen Grabbing, or I can manually choose a color again in HA to re-engage the color. But basically it seems to turn off after 60 seconds.

Not sure if this is a bug, or a setting I can turn off? Or if a keep alive feature could be added?

Hi,
first of all thanks for the great integration, works great for me!
I installed the integration manually for now but it would be great if you could change the repo structure so it can be installed using hacs (home assistant community store). There really is not much to do except for some change in folder structure I think, but then we could easily auto install it and also auto-update using hacs. Here is the list of repos so you may look into the structure it takes: https://hacs.xyz/docs/default_repositories
An option would be even to add this to the default hacs repos: https://hacs.xyz/docs/publish/start

Привет не знаю как еще связаться) Я видел в репе по яндекс станции твое ишью касательно кондиционера daichi, там ты написал что добавил его в HA
Как ты его добавлял?)
можешь на почту ответить? [email protected]

hassio last version

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 231, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/prismatik/light.py", line 65, in async_setup_platform
await light.async_update()
File "/config/custom_components/prismatik/light.py", line 300, in async_update
profiles = await self._get_cmd(PrismatikAPI.CMD_GET_PROFILES)
File "/config/custom_components/prismatik/light.py", line 222, in _get_cmd
answer = await self._send(f"get{cmd}\n")
File "/config/custom_components/prismatik/light.py", line 198, in _send
answer = data.decode("ascii").strip()
UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 48: ordinal not in range(128)

Error message:

Logger: homeassistant.components.light
Source: helpers/entity_platform.py:224
Integration: Light (documentation, issues)
First occurred: 13:57:20 (1 occurrences)
Last logged: 13:57:20

Setup of platform prismatik is taking longer than 60 seconds. Startup will proceed without waiting any longer.

I have tried reinstalling it.

2022-10-02 13:57:16.555 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: light.prismatik
2022-10-02 13:57:20.984 ERROR (MainThread) [homeassistant.components.light] Setup of platform prismatik is taking longer than 60 seconds. Startup will proceed without waiting any longer.
2022-10-02 14:07:55.128 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.prismatik is taking over 10 seconds
2022-10-02 14:08:15.128 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:08:45.129 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:09:15.130 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:09:45.131 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:10:15.132 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:10:45.133 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:11:15.140 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:11:45.140 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:12:15.141 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:12:45.143 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:13:15.145 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:13:45.146 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:14:15.147 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:14:45.148 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:15:15.148 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:15:45.150 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:16:15.150 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:16:45.151 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:17:15.152 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:17:45.153 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:18:15.155 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:18:55.156 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.prismatik is taking over 10 seconds
2022-10-02 14:19:15.157 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:19:45.158 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:20:15.158 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:20:45.159 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:21:15.160 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:21:45.161 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30
2022-10-02 14:22:15.162 WARNING (MainThread) [homeassistant.components.light] Updating prismatik light took longer than the scheduled update interval 0:00:30

Bug Description

When I turn on the prismatik using the home assistant UI I get the following error:

Failed to call service light/turn_on. 'NoneType' object is not subscriptable
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 125, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1265, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1300, in _execute_service
await handler.func(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 208, in handle_service
await self.hass.helpers.service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 471, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 277, in async_update_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 316, in _async_write_ha_state
attr.update(self.state_attributes or {})
File "/usr/src/homeassistant/homeassistant/components/light/init.py", line 426, in state_attributes
data[ATTR_HS_COLOR] = (round(hs_color[0], 3), round(hs_color[1], 3))
TypeError: 'NoneType' object is not subscriptable

The lightpack turns on normally and the state in home assistant briefly changes to on, then reverts to off. If I then try to turn the lightpack on/off I get the following error:

Could not lock prismatik

If I am persistent in mashing the button it will eventually turn off and the bug will reoccur

Enviroment Description

Home Assistant 0.113.1
Prismatik Version 5.11.2.23
WLED version 0.10.0 (Configured as UDP DRGB in prismatik)
Windows 10 1909

Thank's for all your work on Prismatik and this component for Home Assitant ❤️

Entity None (<class 'custom_components.prismatik.light.PrismatikLight'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <LightEntityFeature.EFFECT|17: 21> and color modes, please report it to the author of the 'prismatik' custom integration and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation

What is the purpose of this integration? I installed plugin. However I can't define how to map lights in HA ? I suspected that HA query Prismatic and get the color data. I can see the changes in Prismatic entity in HA. Am I wrong about it?