Legrand/Bticino MyHome

microgolgi · February 28, 2024, 7:35pm

Hi Julien and all,

Is it possible to add 2 lights or 2 covers in the same room ?
I tried this:
Salle_de_douche:
where: “17”
name: “lampe salle de douche plafond”
Salle_de_douche:
where: “18”
name: "lampe salle de douche meuble
But it doesn’t work.

Thanks in advance.

EDIT: issue solved. I simply changed the name before the where…

BWsyl · March 11, 2024, 9:22pm

Hello,

I’m using this great integration since a few years now, and everything worked perfectly (with a scenario module 035 65 as a gateway).
Nevertheless, in order to be able to expand my installation, I had to switch to a BTMYHOMESERVER1 module.

And unfortunately, I encounter I think connection problems. After a while, the integration seems to lose connection to the myhomeserver1, but I can’t see anything significant in the logs.
Moreover, if I launch a command, the light respond accordingly, but the interface won’t be updated.

Does anyone have an idea on how to troubleshoot this behavior ?

Thanks a lot
Syl

Nedns · March 14, 2024, 2:02pm

Thanks this works great.

One question. I use Fan Coils for cooling, is there a way to get the Fan speed in to HA ? Or I am not doing something because I am not seeing it.

  climate:
    zone_1:
      zone: '9'
      name: Living room
      heat: True
      cool: False
      standalone: True
      manufacturer: BTicino
      model: KM4691

Thanks !

microgolgi · March 15, 2024, 12:25pm

Dear all,
i’m facing an issue with my covers with Google Home since I started the trial for NabuCasa cloud.

in Google home app, the cover appears as not connected and If I clic on the cover , it says the item doesn’t appear on the WIFI network even if I can ask the closure voicely with my google nest.

This is the structure in the myhome.yaml:
cover:
Chambre_David:
where: ‘23’
name: Volet chambre David
advanced: True

What it’s not correctly defined?
Thanks
PS: Indentation is lost… How can i copy past correctly the code as in the message above mine ?

Achille_Sano · March 16, 2024, 7:15am

Hello all some time a day i need restart integration becouse dont update status and a no work. After reload it is work corrcltly.

Can i make automation for reload :

Use following automation:

automation:
- alias: Restart Dexcom on startup
  trigger:
  - event: start
    platform: homeassistant
  action:
  - service: hassio.addon_stdin
    data:
      addon: name_of_your_addon
      input: restore-sensor
  mode: single

or use time trigger:

  - trigger:
    - platform: time
      # Military time format. This trigger will fire at 3:32 PM
      at: "15:32:00"

OS it work? Or there is other Solution?

Achille_Sano · March 17, 2024, 6:49pm

alias: Ricarica integrazione btcibo
description: “”
trigger:

platform: time
at: “15:00:00”
platform: time
at: “01:00:00”
condition:
action:
service: homeassistant.reload_config_entry
data:
entry_id: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
mode: single

Betman · March 20, 2024, 4:44pm

Hi Monitoraggio, i’ve got MyHomeServer1 and my working config is:
cover:
bedroom_shutter:
where: ‘29’
name: Tapparella Camera Padronale
advanced: True
manufacturer: BTicino
model: LN4661M2
I can open, close and set opening %.

Monitoraggio.home · March 21, 2024, 6:29am

Hi, thanks for answering my problem, I entered the manufacturer Bticino instead of Legrand, the only difference compared to my configuration, however it still doesn’t work. that same file.yaml worked perfectly with HA HASSIO, I can’t figure out where the error is. Thanks again

aedus78 · April 1, 2024, 6:20am

Hi, I’ve been using this integration for a couple of years now, and in the last few days i noticed that all the entities, every 3 minutes or so, become unavailable, then unkwnown, then fhey become available again (with the right state, on/off etc.).
I tried to update and restart home assistant, and this seemed to have fixed the problem, but if i check history, it repeats the state several times in a second (i.e. off at 08.04.01, off at 08.04.01, off at 08.04.01 off at 08.04.01 and so on).
Restarting HA apparently fixes the problem for 15 minutes or so, but then this pattern repeats itself.
What should I check or do…maybe my Home Server 1 is going nuts?

