That’s a shame as I lost access to the data when Plugwise pulled the server. However I understand the Circles store around 2-3 years of data. It’s a real pity I can’t get access to this data for backup. There’s no way to access the data through the Stretch, as far as I know, as all data was stored on the Plugwise server until it was pulled.
If anyone else knows a way to backup the historic data stored on the Circles please advise as this would be extremely useful.
Just in case you are wondering, I will definitely upgrade this app to be compatible with SDK3 and the new Homey Pro.
I have many circles that I use myself. They are the core of my own home automation.
New version 4.0.1 is ready for testing: Plugwise2py App for Homey | Homey
This will ensure the compatibility with future Homey versions.
@dcj Many thanks for your kind donation. Much appreciated! 
After 2 weeks i can’t get it working. I filled in my circle mas adresses , let it run for a few hours, i don’t see circles in the web page.
2023-08-12 15:35:22,484 - pw-logger - DEBUG - PARS 01 EVAL 1
2023-08-12 15:35:22,484 - pw-logger - DEBUG - PARS 01
2023-08-12 15:35:22,484 - pw-logger - DEBUG - PARS 01 EVAL 1
2023-08-12 15:35:22,484 - pw-logger - DEBUG - PARS 050D6F00029C28DC
2023-08-12 15:35:22,484 - pw-logger - DEBUG - PARS 050D6F00029C28DC EVAL 36 4069190721349852
2023-08-12 15:35:22,484 - pw-logger - DEBUG - PARS 0805
2023-08-12 15:35:22,484 - pw-logger - DEBUG - PARS 0805 EVAL 2053
2023-08-12 15:35:22,485 - pw-logger - DEBUG - PARS FF
2023-08-12 15:35:22,485 - pw-logger - DEBUG - PARS FF EVAL 255
2023-08-12 15:35:22,485 - pw-logger - DEBUG - <plugwise.protocol.PlugwiseStatusR esponse object at 0xb64b9190>
This what i get in the logging.
All the circles are working in Source and also with a Stretch 3.0
I’d like to do a final attempt to add my plugwise circles into Homey pro 2023 via the pw2py app and a raspberry PI with plugwise dongle.
Raspberry Pi 3 Model B Rev 1.2
Operating system 20231012~bullseye (64 bit)
I followed all instructions to set up the pw2py on raspberry , including the config files. No errors reported.
I set the parameters in the app on Homey (IP, mqtt port 1883). Testing MQTT connection gives positive result.
Issues:
the link to browser seems to work, but circles are not available (empty screen). An error occurs: niet beveiligd.
The app on homey gives an error in the logfiler: [ERROR: Url error: [Errno 111] connection refused.
Do you have any suggestions to fix this?
Coffee or beer can be arranged 
Is that caused by an encryption setting maybe? Look at your TLS configuration.
f56c6ebe-e421-4336-83ec-1b589f71816b
crashing again short after restarting app
SOLVED, resetting the Pi solved the crashing.
new version 4.1.0 is ready for testing: Plugwise2py App for Homey | Homey
Used it for a long time without problems but did some stupid things so I have to re-install the raspberry-pi. Doing so, I encounter problems, first with 32bit OS getting the message that OS64 is expected, then with OS64, when docker is installed, the next is shown:
Server: Docker Engine - Community
Engine:
Version: 28.0.4
API version: 1.48 (minimum version 1.24)
Go version: go1.23.7
Git commit: 6430e49
Built: Tue Mar 25 15:07:18 2025
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: 1.7.27
GitCommit: 05044ec0a9a75232cad458027ca83437aae3f4da
runc:
Version: 1.2.5
GitCommit: v1.2.5-0-g59923ef
docker-init:
Version: 0.19.0
GitCommit: de40ad0
================================================================================
To run Docker as a non-privileged user, consider setting up the
Docker daemon in rootless mode for your user:
dockerd-rootless-setuptool.sh install
Visit https://docs.docker.com/go/rootless/ to learn about rootless mode.
To run the Docker daemon as a fully privileged service, but granting non-root
users access, refer to https://docs.docker.com/go/daemon-access/
WARNING: Access to the remote API on a privileged Docker daemon is equivalent
to root access on the host. Refer to the 'Docker daemon attack surface'
documentation for details: https://docs.docker.com/go/attack-surface/
================================================================================
-bash: Executing: command not found
-bash: syntax error near unexpected token `newline'
Is this alarming? Ignoring this,
After the install is finished and Docker is restarted, the Circles data is collected, so far so good, but after that, nothing happens, all my Circles can be seen via the webbrowser but the Circles cannot be switched via the webbrowser.
@Gruijter Please advise what to do.
Better use the full rpi image I created. The docker image itself doesnt seem to be working anymore 
The full rpi image is also using OS32, same expecting OS64.
Yes, but is is a os32 version that works with the embedded docker image.
YES! That’s the solution, thanks very much.
