Underneath the event
date and time, but where is it coming from ?
Here are some fresh:
I noticed that light state works when turn light on or off in HA.
But reverse is not possible (turn on off from HA)
I also noticed that some actuator are not in green but in yellow.
Hop ei can help you help me 
@supertabouret, debug logs can be enabled by adding this to your configuration.yaml, and restarting HA.
logger:
logs:
custom_components.myhome: debug
Then the logs themselves can be found in /config/home-assistant.log (right next to your configuration.yaml)
WHO=2 is for covers, if you receive this warning in the logs, it means Home Assistant received an event for a device that is not configured.
It means you have a cover with address A=9 PL=6.
It would likely be simpler if you could get a clear picture of what devices you have and what their addresses are 
@dirk291, well, that’s interesting! As far as I know, it’s normal for the gateway to broadcast it’s time and date on its own. This allows all devices on the bus that rely on time and date for scheduling to be synchronised (i.e. heating system, energy meters, etc…)
What’s weird though is that this message is a “dimension writing” message, I would not have expected to see those on the event bus!
@anotherjulien
Thank you so When a light works i got
2022-01-12 13:46:52 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [548343375568] Received {'type': 'call_service', 'domain': 'light', 'service': 'turn_on', 'service_data': {'entity_id': 'light.terrassecuisine_light'}, 'id': 187}
2022-01-12 13:46:52 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=light, service=turn_on, service_data=entity_id=light.terrassecuisine_light>
2022-01-12 13:46:52 DEBUG (MainThread) [custom_components.myhome] Message *1*1*31## was successfully queued.
2022-01-12 13:46:52 DEBUG (MainThread) [custom_components.myhome] Message *1*1*31## was successfully unqueued by worker 0.
2022-01-12 13:46:52 DEBUG (MainThread) [custom_components.myhome] Command session connection reset, retrying...
2022-01-12 13:46:52 DEBUG (MainThread) [custom_components.myhome] Opening command session.
2022-01-12 13:46:52 DEBUG (MainThread) [custom_components.myhome] Negotiating command session.
2022-01-12 13:46:52 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [548343375568] Sending {"id": 187, "type": "result", "success": true, "result": {"context": {"id": "f5feb31c846183e8bd3c6d5c4dbda68c", "parent_id": null, "user_id": "c33fd2b8cabd4d839cd09a85f89286cd"}}}
2022-01-12 13:46:52 DEBUG (MainThread) [custom_components.myhome] Reply: *#*1##
2022-01-12 13:46:52 DEBUG (MainThread) [custom_components.myhome] Received nonce: *#293570546##
2022-01-12 13:46:52 DEBUG (MainThread) [custom_components.myhome] Sending command session password.
2022-01-12 13:46:52 DEBUG (MainThread) [custom_components.myhome] Reply: *#*1##
2022-01-12 13:46:52 DEBUG (MainThread) [custom_components.myhome] Command session established.
2022-01-12 13:46:52 INFO (MainThread) [custom_components.myhome] Message *1*1*31## was successfully sent.
2022-01-12 13:46:52 DEBUG (MainThread) [custom_components.myhome] Received: *1*1*31##
2022-01-12 13:46:52 INFO (MainThread) [custom_components.myhome] Light 31 is switched on.
But when i select a light that dont yet work i got :
2022-01-12 13:49:57 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [548343375568] Received {'type': 'call_service', 'domain': 'light', 'service': 'turn_on', 'service_data': {'entity_id': 'light.sdbetagemiroir_light'}, 'id': 205}
2022-01-12 13:49:57 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=light, service=turn_on, service_data=entity_id=light.sdbetagemiroir_light>
2022-01-12 13:49:57 DEBUG (MainThread) [custom_components.myhome] Message *1*1*0113## was successfully queued.
2022-01-12 13:49:57 DEBUG (MainThread) [custom_components.myhome] Message *1*1*0113## was successfully unqueued by worker 0.
2022-01-12 13:49:57 DEBUG (MainThread) [custom_components.myhome] Command session connection reset, retrying...
2022-01-12 13:49:57 DEBUG (MainThread) [custom_components.myhome] Opening command session.
2022-01-12 13:49:57 DEBUG (MainThread) [custom_components.myhome] Negotiating command session.
2022-01-12 13:49:57 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [548343375568] Sending {"id": 205, "type": "result", "success": true, "result": {"context": {"id": "5a1f64b40ab11a0168b612fdefcb1daa", "parent_id": null, "user_id": "c33fd2b8cabd4d839cd09a85f89286cd"}}}
2022-01-12 13:49:57 DEBUG (MainThread) [custom_components.myhome] Reply: *#*1##
2022-01-12 13:49:57 DEBUG (MainThread) [custom_components.myhome] Received nonce: *#606395626##
2022-01-12 13:49:57 DEBUG (MainThread) [custom_components.myhome] Sending command session password.
2022-01-12 13:49:57 DEBUG (MainThread) [custom_components.myhome] Reply: *#*1##
2022-01-12 13:49:57 DEBUG (MainThread) [custom_components.myhome] Command session established.
2022-01-12 13:49:57 INFO (MainThread) [custom_components.myhome] Message *1*1*0113## was successfully sent.
If we compare both we can see that 2 lines are missing at the end.
Also please note i am using only Basic Control i have never used actuators (as i am using scan automation by local button to identify which device is what, though some Switches point to same Light), maybe i should ?
Can you edit your last two posts to enclose the logs in code blocks? (between two lines with 3 ` characters)
In your devices, the actuators are the ones actually doing the work, these are the ones actually connecting and disconnecting the electricity to your load.
The commands are, in a way, just remote controls. You setup your system to tell the ‘commands’ what ‘actuator’ they will talk to.
In theory both should be equivalent, but by default, look at the actuators, not the commands.
@anotherjulien
I edited (sorry i did not know the code block function, i hope it as you asked now)
Also i checked and i can say that some “actuators” APL is same than some “commands” APL
Normal?
Thank you, much more readable!
So, the gateway accepts the message, but then it does not seem to cause anything. (the last two logs when working are saying that the light turned on, independently of what actually turned it on.)
Given the situation, my guess would be that there’s something wrong with the address, maybe it’s not what you think it is?
Yes, same APL between commands and actuator is normal.
As I said, if you give (for example) 31 to a command, it means it will control the actuator with address 31; that’s all.
1/ Huum interesting…do you mean the wallswitch to turn on the light could not be a switch WHO 1 LIGHT but WHO 1 SWITCH ? Or an automation? So i should try the apl with those Whos ?
2/ Let s take this singlewall switch that is for only One light/bulb. How come it has 4 modules ?
It it normal ? knowing module 1 and 3 have same APL could it be the “bug” ?
-
I meant that maybe the light that you thought to be A=1 PL=13 is actually not that. Indeed if you have a scenario module, that command could trigger a scenario that in turn switches the light on. That would be visible as the “function type” of your command being something like CEN or CEN+ maybe
-
When you have an actuator/command, you have both devices in one, you have the command (which is the buttons you press) and the actuator (which is the relays behind the buttons) in one package.
If you use physical configuration the commands will always match the actuator, but if you use the virtual configuration mode, you have more flexibility.
Modules 1 and 2 are the actuators, module 3 and 4 are the commands.
If you wish to, you could configure a wall button to not control the actuator right behind it but something else entirely (I’ve done that in a few places in my home)
However, the default is to be the same; i.e. module 3 (left button) controls module 1 (left relay)
Before i give up, i will try more things for which i thank you if you can answer.
1/ Thinking of what you told me, i rechecked the plant. I have 11 Actuators with APL that i did not used.
But they all do that :
These actuators APL are set with WHO LIGHT. If i try them with WHO SWITCH will do a difference ?
2/ I have 2 scenario buttons HD4680
https://catalogue.bticino.com/BTI-HD4680-EN
They seem to be MyHomeUP. Does it mean they work with myhomeUP though they are inside the F454 ? Then should i look for a HA addon compatible with myhomeup or yours is ?
3/ Let s say i want to reprogramm some light switches because they are not working in HA…
I know how to identify the switch by clicking on Scan automation by local button in MyHomeSuite.
But then how do i find the address of the concerned Buld/Light or i should say actuator ?
hi, a have a question , there is a way to find or how to write a request with time cron or other to update the value of torus F520 more often in place of only 30 sec reading interval, if anyone has an idea?
thanks
Does any light in the house switch on when you click one of your tests?
What happens is that HA sends the command to turn it on, but it never receives the event to say that it is on, so it reverts back to off by default.
Your HD4680 will work fine, but they are commands for scenarios only as far as I know, they cannot be used to switch on lights directly. So if you have lights turning on when you press one of them, it means it is done through a scenario. This means the “address” that is configured on them is the address of the scenario, not the actuator.
I would not recommend starting to reprogram things on your bus because they do not work in HA! You need to understand completely how your bus in configured and why; only then will you have all the information you need to know what to put in HA or not.
Get in touch with the person or company that installed it, they should have produced at list a modicum of documentation about the config…
@Isoparme, I’m not sure I understand the question, I have a cron every 2 or 4 hours (I don’t remember) with the command directing the F520 to send its instantaneous power automatically.
It sends a new value as soon as the power draw changes (probably excluding minor variations).
@anotherjulien
Hope you are fine.
So i did many tests and understood almost fully how the bus is configured.
I found another bus install that is linked with the F454 since these items show in MyHome Suite.
But these have leds blinking as on video here :
Even though i found all the correct APL of the correct Actuators, i still have that problem : The HA switches get the correct state but i am unable to turn on or off the switch the light from HA
I wonder how i can be helped …
Do you mean you have multiple busses in your installation? Linked by an F422 or something similar?
I have a mainboard where the F454 is and yes There seems to be indeed a F422 but on the mainboard.
And i have another board (that is in another part of the house) that is linked to the mainboard (F454) with 2 devices on error (outdoor lights but i dont mind these)
i find the way to do it , with own 18 command and a python script based on
https://github.com/francesco-re-1107/openwebnet-alarm
thanks for your time and excelent works
Hi all!
I came from domoticz and decided to switch to HA to have more features.
How install the gateway for Myhome ? in domoticz a plugin is already available with the install, how install that on HA ? how configure the gateway with ip etc ?
Thanks
@anotherjulien since 1 or 2 month ago all work now I have same problem. I see state but can’t switch ligth and cronotermo I can’t see. So do I have f422 between ligth and alarm bus.
log:
File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 325, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
File “/config/custom_components/myhome/config_flow.py”, line 402, in async_step_ssdp
discovery_info[“port”] = None
TypeError: ‘SsdpServiceInfo’ object does not support item assignment
I have similar situation, work on e off but after 5.minute a don’t see state ligth