AlbertoD · April 4, 2024, 8:22am

Hi @anotherjulien,
first of all thanks for your contribution.
I installed the integration version 0.9.3 and configured all lights, switches and covers.
I can successfully control all of them, but there is no status reported.
Even if I reduce the config file to a single light, I still have the same problem. I can control the light, but the status is “Unknown”.

Here is my myhome.yaml (mac address is edited):

mh201:
  mac: "00:03:50:a0:00:00"
  light:
    disimpegno_notte:
      where: "0205"
      name: Disimpegno
      dimmable: False
      manufacturer: BTicino
      model: L4671/1

I tried to restart the Home Assistant VM multiple times (also three times in a row), but it didn’t help.

Here is a log file after the integration reload, where I turned on/off the light.

2024-04-03 23:45:52.685 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration myhome which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-03 23:45:52.686 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-03 23:45:55.703 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-04-04 00:45:55.706 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Connection interrupted, reconnecting...
2024-04-04 00:45:55.710 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Data received is not a message: `None`
2024-04-04 01:45:55.595 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Connection interrupted, reconnecting...
2024-04-04 01:45:55.601 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Data received is not a message: `None`
2024-04-04 02:45:55.490 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Connection interrupted, reconnecting...
2024-04-04 02:45:55.495 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Data received is not a message: `None`
2024-04-04 03:45:55.385 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Connection interrupted, reconnecting...
2024-04-04 03:45:55.389 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Data received is not a message: `None`
2024-04-04 04:45:55.280 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Connection interrupted, reconnecting...
2024-04-04 04:45:55.285 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Data received is not a message: `None`
2024-04-04 05:45:55.178 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Connection interrupted, reconnecting...
2024-04-04 05:45:55.183 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Data received is not a message: `None`
2024-04-04 06:45:55.071 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Connection interrupted, reconnecting...
2024-04-04 06:45:55.076 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Data received is not a message: `None`
2024-04-04 07:45:54.966 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Connection interrupted, reconnecting...
2024-04-04 07:45:54.971 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Data received is not a message: `None`
2024-04-04 08:45:54.862 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Connection interrupted, reconnecting...
2024-04-04 08:45:54.869 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Data received is not a message: `None`
2024-04-04 09:45:54.756 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Connection interrupted, reconnecting...
2024-04-04 09:45:54.761 WARNING (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Data received is not a message: `None`
2024-04-04 10:19:29.824 INFO (MainThread) [custom_components.myhome] Unloading MyHome entry.
2024-04-04 10:19:29.825 INFO (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Closing event listener
2024-04-04 10:19:29.831 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Negotiating test session.
2024-04-04 10:19:29.832 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Received nonce: `*#632967638##`
2024-04-04 10:19:29.832 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Sending test session password.
2024-04-04 10:19:29.833 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Test session established.
2024-04-04 10:19:29.834 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Test session closed.
2024-04-04 10:19:29.834 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message `*#1*0205##` was successfully queued.
2024-04-04 10:19:29.838 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Creating listening worker.
2024-04-04 10:19:29.838 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Opening event session.
2024-04-04 10:19:29.839 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Creating sending worker 0
2024-04-04 10:19:29.840 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Opening command session.
2024-04-04 10:19:29.841 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Negotiating event session.
2024-04-04 10:19:29.841 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Negotiating command session.
2024-04-04 10:19:29.841 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Received nonce: `*#842828621##`
2024-04-04 10:19:29.841 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Sending event session password.
2024-04-04 10:19:29.843 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Received nonce: `*#842828621##`
2024-04-04 10:19:29.843 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Sending command session password.
2024-04-04 10:19:29.843 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Event session established.
2024-04-04 10:19:29.844 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Command session established.
2024-04-04 10:19:29.892 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message `*#1*0205##` was successfully sent.
2024-04-04 10:19:29.920 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message received: `*1*0*25##`
2024-04-04 10:19:29.920 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message received: `*1*0*25##`
2024-04-04 10:19:29.921 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Event session closed.
2024-04-04 10:19:29.921 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Destroying listening worker.
2024-04-04 10:19:55.706 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message `*1*1*0205##` was successfully queued.
2024-04-04 10:19:55.747 INFO (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message `*1*1*0205##` was successfully sent.
2024-04-04 10:19:55.779 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message received: `*1*1*25##`
2024-04-04 10:19:58.106 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message `*1*0*0205##` was successfully queued.
2024-04-04 10:19:58.148 INFO (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message `*1*0*0205##` was successfully sent.
2024-04-04 10:19:58.179 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message received: `*1*0*25##`
2024-04-04 10:20:02.172 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message `*1*1*0205##` was successfully queued.
2024-04-04 10:20:02.214 INFO (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message `*1*1*0205##` was successfully sent.
2024-04-04 10:20:02.239 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message received: `*1*1*25##`
2024-04-04 10:20:05.260 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message `*1*0*0205##` was successfully queued.
2024-04-04 10:20:05.301 INFO (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message `*1*0*0205##` was successfully sent.
2024-04-04 10:20:05.329 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message received: `*1*0*25##`
2024-04-04 10:20:09.409 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message `*1*1*0205##` was successfully queued.
2024-04-04 10:20:09.451 INFO (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message `*1*1*0205##` was successfully sent.
2024-04-04 10:20:09.479 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message received: `*1*1*25##`
2024-04-04 10:20:10.473 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message `*1*0*0205##` was successfully queued.
2024-04-04 10:20:10.516 INFO (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message `*1*0*0205##` was successfully sent.
2024-04-04 10:20:10.549 DEBUG (MainThread) [custom_components.myhome] [MH201 gateway - 192.168.1.32] Message received: `*1*0*25##`

Any help is appreciated. Thanks.

Marko99f · April 7, 2024, 3:36pm

Hi, guys!
I have a question, can i config a cen event with a phisic configuration? If yes how?
I ve been trying to config like this:
My phisic config is the following:
A1: 3
Pl1: 3
M1:cen
A2:
Pl2:
M2:cen

SylvainS · April 8, 2024, 5:55pm

Bonjour Julien,
Do you think it could be possible to add support for the Legrand/Bticino Myhome Play USB Key in your plugin ?

JackPin · April 12, 2024, 9:39pm

Hello Julien,

first of all, thanks for the amazing work. My entire home automation system relies on your integration and, if it was not there, I’d be completely stuck.

I’ve configured the integration correctly and everything works like a charm, but at a certain point it gets stuck.
I can no longer interact with lights, switches or whatever.
I used to notice events coming through all the time from the energy sensor, and now they’re all gone, the event stream is compeltely silent. Even events coming from the physical switches on the wall are not being received.

The home server itself is still running, the switches still works and I can access it via other apps.

The logs do not provide much information, the last two I have from myhome are

Logger: custom_components.myhome
Source: custom_components/myhome/gateway.py:387
integration: MyHome (documentation, issues)
First occurred: April 11, 2024 at 5:57:16 PM (2 occurrences)
Last logged: April 11, 2024 at 5:57:20 PM

[F454 gateway - 10.0.5.2] Could not send message `*#1*0110##`.
[F454 gateway - 10.0.5.2] Could not send message `*#1*0111##`.

which I think might be the periodic message to wake up the power meter.

The only way to get things working again is to reboot HA.

This happens pretty much once a day, it is quite a nuisance.

Here is the chart of the power meter, the flat lines are when the integration stops and the same value is held until reboot.

Do you have any idea as to why? What other info can I provide?

I have found some logs that might point to an issue. It seems at a certain point the session is lost or has to be renewed and it gets stuck in a loop.

2024-04-14 19:47:24.507 INFO (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Sensor 1 is reporting an active power draw of 486 W.
2024-04-14 19:47:41.665 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*1*1000#1*13##`
2024-04-14 19:47:41.665 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Ignoring translation message `*1*1000#1*13##`
2024-04-14 19:47:41.717 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*1*10*13##`
2024-04-14 19:48:07.801 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` was successfully queued.
2024-04-14 19:48:07.810 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Command session connection reset, retrying...
2024-04-14 19:48:07.810 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Opening command session.
2024-04-14 19:48:07.815 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Negotiating command session.
2024-04-14 19:48:07.818 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Received SHA challenge: `*98*2##`
2024-04-14 19:48:07.818 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Accepting sha256 challenge, initiating handshake.
2024-04-14 19:48:07.821 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Sending command session password.
2024-04-14 19:48:07.989 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` received response `*#18*51*51*567463##`.
2024-04-14 19:48:08.031 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` was successfully sent.
2024-04-14 19:49:07.801 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` was successfully queued.
2024-04-14 19:49:07.810 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Command session connection reset, retrying...
2024-04-14 19:49:07.811 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Opening command session.
2024-04-14 19:49:07.815 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Negotiating command session.
2024-04-14 19:49:07.818 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Received SHA challenge: `*98*2##`
2024-04-14 19:49:07.819 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Accepting sha256 challenge, initiating handshake.
2024-04-14 19:49:07.821 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Sending command session password.
2024-04-14 19:49:07.989 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` received response `*#18*51*51*567463##`.
2024-04-14 19:49:08.030 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` was successfully sent.
2024-04-14 19:50:07.802 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` was successfully queued.
2024-04-14 19:50:07.812 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Command session connection reset, retrying...
2024-04-14 19:50:07.812 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Opening command session.
2024-04-14 19:50:07.817 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Negotiating command session.
2024-04-14 19:50:07.820 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Received SHA challenge: `*98*2##`
2024-04-14 19:50:07.820 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Accepting sha256 challenge, initiating handshake.
2024-04-14 19:50:07.823 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Sending command session password.
2024-04-14 19:50:

Looking back at the topic it seems I might have the same issue as @XDUSS had here

@XDUSS have you solved the issue somehow?

Folgore733 · April 13, 2024, 3:53pm

Hi everyone
I’m new here, I also have a problem with the integration that sometimes breaks down.
the error message is as follows:
[Myhomeserver1 gateway - 192.168.2.35] Data received is not a message: *#22*3#1#1*1*10##
[Myhomeserver1 gateway - 192.168.2.35] Data received is not a message: *22*3#1*3#1#1##
[Myhomeserver1 gateway - 192.168.2.35] Data received is not a message: *#22*3#1#1*1*11##
[Myhomeserver1 gateway - 192.168.2.35] Data received is not a message: *22*0#4#0*3#1#1##
[Myhomeserver1 gateway - 192.168.2.35] Data received is not a message: *#22*3#1#1*12*0*10##.
I think it is linked to the fact that messages are arriving from the myhome sound system.
can it be solved?

AlbertoD · April 15, 2024, 10:43am

I solved my problem.
Looking at the log I see these lines:

[MH201 gateway - 192.168.1.32] Message `*#1*0205##` was successfully sent.
[MH201 gateway - 192.168.1.32] Message received: `*1*0*25##`

which I guess is the status request and the answer. The second line is also repeated after the commands to turn on-off the light. It should be the new status confirming a status change.

Interestingly, the commands are sent for a where=0205, but the answer is sent for a where=25.
I changed the where to 25 (removing the zeros) in the yaml file and everything now works as expected.

JackPin · April 16, 2024, 8:42pm

I noticed something else in the logs. Normally, after the response arrives from the gateway, it is “interpreted” in a human readable fashion. See the following

2024-04-16 20:08:13.327 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Command session connection reset, retrying...
2024-04-16 20:08:13.328 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Opening command session.
2024-04-16 20:08:13.333 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Negotiating command session.
2024-04-16 20:08:13.336 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Received SHA challenge: `*98*2##`
2024-04-16 20:08:13.336 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Accepting sha256 challenge, initiating handshake.
2024-04-16 20:08:13.339 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Sending command session password.
2024-04-16 20:08:13.507 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*#18*51*51*584395##`
2024-04-16 20:08:13.507 INFO (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Sensor 1 is reporting a total power consumption of 584395 Wh.
2024-04-16 20:08:13.510 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` received response `*#18*51*51*584395##`.
2024-04-16 20:08:13.551 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` was successfully sent.
2024-04-16 20:08:15.203 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*#18*51*113*1550##`
2024-04-16 20:08:15.204 INFO (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Sensor 1 is reporting an active power draw of 1550 W.
2024-04-16 20:08:35.351 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*1*1000#0*13##`
2024-04-16 20:08:35.351 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Ignoring translation message `*1*1000#0*13##`
2024-04-16 20:08:35.400 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*1*0*13##`
2024-04-16 20:08:42.266 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*1*1000#0*13##`
2024-04-16 20:08:42.266 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Ignoring translation message `*1*1000#0*13##`
2024-04-16 20:08:42.319 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*1*0*13##`
2024-04-16 20:08:44.735 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*1*1000#0*13##`
2024-04-16 20:08:44.736 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Ignoring translation message `*1*1000#0*13##`
2024-04-16 20:08:44.786 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*1*0*13##`
2024-04-16 20:08:45.138 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*#18*51*113*1540##`
2024-04-16 20:08:45.139 INFO (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Sensor 1 is reporting an active power draw of 1540 W.

What I mean is

2024-04-16 20:08:13.507 INFO (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Sensor 1 is reporting a total power consumption of 584395 Wh.
2024-04-16 20:08:13.510 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` received response `*#18*51*51*584395##`.

When the integration get stuck, this does not happen anymore, as the loop is

2024-04-16 20:08:47.509 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*1*1000#1*13##`
2024-04-16 20:08:47.510 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Ignoring translation message `*1*1000#1*13##`
2024-04-16 20:08:47.561 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*1*10*13##`
2024-04-16 20:09:13.320 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` was successfully queued.
2024-04-16 20:09:13.329 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Command session connection reset, retrying...
2024-04-16 20:09:13.330 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Opening command session.
2024-04-16 20:09:13.334 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Negotiating command session.
2024-04-16 20:09:13.339 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Received SHA challenge: `*98*2##`
2024-04-16 20:09:13.339 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Accepting sha256 challenge, initiating handshake.
2024-04-16 20:09:13.342 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Sending command session password.
2024-04-16 20:09:13.511 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` received response `*#18*51*51*584395##`.
2024-04-16 20:09:13.555 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` was successfully sent.
2024-04-16 20:10:13.321 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` was successfully queued.
2024-04-16 20:10:13.330 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Command session connection reset, retrying...
2

without any parsing of the value.

I notice though that the message response for total energy consumption does change overtime, so the sensor and the gateway are responding with up to date values.

2024-04-16 20:10:13.512 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` received response `*#18*51*51*584395##`.
 and after a while
2024-04-16 20:32:13.532 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message `*#18*51*51##` received response `*#18*51*51*584948##`.

Tho the UI does not report any change, I guess because it is not parsed and updated by the integration.

Lastly, I noticed that when the integration gets stuck I do not get any more acknowledgement from the gateway of messages being received, such as

2024-04-16 00:07:12.465 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*1*0*08##`

JackPin · April 18, 2024, 5:46pm

I might be on to something.

When I turn on a regular light, I get three events, in order:

event_type: myhome_message_event
data:
  gateway: 10.0.5.2
  message: "*1*1000#0*09##"
  family: Command translation
  type: Status
  who: 1
  where: "09"
  what: 1000
  what parameters:
    - "0"
origin: LOCAL
time_fired: "2024-04-18T17:36:45.059288+00:00"
context:
  id: 01HVS4GG03Z60NT9PTT6R971TW
  parent_id: null
  user_id: null

event_type: myhome_message_event
data:
  gateway: 10.0.5.2
  message: "*1*0*09##"
  family: Event
  type: Status
  who: 1
  where: "09"
origin: LOCAL
time_fired: "2024-04-18T17:36:45.132662+00:00"
context:
  id: 01HVS4GG2CBSCJ9T7TSA5M55Q2
  parent_id: null
  user_id: null

event_type: state_changed
data:
  entity_id: light.terrazza_piccola
  old_state:
    entity_id: light.terrazza_piccola
    state: "on"
    attributes:
      supported_color_modes:
        - onoff
      color_mode: onoff
      A: "0"
      PL: "9"
      friendly_name: Small Terrace
      supported_features: 8
    last_changed: "2024-04-18T17:36:43.909439+00:00"
    last_reported: "2024-04-18T17:36:43.909439+00:00"
    last_updated: "2024-04-18T17:36:43.909439+00:00"
    context:
      id: 01HVS4GEW5FAY2PA7RATTA80R8
      parent_id: null
      user_id: null
  new_state:
    entity_id: light.terrazza_piccola
    state: "off"
    attributes:
      supported_color_modes:
        - onoff
      color_mode: null
      A: "0"
      PL: "9"
      friendly_name: Small Terrace
      supported_features: 8
    last_changed: "2024-04-18T17:36:45.133549+00:00"
    last_reported: "2024-04-18T17:36:45.133549+00:00"
    last_updated: "2024-04-18T17:36:45.133549+00:00"
    context:
      id: 01HVS4GG2DF1RGCS1S369ESH9S
      parent_id: null
      user_id: null
origin: LOCAL
time_fired: "2024-04-18T17:36:45.133549+00:00"
context:
  id: 01HVS4GG2DF1RGCS1S369ESH9S
  parent_id: null
  user_id: null

Which I assume is the event for the light switch and its translation by the integration.

If I do so with a dimmable light

event_type: myhome_message_event
data:
  gateway: 10.0.5.2
  message: "*1*1000#1*13##"
  family: Command translation
  type: Status
  who: 1
  where: "13"
  what: 1000
  what parameters:
    - "1"
origin: LOCAL
time_fired: "2024-04-18T17:43:57.886245+00:00"
context:
  id: 01HVS4XPNYXGDDY547AHBRF42R
  parent_id: null
  user_id: null

event_type: myhome_message_event
data:
  gateway: 10.0.5.2
  message: "*1*10*13##"
  family: Event
  type: Status
  who: 1
  where: "13"
  what: 10
origin: LOCAL
time_fired: "2024-04-18T17:43:57.925931+00:00"
context:
  id: 01HVS4XPQ50MGF8THJPXBWKRJ6
  parent_id: null
  user_id: null

2024-04-18 19:43:57.886 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*1*1000#1*13##`
2024-04-18 19:43:57.886 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Ignoring translation message `*1*1000#1*13##`
2024-04-18 19:43:57.925 DEBUG (MainThread) [custom_components.myhome] CHIPOTLE
2024-04-18 19:43:57.925 DEBUG (MainThread) [custom_components.myhome] [F454 gateway - 10.0.5.2] Message received: `*1*10*13##`
2024-04-18 19:43:57.937 ERROR (MainThread) [custom_components.myhome] Traceback (most recent call last):
File "/config/custom_components/myhome/gateway.py", line 264, in listening_loop
self.hass.data[DOMAIN][self.mac][CONF_PLATFORMS][LIGHT][message.entity][CONF_ENTITIES][LIGHT],
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
KeyError: '1-13'

Could it be due to the dimmable light message format?

I use a DALI dimmer, could that be the cause?

JackPin · April 18, 2024, 8:41pm

Turns out, a light in my home was not mapped in the configuration of this integration, and interacting with it would cause a message to look up an entity in a dictionary, not finding it and breaking.

At least that’s how I’ve understood it so far.

thatitguy · April 20, 2024, 6:45am

Hi all I am considering to use for production this integration (I have a F454 as gateway and a large systems with around 100 devices) but reading this thread it seems is really unstable (many users complaining it get stuck every few times per day → need to restart HA)

but what also worries me is that there is basically no answer from the developers for several weeks, so basically no help/support.

Why this integration is not officially part of HA?

Also there is no automatic discovery of devices and everything must to be configured via yaml files.

So I am looking for suggestion and maybe experience with alternatives?

Sdomotica_Automation · April 21, 2024, 8:23pm

Sdomotica_Automation](/u/Sdomotica_Automation)

1m

For biggest systems I suggest mine solution Sdomotica