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

Cannot connect to ecomax360i #143

Open
4 of 10 tasks
lachand opened this issue Oct 24, 2024 · 2 comments
Open
4 of 10 tasks

Cannot connect to ecomax360i #143

lachand opened this issue Oct 24, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@lachand
Copy link
Contributor

lachand commented Oct 24, 2024

Is there an existing issue for this?

  • I have searched the existing issues

I'm having the following issue:

I get a ‘No devices found on the network’ message when I try to add the integration.

I use elfin EW11 RS485/wifi for the connection.
When I connect via TCP, I get an ecomax360i indication and the name of one of my circuits appears.

I have configured the EW11 as indicated in issue 63 but it doesn't work.

I have following devices connected:

  • ecoMAX 3xx series
  • ecoMAX 8xx series
  • ecoMAX 9xx series
  • Expansion module B
  • Expansion module C
  • ecoSTER 200/ecoSTER Touch
  • ecoLAMBDA
  • ecoNET 300

I'm connecting to my devices using:

Ethernet/WiFi to RS-485 converter

I'm seeing following log messages:

Traceback (most recent call last):
  File "/usr/local/lib/python3.12/asyncio/tasks.py", line 520, in wait_for
    return await fut
           ^^^^^^^^^
  File "/usr/local/lib/python3.12/asyncio/locks.py", line 212, in wait
    await fut
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/plum_ecomax/config_flow.py", line 188, in async_step_identify
    await self.identify_task
  File "/config/custom_components/plum_ecomax/config_flow.py", line 264, in _async_identify_device
    await self.connection.get(DeviceType.ECOMAX, timeout=DEFAULT_TIMEOUT),
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/pyplumio/helpers/event_manager.py", line 66, in get
    await self.wait_for(name, timeout=timeout)
  File "/usr/local/lib/python3.12/site-packages/pyplumio/helpers/event_manager.py", line 52, in wait_for
    await asyncio.wait_for(self.create_event(name).wait(), timeout=timeout)
  File "/usr/local/lib/python3.12/asyncio/tasks.py", line 519, in wait_for
    async with timeouts.timeout(timeout):
  File "/usr/local/lib/python3.12/asyncio/timeouts.py", line 115, in __aexit__
    raise TimeoutError from exc_val
TimeoutError

My diagnostics data:

ecomax

Code of Conduct

  • I agree to follow this project's Code of Conduct
@lachand lachand added the bug Something isn't working label Oct 24, 2024
@denpamusic
Copy link
Owner

Hi,

Sorry for the delayed response, sadly from you screenshot above, it seems like you device use GazModem3 (GM3) protocol.
PyPlumIO and, by extension, this integration use ecoMAX (EM) protocol to connect to the controller, hence your device is currently unsupported.

There is some work being done to bring GM3 protocol support to PIO, but it is very slow, because I don't have GM3-compatible device myself.

@lachand
Copy link
Contributor Author

lachand commented Nov 4, 2024

Hi,
Thank you for your reply.
Is the problem with the GM3 protocol related to the frame format?
If you need help from owners of GM3-compatible devices, don't hesitate to tell me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants