Closed DivanX10 closed 2 years ago
I have not tested it with the add-on. mk don't use it. the feedback is fine and is configurable with a timeout, as you can see from the readme. I can only suspect that it does not work in the addon, but send a log for that? + which version of ledfx are you using ?, only one is currently supported. if there are no messages in the log, enable the debug mode and send it too. And making separate requests for each switch is not good, I have a very bad effect on the system and the ledfx instance itself.
0.10.7 is only supported. update. if it does not work, you need logs.
Do I understand correctly that the debug log needs to be included in the config? If true, then I will collect and send the logs, but I can't pull the logs out of the Led FX itself.
logger:
default: fatal
logs:
homeassistant.components.ledfx: debug
Do I understand correctly that the debug log needs to be included in the config? If true, then I will collect and send the logs, but I can't pull the logs out of the Led FX itself.
from ledfx it is not necessary, it is necessary from home assistant.
I have an assumption that there is no return due to the fact that an error occurs. Perhaps it is related to the version.
Would you be able to install the LedFX addon in your Home Assistant and connect to it through your LedFX integration? This will make it easier for you to localize the problem.
In the Led FX addon, Led FX v0.10.7 is installed, your integration works fine with Led FX v 0.10.5 if the Led FX v 0.10.5 server is on Windows \Ubuntu Server 20.04 LTS. Problem with access to the Led FX addon
The Led FX addon is here
Add a repository to the addon store
https://github.com/hassio-addons
try updating ledfx. I see from the text that the wrong json has arrived
Specify whether to update the Led FX addon or the integration itself? If we are talking about the LedFX addon, then the addon is fresh. There, as I understand it, the integration simply does not have access to the internal address 127.0.0.1:8888, since the web interface works on a different address and a different port and it turns out that your LedFX integration physically cannot connect to 127.0.0.1:8888
That's why I suggest you install the LedFX addon yourself and personally check everything yourself and if it works for you, then write what and how you did it
I found the problem. The problem turns out to be in the settings of the addon itself. It remains to understand how to fix it and who will fix it
When a bridge is specified in the addon, the Led FX integration cannot connect to the addon
When the host is specified in the addon, the Led FX integration can connect to the addon
translator have you tried to register not 127.0.0.1:8888 but 192.168.1.86:5333?
Recorded on video, I think it will be clear
magic. and it is possible to log from Hass after all attempts of different authorizations?
I'm afraid of course that this is a network problem. but it would be interesting to understand.
Tell me, how is it better to write in Russian or in English? By nickname you are Russian )
I looked at the addon now and you are right, you really need to edit the addon (
OK, then I went to the author of the Led FX addon)
the problem is not the addon is not running on host network but that ledfx is running behind revers proxy and force you to login if you like to access the addon backend
Tell me, how is it better to write in Russian or in English? By nickname you are Russian )
Text in English Текст на русском (Text in Russian)
@dmamontov
could you take this into account and refine your integration so that you can connect to the Led FX addon? My control has started working. Read here
The question is removed. Closing the topic. In the latest version of the Led FX addon, you can now turn off authorization and thanks to this, you can now use LedFX integration.
In the settings of the Led FX addon, add the line leave_front_door_open: true
certfile: fullchain.pem
keyfile: privkey.pem
ssl: false
leave_front_door_open: true
In the Led FX integration settings, we specify
IP adress: localhost
Port: 5333
OS: Home Assistant OS 7.0 Core: 2021.12.2 Supervisor: 2021.12.2 Led FX addon: ledfx Current version: 7d13080
Thank you for your integration, but there are problems with it
1) It is not possible to connect to the Led FX addon 2) The buttons have no feedback (I decided this in my own way and the answer is below)
About the Led FX addon
This integration can easily connect to the Led FX server that runs on Windows \ Ubuntu Server 20.04 LTS, but it cannot connect to the LedFX addon on Home Assistant and, accordingly, I cannot control the scenes. I created issues here
About switches
I can choose scenes through lighting, but in the integration there are also switches for turning on scenes and they just turn on any scene and do not show the real status. I made switches for myself that show the real status of the selected scene. Can you add feedback to your integration to turn scenes on and off?
Here I have described everything in detail what and how I did it. This works if Led FX is on Windows \ Ubuntu Server 20.04 LTS,
In the case of Windows \ Ubuntu Server 20.04 LTS, all this works fine, I attach videos \ screenshots and the code itself for the feedback switches
Screenshots
![image](https://user-images.githubusercontent.com/64090632/146368285-b320e5f7-fa00-4402-ad99-19e3add8cae5.png) ![image](https://user-images.githubusercontent.com/64090632/146368776-8e027151-a78d-4569-9799-34ee268ad734.png) ![image](https://user-images.githubusercontent.com/64090632/146368848-32b0913f-a340-4394-9794-6df86539f88b.png) ![image](https://user-images.githubusercontent.com/64090632/146369585-88f96eef-9a80-4e90-83bc-b956443ea30f.png)Switches - code
``` switch: - platform: command_line switches: ledfx_scene_visualiser_blade_power: friendly_name: "LedFX Visualiser BladePower" command_timeout : 10 icon_template: mdi:music command_on: curl -L -X PUT 'http://192.168.5.27:8888/api/scenes' --data-raw '{"id":"blade-power","action":"activate"}' command_off: curl -L -X PUT 'http://192.168.5.27:8888/api/scenes' --data-raw '{"id":"music-off","action":"activate"}' command_state: curl -X GET 'http://192.168.5.27:8888/api/devices' | grep 'blade_power(Reactive)' - platform: command_line switches: ledfx_scene_visualiser_bands: friendly_name: "LedFX Visualiser Bands" command_timeout : 10 icon_template: mdi:music command_on: curl -L -X PUT 'http://192.168.5.27:8888/api/scenes' --data-raw '{"id":"bands","action":"activate"}' command_off: curl -L -X PUT 'http://192.168.5.27:8888/api/scenes' --data-raw '{"id":"music-off","action":"activate"}' command_state: curl -X GET 'http://192.168.5.27:8888/api/devices' | grep 'bands(Reactive)' - platform: command_line switches: ledfx_scene_visualiser_energy: friendly_name: "LedFX Visualiser Energy" command_timeout : 10 icon_template: mdi:music command_on: curl -L -X PUT 'http://192.168.5.27:8888/api/scenes' --data-raw '{"id":"energy","action":"activate"}' command_off: curl -L -X PUT 'http://192.168.5.27:8888/api/scenes' --data-raw '{"id":"music-off","action":"activate"}' command_state: curl -X GET 'http://192.168.5.27:8888/api/devices' | grep 'energy(Reactive)' ```https://user-images.githubusercontent.com/64090632/146373859-88c43d17-6113-46da-8f5f-736e67d4f134.mp4