-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] #23
Comments
Updated to 2023.7.1 |
I've never had this integration working before, but installed it today through HACS (HA 2023.7.1 Supervisor 2023.07.1, OS 10.3, Frontend 20230705.1 - latest) and get a similar issue. When configuring LEDFx integration I provide the IP address and port and it sets up with all my LEDFx devices. But when trying to control anything through the HA integration it gives an error "Failed to call service light/turn_on. connection lost". When clicking on the link from the LEDFx devices page it takes me to "192.168.52.10:8888/devices/tv-shelf", which gives a 404 error. The correct link would be "192.168.52.10:8888/#/device/tv-shelf" (with the hash in the middle of the link). Not sure if this is related to the problem. |
Until the author of the integration fixed the problem. I made the following crutch for myself. Since automation has been created for me to work with this integration, I had to raise a virtual machine, put XA version 2023.05 on it (integration works on this version). With the help of Remote Home-Assistant integration, I threw the necessary elements into the main system. By the way integration in version 2023.06 il 07 understands the meaning of sensors but cannot control them |
Also looking for a solution for this. |
Hello, do you know exactly how the URL changes when ledfx is on a pc and my HA instance is on a pi ? When I test the request on postman from my computer it works great, when I do it on HA via rest_command, nothing happens... |
Integration sees the device, but an error appears when trying to turn it on
"Не удалось вызвать службу light/turn_on. 'LedFxLight' object has no attribute '_ActionType.DEVICE_on'"
Please complete the following information:
The text was updated successfully, but these errors were encountered: