Compatibility Smartlink SI D

[D2702]

Is it also possible to use an Acti 9 Smartlink SI D gateway? I saw in another topic that there was a possibility for a Smartlink SI B.

I certainly cannot add these automatically and manually at the moment.

[Breina]

These ones? https://www.se.com/uk/en/product-range/64482-acti9-smartlink-si-d/44105740929-gateways

Yeah they're supported. Are you seeing any errors?

[D2702]

Yes, this is it, it is an old type, not what is available now, it does have the latest firmware version (V2.4.6) It does not work either automatically or manually.

I can find the errors below in the "home assistant.log" Are there any places I should look?

2024-01-30 18:07:20.161 WARNING (MainThread) [homeassistant.util.async_] Detected blocking call to sleep inside the event loop by custom integration 'powertag_gateway' at custom_components/powertag_gateway/soap_communication.py, line 42: services = wsd.searchServices(types=[QName(NAMESPACE_SCHNEIDER, LOCAL_NAME_GATEWAY_SERVER)]), please create a bug report at https://github.com/Breina/PowerTagGateway/issues 2024-01-30 18:07:20.286 WARNING (Thread-3) [daemon] could not find handler for: _handle_probe 2024-01-30 18:37:58.131 WARNING (MainThread) [homeassistant.components.modbus.modbus] modbus hub1 communication closed

[Breina]

Ah I see.

Can you check that your web interface has this configured as such?

We should be able to get more logs through HomeAssistant through Settings > System > Logs, then search for powertag_gateway and click 'Load full logs', for example:

Please send me all of those logs, that should be more helpful.

[D2702]

Hi,

Below is the configuration of the Smartlink.

I get the following error when I want to connect to the Smarlink from HA.

Unfortunately, I cannot find much in the log you requested. see below.

[Breina]

Ah man I didn't log that error, that's on me. Sorry about that!

In custom_components/powertag_gateway/config_flow.py on line 169, please add logging.error(e) (indentation matters).

Then restart and check logs.

Is it possible that your Gateway is unreachable through the network?

[D2702]

I have adjusted the code. The gateway is available from the network (located in the same subnet). I can also read this via a modbus client.

Below is the logging:

Also an image of the TAG configuration:

When I change the IP address of the modbus port in the gateway, I get an error below. Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.100.31:502)]

This error also occurs immediately if the gateway is not reachable. If this is accessible, it will take quite a while before I get the other error.

[Breina]

If this is accessible, it will take quite a while before I get the other error.

Yeah that's because we need to search for the synthesis table first;

So it's going through all 247 tables before throwing this error.

Can you please use your modbus client to check that this one exists on address 247? I use this first one to check we got the right one;

(reference: https://www.productinfo.schneider-electric.com/powertaglinkuserguide/powertag-link-user-guide/English/BM_PowerTag%20Link%20D%20User%20Manual_4af62430_T000501355.xml/$/TPC_SynthesisTableIdentificationREF_0000550649)

[D2702]

I think the "Smartlink SI D" doesn't have a synthesis table. I can't find this anywhere in the manual. This is only stated in the manual of the "PowerTag Link Gateway".

[Breina]

Aaah ok! I get it. Yes.

Alright I know what to do, give me a moment to develop this for you.

Uploading manual for my own reference DOCA0115EN-03.pdf

[Breina]

Please test v0.2.2-alpha: https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha

[D2702]

I see the option in the configuration menu, but when I click connect I immediately get an error.

[Breina]

Alright thanks for testing. Added more logs and made one thing more resilient. Please report back.

[Breina]

https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha2

[D2702]

Unfortunately, the error code is also still the same.

[Breina]

I think the code didn't quite update, it must print some logging before the crash;

Can you see these in custom_components/powertag_gateway/config_flow.py?

[D2702]

Yes, I see.

[Breina]

Ok thanks for clearing this up.

This one should log better; https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha3

[D2702]

[Breina]

Much better!

Fixed https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha4

[D2702]

A step forward, but no tags are added.

[Breina]

Getting there :)

https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha5

[D2702]

Sorry... It seems the same.

[Breina]

No, this is better. We're getting further :)

Hold on

[Breina]

Btw 'Unknown' is I can't read the device's name. So it's going to be called Unknown. Please suggest a better default if you have one. :)

[Breina]

Getting close now

https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha6

[D2702]

Same fault

[Breina]

Not the same fault, we're actually making great progress!

I'll fix these tomorrow.

[D2702]

Ok, good night and thank you very much for checking this out!

