-
Notifications
You must be signed in to change notification settings - Fork 66
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
F422 BUS-BUS Interface #87
Comments
As can be seen in the image of the light, the icon is represented by a lightning bolt and does not change state when the button is pressed |
Can you show me the exact configuration you have for those lights? (in a code block, so the formatting is not lost) |
what I am attaching is a small summary. where you see the interface set are separate zones. where I have not set the interface are shared zones under the F422 module |
Hmmm, the configuration looks perfectly fine. |
Goodmorning, same issue me too. |
If you want I can make you a user and password to enter directly.so you can
verify exactly what I tell you.
Il Sab 10 Giu 2023, 10:52 anotherjulien ***@***.***> ha
scritto:
… Hmmm, the configuration looks perfectly fine.
Would you be able to collect and post debug logs of what happens when you
turn on the light?
—
Reply to this email directly, view it on GitHub
<#87 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A477BWVNGZIX32LQUSQ6J6TXKQYTFANCNFSM6AAAAAAYZ4PTOQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I attach the debug log. The problem is with light 6.6 interface 01 and light 6.6 shared with no interface. When I turn on or off the light with interface 01, the status of the icon does not change. if, on the other hand, I turn on or off the light without an interface, the status icon works. In my opinion, the problem exists in the configuration file loading phase because it displays a lightning bolt instead of light. |
This is really strange, it looks like the interface was not extracted from the message. |
I have never done this analysis. can you tell me what i have to do? I don't have access to all folders |
It depends on your install method. |
Hello, i also have the same problem, i use HassOS. All the light/switch in secondary bus( interface 02 for me) show lightning icon. |
Same problem here, when defining the interface, the status is not retrieved from the light |
Hi and thanks for this great integration. I have the same problem. Devices conected to interface "01" send the command but que icon on HA don't show if light is on or off. There is a solution? |
Hello. I've found a solution/workaround for not working with interface. I have done 2 changes in my system:
I'm going to make a pull request for both |
Would love to see the code and update it in my installations |
Hello those are the changes: Myhome OWNd: Hope it helps. |
When I use the 'Interface' #4# commands it doesn't show me the correct status of the lights.
While the button works, it does not change the status of the icon
The problem is more serious when you have 2 lights with the same 'where' code "A=01, PL=10" but one light is connected to #4# 01 for example and the other is connected below the F422 BUS-BUS module in the condominium backbone.
<configuration_identifier>:
for example
1 light:
who:
where: <0110>
interface: <01>
name:
manufacturer:
model:
2 light:
who:
where: <0110>
name:
manufacturer:
model:
in this case when you activate light 1 it turns on correctly but the icon remains off and light 2 does not turn on (correctly) but the icon turns on
The text was updated successfully, but these errors were encountered: