Thanks, that helps. But itâs bad news, it shows that our code doesnât detect your Stretch.
Let me think about what we can do nextâŚ
You didnât open the VOLLEDIG HOME ASSISTANT LOGBOEK I think?
When you open it, is there more info displayed related to this error?
What to do next: on your webbrowser can you please browse to: (replace stretch-ip-adres by 192.168.x.xyz, replace x and xyz by numbers)
http://stretch-ip-adres/core/domain_objects
And look for something like this:
<module id='f7aec5636cb74ace95ff4ecde676e1eb'>
<vendor_name>Plugwise</vendor_name>
<vendor_model>NR</vendor_model>
<hardware_version>0000-0440-0107</hardware_version>
<firmware_version>2011-06-27T10:52:18+02:00</firmware_version>
<created_date>2014-04-05T01:05:07.112+02:00</created_date>
<modified_date>2020-08-03T22:02:45.660+02:00</modified_date>
<deleted_date></deleted_date>
<services>
<electricity_point_meter id='6b14043118244715bdcf32c0616240a8'>
<measurement log_date="2020-08-03T22:02:45.630+02:00" unit="W" directionality="consumed">0.00</measurement>
<measurement log_date="2020-08-03T22:02:45.630+02:00" unit="W" directionality="produced">0.00</measurement>
</electricity_point_meter>
<electricity_interval_meter id='4361585930b442a399e9f528d1a62701'>
<measurement log_date="2020-08-03T22:00:00+02:00" unit="Wh" directionality="consumed" interval="PT1H">0.00</measurement>
</electricity_interval_meter>
<relay id='cf19ac6a98d448de9293b1558f7473ea'>
<measurement log_date="2020-08-03T22:02:22.120+02:00">off</measurement>
</relay>
</services>
<protocols>
<network_router id='0e369c55ace04c128c11c327c96127fb'><mac_address>0123456789AB</mac_address><network id='6e3e708b07ca4648964795a582c90ad1'/></network_router>
</protocols>
</module>
Iâm particularly interested in the part:
<protocols>
<network_router id='0e369c55ace04c128c11c327c96127fb'><mac_address>0123456789AB</mac_address><network id='6e3e708b07ca4648964795a582c90ad1'/></network_router>
</protocols>
How does that look on your Stretch?
Ok, can you find another entry that has ânetwork_routerâ instead of ânetwork_coordinatorâ and show it here? Preferably the first entry from the top of the file.
no there is no router entry 
at the bottom i have 
Ok, thatâs unexpected. On the other hand, until now we only have data from one Stretch with 2.3.12 firmware. You are the 2nd one who clearly has a different setup 
Always welcome to try debugging with this stretch
How many network_coordinators and master_controller entries are there in your /core/domain_objects?
One of each?
Never mind, I have decided to use network_coordinator, I think this is the Circle+ or equivalent.
You have installed plugwise-beta via HACS?
Just FYI, Iâm running into an issue, I will try to have the fix available sometime tomorrow-evening.
Yes I did the install through hacs
Relax, no hurry. Thanks for your time and good Luck with the other issue
Talk to you soon
I might have something similar.
Stretch firmware : 2.7.18
The error:
2022-01-24 19:46:33 ERROR (MainThread) [plugwise.smile] Connected but expected text not returned, we got <Element âdomain_objectsâ at 0x7fb9d8dd56d0>
The /core/domain_objects returns empty. (<domain_objects/>)
@mikje @pepijng Please install and test Plugwise-beta v0.20.0-alpha10.
You can do this in HACS by clicking on the 3 vertical points in the plugwise integration rectangle, click Redownload and in the window that pops up, select Show beta. Then this test version should be shown.
You can ignore the DONâT INSTALL warning.
The error in the UI still exists but âŚ
2022-01-25 09:15:54 ERROR (MainThread) [custom_components.plugwise.config_flow] Unexpected exception
Traceback (most recent call last):
File "/config/custom_components/plugwise/config_flow.py", line 256, in async_step_user_gateway
api = await validate_gw_input(self.hass, user_input)
File "/config/custom_components/plugwise/config_flow.py", line 133, in validate_gw_input
await api.connect()
File "/usr/local/lib/python3.9/site-packages/plugwise/smile.py", line 314, in connect
result = await self._request(DOMAIN_OBJECTS)
File "/usr/local/lib/python3.9/site-packages/plugwise/helper.py", line 304, in _request
resp = await self._websession.get(url, headers=headers, auth=self._auth)
File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 559, in _request
await resp.start(conn)
File "/usr/local/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 898, in start
message, payload = await protocol.read() # type: ignore[union-attr]
File "/usr/local/lib/python3.9/site-packages/aiohttp/streams.py", line 616, in read
await self._waiter
aiohttp.client_exceptions.ClientOSError: [Errno 104] Connection reset by peer
This is a different error: looks like this is a connection-problem.
We should probaby catch this error in our code and retry.
Can you please retry yourself a few times?
From other users we know that the Stretch is slow in responding, we have set a timeout of 30 seconds, when the unit still hasnât responded the connection will be reset.
You are right I had an issue with my Stretch. But still the original error
2022-01-25 12:09:42 ERROR (MainThread) [plugwise.smile] Connected but expected text not returned, we got <Element 'domain_objects' at 0x7f0026b57810>
2022-01-25 12:09:45 ERROR (MainThread) [plugwise.smile] Connected but expected text not returned, we got <Element 'domain_objects' at 0x7f0026b0af90>
2022-01-25 12:09:47 ERROR (MainThread) [plugwise.smile] Connected but expected text not returned, we got <Element 'domain_objects' at 0x7f0026a8fbd0>