Powertech Gate (EyeOpen) – gate control and live status in Home Assistant

Share your Projects! Custom Integrations
, ,
21

Hi Marek,

thanks again for the detailed test results.

I’ve now released v0.9.7, which adds privacy-safe diagnostics specifically for the 404 shadow issue you’re seeing.

The goal of this version is to check whether your Powertech account exposes a different AWS IoT Thing/client/device identifier than the UUID currently used by the integration.

Please update to 0.9.7 through HACS, restart Home Assistant, and try the setup again with debug logging enabled.

If it still fails, please send the Powertech log lines containing:

Powertech discovery item
Powertech selected AWS Thing identifier
Powertech shadow request rejected
Powertech shadow validation timed out

The new diagnostics only include field names and short fingerprints, not the raw identifiers.

This should tell us whether the 404 is caused by using the wrong Thing identifier or whether we need to investigate a different state-reporting path.

Thanks again for helping with the testing!

Andras

22

Hi Andras,

I tested v0.9.7 and the setup still fails.

The new diagnostics show:

Powertech selected AWS Thing identifier source=uuid ... alternative_identifier_candidates=[]

The MQTT connection succeeds and the subscriptions are ready, but all four shadow GET attempts are rejected with:

Powertech shadow request rejected; code=404

The final validation result is:

Powertech shadow validation timed out; mqtt_connected=True subscriptions_ready=True confirmed=['command_ack', 'position', 'shadow_accepted', 'shadow_rejected', 'shadow_updated'] failed=[] get_attempts=4 get_accepted=0 get_rejected=4 publish_failures=0

So it looks like the integration is still using the UUID as the AWS Thing identifier, and no alternative identifier candidates were found.

Let me know if you would like me to test another build or provide any additional privacy-safe diagnostics.

Thanks again!

23

Hi Marek,

thanks again for testing.

I’ve now released v0.9.8 with the next diagnostic step for your 404 shadow issue.

Since v0.9.7 confirmed that no alternate Thing identifier is exposed by the backend, this version now passively checks whether your controller publishes state through other MQTT topics or a named AWS IoT shadow instead of the default shadow.

No gate movement commands are sent during this test, and message payloads or raw unknown topic names are not logged.

Please update to 0.9.8 through HACS, restart Home Assistant, and try adding the integration again with debug logging enabled.

If setup still fails, please send the Powertech lines containing:

Powertech MQTT subscription acknowledged
Powertech passive MQTT activity
Powertech shadow request rejected
Powertech shadow validation timed out

The final validation line will now also show passive topic counts and safe fingerprints for any unknown topics that were seen.

This should tell us whether your controller is exposing its state somewhere outside the default AWS IoT shadow.

Thanks again for your help!

Andras

24

Hi Andras,
I tested v0.9.8. This time the result is different from my previous test.
MQTT connects successfully, but the validation ends with:
Powertech shadow validation timed out; mqtt_connected=True subscriptions_ready=False confirmed=[‘shadow_accepted’] failed= get_attempts=0 get_accepted=0 get_rejected=0 publish_failures=0 passive_topic_counts={‘position’: 0, ‘command_ack’: 0, ‘unknown_device_topic’: 0, ‘named_shadow_update’: 0} unknown_topic_fingerprints=
I also see several successful MQTT connections followed shortly by:
Powertech MQTT disconnected: Unspecified error
So unlike the previous test, there are no 404 shadow rejections this time because no shadow GET request is attempted (get_attempts=0).
Passive monitoring also did not detect any position, command acknowledgement, unknown device topic, or named shadow update.
The setup still fails and the device is not added to Home Assistant.
Let me know if you would like me to test another build or provide any additional privacy-safe diagnostics.

25

Hi Marek,

thanks again for the testing.

I’ve now released v0.9.9 with a more targeted diagnostic for the persistent shadow 404.

From the EyeOpen APK analysis, I confirmed that the official WBT01 client uses a fixed AWS IoT endpoint in eu-central-1. Version 0.9.9 now compares the endpoint returned by the Powertech user-certificate API with that official endpoint.

I also removed the broader MQTT wildcard subscriptions introduced in 0.9.8, since your last test showed they could disrupt the AWS IoT session before normal shadow validation completed. So 0.9.9 restores the known-good subscription behavior from 0.9.7.

Please update to 0.9.9 through HACS, restart Home Assistant, and try the setup again with debug logging enabled.

Could you please send the Powertech lines containing:

Powertech AWS endpoint diagnostic
Powertech AWS endpoint source diagnostic
Powertech shadow request rejected
Powertech shadow validation timed out

The endpoint diagnostic is privacy-safe: it only shows whether the certificate endpoint matches the official EyeOpen WBT endpoint and the AWS region. It does not log the raw endpoint or credentials.

This should tell us whether the 404 is caused by the backend giving Home Assistant a different AWS IoT endpoint than the official EyeOpen app expects.

Thanks again for helping narrow this down!

Andras