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?

[KingandQ]

Thanks for the update.
I have numbered all units consecutively. (150…..163)
All 15 units have been found.

Only unit shown as “Unknown” (the A9XMWA20)

[KingandQ]

OEPS!!!
After upgrade to version v0.3.0, and a restart:
All Entities of all units are “Unavailable”

[Breina]

Ah man sorry about that, I refactored a lot of code. I'll can fix that tomorrow.Can you include your logs as well please? That will help for sure.On 4 May 2024 10:36, KingandQ ***@***.***> wrote: OEPS!!! After upgrade to version v0.3.0, and a restart: All Entities of all units are “Unavailable” image.png (view on web) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[KingandQ]

No problem, there seems to be light at the end of the tunnel………. 

Results after some testing:
Test-Environment:

• First installed version 0.2.5
• All Diveces where found and all there entities except the entities for A9XMWA20
  Live-Environment:
• Reloaded version 0.2.5 (so donwgraded from 0.3.0)
• All devices where found and all there entities except the entities for AX9MWA20
  Test-Environment:
• Upgrade to 0.3.0
• All Diveces where found and NON of the entities.

Unfortunately, no more time to filter all power tag lines from the logging.

[Breina]

Unfortunately, no more time to filter all power tag lines from the logging.

@KingandQ any chance you can get me those logs still? I don't immediately see what I missed in the upgrade.

[KingandQ]

Due to a short holiday I was not able to respond sooner.
The attached document is the logging of the test environment from 5-5-2024.
(Test_Envr_V0_3_0.docx)
Test_Envr_V0_3_0.docx

[Breina]

Alright I got that fixed for you on v0.4.1. :)

Hope everything works now?

[KingandQ]

Unfortunately not yet.
Logging after installation of V.04.01
Test_Envr_V0_4_1.docx

[Breina]

In the full logs, can you please show me what happens right after this line?

Error while setting up powertag_gateway platform for sensor

The HA filtering eats part of the stacktrace. >.<

[Breina]

To be clear, talking about this part:

[KingandQ]

A screenshot without a filter:

[Breina]

Thanks! Fixed this one as well. :)

Please check out 0.4.2. That should do it I think.

[KingandQ]

[Breina]

How about v0.5.0?

[KingandQ]

Thanks for the update.

A Big step forward.
All units are found but some data is still missing.
Version 0.2.0 is OK.

Version 0.5.0:

• Temperature in: F (Maybe this is an environment setting?)
• 3 times: Unavailable

[Breina]

Temperature is indeed your config, we receive them as Celcius.

Alarm valid has been removed because I deemed it useless and needed work. You may remove this one.

Active power phase Phase.A has been renamed to Active power phase A, does it not appear for you? Maybe try another restart or reconfig?

Partial energy should be the same as Partial energy delivered and received right? There really should be an entity that is available for this.

[KingandQ]

The latest version installed on the live environment today.
It seems that all data retrieved from all 14 units are displayed correctly.

Regarding: A9XMWA20
I don't know if this is all that can be displayed:

• Datetime
• Status

[Breina]

Glad to hear! :)

It should also display hardware version, firmware version and serial number in device info. The status has an extra attribute showing what's wrong when something is wrong. And that's literally everything that your device exposes through modbus. It's the same for the Panel Server even, that's everything.

[KingandQ]

Today I put all entities of all units on a dashboard
The following enteties all show the value: Unknown

Is this as expected?

[Breina]

Ah no, I hoped they did work. I'll fix them for you.

[Breina]

Did some fixes in in v0.5.1, please try again. The 'phase A' ones will become unavailable, as they're not supported by Smartlink.

[KingandQ]

After install V0.5.1

[Breina]

Ah man I was hoping the 'Unknown' ones would have worked. :( They are only available for NSX devices it seems.

Please confirm that your device isn't an NSX one? I'll disable those for non-NSX ones in the next round.

The Unavailable ones can be removed, those aren't supported.

[KingandQ]

First of all, thanks again for all your efforts to resolve this.

Below my hardware-configuration as in my previous post:

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

Since they don't appear in your overview, I assume these are not NSX devices.

Is it recommended to remove all "Unavailable" and all "Unknown" entities, or does that happen automatically with the next update?

[Breina]

Ah right, I should have figured.

The "Unavailable" ones mean that the entity is no longer provided by this integration, and must be removed manually. I can't do this for you as far as I'm aware.

The "Unknown" ones mean that this integration tries to get its data, but it's not able to. You can't remove this one yet, but next release, I'll make them become "Unavailable" so you can clean them up.

[KingandQ]

Some additional info.

I have 5 modules of type A9DG3616.
2 out of 5 show power factor : Unknown

What needs to be done to correct this?

[Breina]

Cleaned up those Unknown entities for you now, these will become Unavailable, which you can remove now.

For the power factor;

Is there a difference in firmware version between the devices? For example, device temperature only becomes available from firmware versions 004.xxx.xxx, it's possible that power factor has a similar threshold.

Otherwise, can you find any differences between its setup of your device configuration? Can you find any problem in the logs about this? This entity also uses 'Power factor sign convention', perhaps that requires configuration?