Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Control no longer possible after firmware update to 1.1.2_b (EZ1-M) #142340

Open
LocaEasy opened this issue Apr 5, 2025 · 2 comments
Open

Control no longer possible after firmware update to 1.1.2_b (EZ1-M) #142340

LocaEasy opened this issue Apr 5, 2025 · 2 comments

Comments

@LocaEasy
Copy link

LocaEasy commented Apr 5, 2025

The problem

Description:
After the automatic firmware update to version 1.1.2_b, it is no longer possible to control my EZ1-M device from APsystems.

Details:

Image

Device: EZ1-M by APsystems

Firmware version: 1.1.2_b

Serial number: E070000009266

Issue: Control via automations, scenes, and scripts is no longer functional.

Current behavior:
Since the update, no active automations, scenes, or scripts are shown in the interface. Adding new ones appears possible, but they do not take effect.
External control (e.g., via Home Assistant or API) also seems to be non-functional.

Observed behavior:

No error messages on the UI

Logbook only shows standard messages (“OK”, “no problem detected”)

Control commands have no effect

Suspected cause:
It seems likely that firmware version 1.1.2_b disabled or blocked the control functionality or relevant interfaces.

Question to the community / developers:
Are there any known changes introduced with firmware 1.1.2_b that affect device control?
Is there a fix or rollback option available?

Thanks in advance for your support!

What version of Home Assistant Core has the issue?

Core 2025.4.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

AP Systems

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

@silviuk
Copy link

silviuk commented Apr 6, 2025

Can't tell if it's the same reason, but since 4h ago none of my 2 APsystems EZ1-M (firmware versions 2.0.1_b and respectively 1.7.7) work anymore:

Image

The only thing that was updated yesterday for me is the latest 2025.4.1 HA core. I may have not realized that the devices were not updating data anymore until today.

The inverters are both pingable from the local network and report correctly the data to the APsystems app via Bluetooth.

@silviuk
Copy link

silviuk commented Apr 6, 2025

Can't tell if it's the same reason, but since 4h ago none of my 2 APsystems EZ1-M (firmware versions 2.0.1_b and respectively 1.7.7) work anymore:

Image

The only thing that was updated yesterday for me is the latest 2025.4.1 HA core. I may have not realized that the devices were not updating data anymore until today.

The inverters are both pingable from the local network and report correctly the data to the APsystems app via Bluetooth.

Fixed in my case after restarting HA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants