ECU-R 2162

[ViperRNMC]

Hey, zoals beloofd een issue voor het vervolgen van de 2162.

Debug log in Home Assistant:

2024-12-07 16:02:23.343 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy.api] Server for port 8997 started
2024-12-08 00:00:00.311 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy] midnight reset
2024-12-08 00:00:00.312 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy] Requesting midnight_reset to update with value SensorData(data=0, attributes={'timestamp': datetime.datetime(2024, 12, 8, 0, 0, 0, 312136, tzinfo=zoneinfo.ZoneInfo(key='Europe/Amsterdam'))})
2024-12-08 11:22:46.907 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy.config_flow] async_get_options_flow called: <ConfigEntry entry_id=01JEB644BM9VQK7P6EAP1VT3QB version=1 domain=apsystems_ecu_proxy title=APsystems ECU proxy state=ConfigEntryState.LOADED unique_id=None>
2024-12-08 11:22:46.922 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy.config_flow] async_step_init with configuration: {'ema_host': '3.67.1.32', 'max_stub_interval': '300', 'message_ignore_age': '1800', 'no_update_timeout': '660', 'send_to_ema': True}
2024-12-08 11:22:48.167 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy.config_flow] async_step_init with configuration: {'ema_host': '3.67.1.32', 'max_stub_interval': '300', 'message_ignore_age': '1800', 'no_update_timeout': '660', 'send_to_ema': True}
2024-12-08 11:23:09.109 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy.api] Server for port 8995 stopped
2024-12-08 11:23:09.110 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy.api] Server for port 8996 stopped
2024-12-08 11:23:09.111 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy.api] Server for port 8997 stopped
2024-12-08 11:23:26.248 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy.config_flow] async_step_user
2024-12-08 11:23:29.538 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy.config_flow] async_step_user
2024-12-08 11:23:29.597 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy] Creating server for port 8995
2024-12-08 11:23:29.601 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy.api] Server for port 8995 started
2024-12-08 11:23:29.601 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy] Creating server for port 8996
2024-12-08 11:23:29.608 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy.api] Server for port 8996 started
2024-12-08 11:23:29.608 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy] Creating server for port 8997
2024-12-08 11:23:29.614 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy.api] Server for port 8997 started
2024-12-09 00:00:00.436 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy] midnight reset
2024-12-09 00:00:00.436 DEBUG (MainThread) [custom_components.apsystems_ecu_proxy] Requesting midnight_reset to update 

Unifi en Adguard geprobeerd om A-host/DNS rewrite uit te voeren naar ip van addon ipv ecu.apsystemsema.com. Data wordt op moment van draaien addon niet naar ema gestuurd, zodra de rewrite weer uit is komt de data wel binnen. Voldoende info? wat zijn de vervolgstappen die we kunnen nemen?

[HAEdwin]

Thanks for submitting. Currently quite busy days at the end of the year. The closed issues show that the ECU-C communicates, for example, via socket port 9001, 9002 and 9003. So you could check whether you can receive data via those ports if you manage to adjust the code. Unfortunately I can't help you alot because I still own a 2160xxxx and not a 2162xxxx ECU-R model. So if you see data (with the integration set in debug mode, I would like to have that along with a date/time stamp).

[HAEdwin]

@ViperRNMC
I bought a new ECU-R 2162 thinking that my old 2160 had broken down. That turned out not to be the case, so now I can test both models (which is great). I have now also discovered that the 2162 communicates with EMA via ports 8997, 9227 and 9228 and unfortunately via a different communication protocol (secure), which is of course safer, but does not help to get this integration working for the 2162. The conclusion is that this integration is only ECU-R (2160) and ECU-B compatible.

So for now I let this project rest,.. it's stable and working great for those who prefer this. In the meantime, I am finally completely reviewing and cleaning up the other variant in terms of code. With both ECUs in hand I can easily test how they respond. The integration already works faster at start-up and has been very stable so far.

[ViperRNMC]

Thanks for the update, if you need some testing let me know.

[HAEdwin]

I'll close this issue with the conclusion that this integration is only ECU 2160 and ECU-B compatible.