[Breina]

This might well be the last fix we needed! :)

https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha7

[D2702]

Another step closer, I no longer receive any error messages. Only the power tags are not visible. Do I need to configure anything else?

[Breina]

It's me, not you. You should have been seeing powertags.

So since on your device, there's no way to determine how many devices are connected, I just have to try slave addresses starting from 150 until one fails. What's happening now is that it fails immediately.

Can you please try reading this table on slave id 150?

[D2702]

I can read this value via a modbus client, see below. FYI, this value also corresponds to the installed tag.

[Breina]

Alright thanks for confirming!

Found and fixed an off-by-one error. :)

https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha8

[D2702]

Thanks for the update. The power tags are not added yet, but I do get the error below. Hopefully you can do something with this.

If it is too difficult or takes too much time, you can also say so and I will do it in a different way. I really like that you are still trying to integrate this module!

[Breina]

In schneider_modbus.py on line 531, can you please change identifier = self.__read_int_16(0x792F, power_tag_index) into identifier = self.__read_int_16(0x7930, power_tag_index)? I believe I made a mistake.

If it is too difficult or takes too much time, you can also say so and I will do it in a different way.

Not at all! :) This is normal error driven development progress. I appreciate you testing so much for me. I would really like to support your device!

[D2702]

Good to hear! I have adjusted the modbus address, I no longer get error messages, but the tags are not added either.

[Breina]

I haven't forgotten you, just have been busy the last few days.

The lack of errors is the bane of error-driven-development, so I'm scratching my head a bit. I can add a bunch of logs tomorrow to see what it's doing and where it fails.

[Breina]

Alright, please try this one: https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha9

And please fetch me all of its logs. Should be able to figure out where it goes wrong.

[D2702]

Attached is the requested log.

[Breina]

Ok my brain finally managed to understand this problem during my dog walk. I fixed this. Try it out! :)

https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha10

[KingandQ]

I recently started using Home Assistant. So, little experience yet.

During installation the option “Perform automatic DWPS discovery” didn’t work. But it was successful via manually entering the Host IP-Address. No error messages during installation.

It seems I have a similar problem.: now devices or entities are found.

I would like to install the patch, but unfortunately, I have no knowledge how to do this. After unzipping the alpha10-zip-file I recognize existing directory structure, but also new ones. Can you please provide instructions on how to install this patch correctly?

[Breina]

Hi, welcome to the club! :) Thanks for being willing to test as well!

Yeah you have to specifically enable pre-releases: https://hacs.xyz/docs/faq/beta/. Then you can just update through HACS (restart afterwards).

You can also do it manually through downloading the release, copying the custom_components/powertag_gateway folder into the custom_components folder of your HomeAssistant. Then restart.

[KingandQ]

Thanks for explaining.

After installing patch alpha10, there is an additional option for selecting type of Gateway. I’ve tried all 3.

When selecting: Panel server

• Fail to connect.

When selecting: PowerTag Link

• The correct name of the PowerTagLink is displayed, but no devices or entities.

When selecting type of Gateway: Smartlink SI D

• Unit A9XMWA20 is found
• Name is Unknown
• But : 1 device and 2 entities.

My configuration:

• 1 * Acti9 SmartLink
• 12 * A9MEM1560
• 1 * A9MEM1542
• 1 * A9MEM1541

[Breina]

Oh looks like we've made progress then! We found one of your powertags, but the sensors don't work properly yet. It's the smartlink one that you should pick, this is the one I'm setting up for this issue.

Can you please go to Settings > System > Logs and filter on powertag_gateway, then copy paste here what you see there.

[KingandQ]

As requested:

[Breina]

Ah man something is wrong with these logs. Missing a lot of crucial information.

How is your logged configured in your configuration yaml?

Here's an example:

logger:
  default: info
  logs:
    custom_components.powertag_gateway: debug

[Breina]

The code is very verbose in telling me what's going on;

[KingandQ]

Sorry, but I recently started using Home Assistant. All new to me ;-)

Configuration.yaml modified as indicated. Logging filtered by: powertag

[Breina]

Please don't apologise! I had to learn this at one point too. :)

I appreciate you taking your time to wrestle through this.

Please upgrade to v0.2.2-alpha11, restart, add the integration again and check your logs. Won't fix anything, but should be more verbose around where it's going wrong.

[KingandQ]

After installing patch:

Logging filtered by: powertag

I do not see mutch diference. I’ve gone through the rest of the logging but don’t see any Powertag related info.