Legrand/Bticino MyHome

Third party integrations
164

according to your log warnings, you must enter where as the address. just remove the number 5. you should have this configuration.

sensor:
  - platform: myhome
    devices:
      prese_piano1:
        where: '73'
        name: prese_piano1
        class: power
        manufacturer: BTicino
        model: F522
      cucina_f522:
        where: '72'
        name: cucina_f522
        class: power
        manufacturer: BTicino
        model: F522
      centrale_termica:
        where: '71'
        name: centrale_termicaf522
        class: power
        manufacturer: BTicino
        model: F522

EDIT: See here

165

Thank you caiosweet ! I tried without 5 but it return always 0.
I was using 571 because for f520 and f521 the address with 5 is returning the correct value.
Example:
water_heater_power:
where: ‘5125’
name: “Centrale Termica”
class: power
manufacturer: BTicino
model: F520

166

Sorry! my bad.
in fact there is also written on github …

where is also a special case for those as well since power meters are always “5” followed by the sensor number assigned “[1-255]”.

maybe you lack automation to update the data, see here

service: myhome.start_sending_instant_power
data:
  duration: 125
  entity_id: sensor.general_power
167

@federicoimg, changing the requirement to 0.7.20 forces your Home Assistant instance to download and install that version of the OWNd library that is used to communicate with the gateway. In that version I fixed a bug related to message handling and the way the zone number is manipulated.
Could you let me know if the actuators 2 and 3 for heat and cold is something you can configure or is it always 2 and 3 for everybody? (If this is something you know, of course!)

@Betman, I see in the WHO 18 documentation that F522 actuators have an address as “7[1-255]” instead of “5[1-255]” for F520 (F523 seem to have both??)
Can you try by just putting the where like this:

sensor:
  - platform: myhome
    devices:
      prese_piano1:
        where: '773'
        name: prese_piano1
        class: power
        manufacturer: BTicino
        model: F522
      cucina_f522:
        where: ‘772’
        name: cucina_f522
        class: power
        manufacturer: BTicino
        model: F522
      centrale_termica:
        where: ‘771’
        name: centrale_termicaf522
        class: power
        manufacturer: BTicino
        model: F522

EDIT: Nevermind, I see in the code that I ignore the message if the where does not start with “5”, give me some time to edit this, and I will publish a new version of OWNd!
I’ll let you know when you can try!

168

@anotherjulien I change the confing but unfortunately always 0. Could you link me the documentation so i can check?
@caiosweet I can collect data from other sensor without the service, only f522 are giving me problem

thankyou

169

Actually, the change in the code was not that bad… So I already published the new version of OWNd.
All you need to do to try it is edit the manifest.json file and set the requirement as OWNd==0.7.21 and set your configuration as follows:

sensor:
  - platform: myhome
    devices:
      prese_piano1:
        where: '73'
        name: prese_piano1
        class: power
        manufacturer: BTicino
        model: F522
      cucina_f522:
        where: ‘72’
        name: cucina_f522
        class: power
        manufacturer: BTicino
        model: F522
      centrale_termica:
        where: ‘71’
        name: centrale_termicaf522
        class: power
        manufacturer: BTicino
        model: F522

With the sensors as 71, 72 and 73 (That’s why it already started with a 7, I should have known :smiley:)

Once done, restart HA and it should work like this!
When you confirm it works properly, I’ll publish this new requirement in the integration’s master branch.

(The OpenWebNet documentation for WHO 18 is here, but as all documentation for OpenWebNet: it is old and incomplete.)

170

I changed according your suggestion and restarted home assistant. Unfortunately data is another time 0.
I configured the same object in myhome app as energy meter with the same address…and also there the value is 0!
So I think your integration is correct, is myhome up system that doesn’t permit reading this data.
I also enabled bedug log and cannot see message concerning object with ID 71-72-73, only with ID 5xx.
Is anyone using the same module ( f522 ) and collecting data?

171

Ciao Julien,
about the actuators I’m not sure, I checked installator manual of 4695 central unit (4 zone) and it is possible to configure actuators in the range 1-9. In my system number 2 and 3 are configured but I think this is something that can be changed for different systems.

Thanks again.

172

@Betman, I suppose you also tried to call the appropriate service to get the sensor to send its instant power consumption, right?
It might be those do not send instant power since they seem to be designed for load control, but that would still be strange.

@federicoimg, thanks for the information :slightly_smiling_face: This is a level of complexity that I won’t tackle right now, but I’ll keep it in mind for a future development!

173

Julien, great job. Thank you.
I installed through HACS and I can control devices, but I don’t get status updates.
A restart didn’t help.

Also, the ‘Integrations’ page shows 5 instances of the F454. I don’t know if this is related.
2021-01-17_12-43-31

174

Hi, yes, that would probably be your problem…
You’ll need to go to all gateways configured on the integration page and delete all of them to leave only one (does not matter which one).
Then restart and you should be good to go!

I still need to remove the mechanism that tries the default password automatically, it’s more trouble than it is worth in the end.

175

You were right - this solved the issue. THANK YOU!

176

Yes, i created the corresponding service but no value is returned. At the moment i’ll use only f520 module and leave this 3 unconfigured
Thank you

177

Ok. Sometimes it happens.
I found this workaround.
API - Reload integration with CURL or Rest Command

I hope it will be useful :sunglasses:

1 Like
178

Hi,
about power monitoring with F522, have you tried to use 71#0, 72#0, 73#0 ?

where18_01

179

The #0 part should not be part of what is put in the configuration file.
The library splits this when receiving events, and the unique identifier for the device will always ignore what’s the # and whatever comes after.

180

Hi Julien,
I’m using your fantastic MyHome component for a month and it works fine.
But concerning the cover items it seems that you don’t support the optimistic attribute that allows to track automatically the cover state, depending on the command you send it.
Is it correct ?
Do you have any plan to support it?
Thanks in advance for your help

181

I’m afraid I’ve never heard about the optimistic attribute…
Can you explain what it is / how it works? Or is there documentation about that?

182

Unfortunately there is no real documentation about that attribute.
A short and not very clear description is here:

In my opinion, maybe it means that the cover entity could assume the state is close or open as soon as it receive the close or open command respectly, regardles if the cover is really in that state (an optimistic assumption).

I found a similar behavoiur in Homebridge that has the possbility to declare in an attribute the timing the shutter requires for closing. Based on that timing you can define a percentage of closure of the shutter, because the entity records automatically the timing of the command duration.
Do you think something like one of these features can be implemented?

Thanks

183

From what I can see, that attribute is only present in the Template cover, not in the actual cover entity.

If Home Assistant plans to add a function supporting this in the cover entity, I’ll be glad to implement it.
I’m not planning, however, to add these functionalities if they are not supported in the wider Home Assistant system.