Wat is er nieuw

This update includes every change since Phaeton v0.66.105.

What changed

Phaeton v0.66.107

• Maintenance only: Phaeton's own code now follows a stricter internal error-handling rule. Charging, settings, the web pages and the connection to the GX behave as before.

Phaeton v0.66.106

• When Dynamic ESS or Opportunity Loads takes over the charger, Phaeton now accepts the GX's first charging command straight away, as a Victron EV Charging Station does. Before, the first command was refused, the GX logged an error, and control started a few seconds later.

This update includes every change since Phaeton v0.66.100.

What changed

Phaeton v0.66.105

• With the Auto mode Controlled by the Victron GX, the Charging page now names the Victron feature that controls the charger: Controlled by Dynamic ESS or Controlled by Opportunity Loads, and Paused by Dynamic ESS or Paused by Opportunity Loads when it pauses charging. Before, it said only GX.
• From Venus OS 3.90, Dynamic ESS can take control of the charger with the Auto mode Controlled by the Victron GX, when Phaeton connects to the GX over MQTT, EV charging control is on in the Dynamic ESS settings in VRM and the charger is in Auto. The guide explains what that needs, and that Dynamic ESS starts charging at the lowest current when none of its time slots in the hour after the car was plugged in includes the car.

Phaeton v0.66.104

• On a phone, the bottom bar now holds only Charging, Schedule, Settings and System. Log out moved to the top right of the screen, so it is no longer one tap away from System.
• The header buttons and the chart range choices on a phone are easier to tap, and the whole "Not licensed" badge now opens the activation page.
• Dark mode no longer lights up the selected charge mode, the warning and status banners, the license badge, the activation guidance and the setup steps in pale colours. They use darker tones that are easier on the eyes at night, and the selected mode stands out with a brighter edge. The Schedule page shows each day's track again in dark mode.
• Switches and day choices that are off now have a clearly visible edge.
• The browser tab now names the page you are on, for example "Schedule · Phaeton". Screen readers announce the new page when you switch pages, and keyboard focus moves to its heading.
• After you change the charge mode, the phase choice or Start/Stop with the keyboard, focus returns to that button once Phaeton has handled the request.
• The top bar, the Settings save bar and, on a phone, the bottom bar no longer hide the button or field you move to with the keyboard. With large text the top bar wraps instead of pushing its buttons off the screen.
• The Skip to content link now moves to the page content instead of switching to the Charging page.
• The diagnostics page is now called Health everywhere: in the System tabs, on the page itself and in the links that lead to it.
• The Logs page is tidier. The filter, the log level, Follow and Contact support stay in view; copying, downloads and clearing are under More. On a phone the log now starts on the first screen.
• The log level on the Logs page is now called "Device log level" and explains that it changes what Phaeton records for everyone who uses it. When DEBUG or TRACE is on, the page says until when, and if Phaeton does not accept a new level, the page says so and shows the level that still applies.
• When multiple relay charging is off, the reason beside the phase choice now uses that same name. Directions to settings now use one style, and a few labels use sentence case, such as "Log out" and "Activation mode".

Phaeton v0.66.103

• The online user guide has a new What's new page with the release notes of recent Phaeton versions, newest first. The release notes on the Updates page link to it.

Phaeton v0.66.102

• Settings, Logs and Updates now link to the matching part of the online user guide. Each Settings page has a Learn more link, and so do the Phases, Inverter protection, Session pricing, Access and Maintenance cards.
• When the Charging page explains a status, it now links to the guide's list of status messages, which says what each one means and what to do.

Phaeton v0.66.101

• The charging history charts can now be read with the keyboard and by screen readers. Select a chart and use the arrow keys to step through earlier readings; each reading's time, charging mode and values are shown under the chart and read aloud. Without a selection, the latest reading is shown.
• The charts are easier to read. Every gridline has a value, times fall on round minutes, and the charging mode and number of phases are written along the top. Measured values are the only solid line, limits are dashed or dotted, the charger maximum is red and solar surplus is a shaded area, so the lines can be told apart without relying on colour.
• Where the energy comes from now separates the live readings, under "Now", from this session's solar and grid share, under "This session". On tablets the energy readings form two rows of two.
• Past sessions is always shown. It says when there are no completed sessions yet, and if the list cannot be loaded or refreshed it says so, shows when the list was last loaded, and offers Retry.
• Chart descriptions now say "1 sample" instead of "1 samples".

This update includes every change since Phaeton v0.66.89. Read the upgrade notes first: some installations need an action.

Upgrade notes

Phaeton v0.66.100

• If you chose Battery-powered or Feed-in as the Auto mode for an Easee, Zaptec, Tinkerforge WARP or Bender charger, or a KEBA whose phase switching source is not set to Modbus, only because the GX could not take over its Auto mode, you can now choose Controlled by the Victron GX. The GX takes over Auto only when the charger connects to it over MQTT.
• For Easee, Zaptec, Tinkerforge WARP and Bender chargers, and a KEBA whose phase switching source is not set to Modbus, the Victron GX cannot switch between one and three phases. On a single-phase installation, the GX waits for about 4.1 kW of surplus before it starts charging, until it has seen the car charge on one phase. Choose Battery-powered or Feed-in as the Auto mode there.

Phaeton v0.66.97

• Charging limit in Settings: if the saved charging limit is above the station max current or above the most the charger integration accepts, Settings marks it, and applying a change in Settings first asks for a lower limit, or a higher station max current where that is what limits it. Schedule changes, restoring a backup and the Change charger step keep the saved value, and charging keeps using the lower value, as before.

Phaeton v0.66.93

• On a KEBA P40, the RFID card is shown only when Enable RFID is turned on in the charger's Modbus settings in the KEBA eMobility App.

What changed

Phaeton v0.66.100

• The Victron GX can now take over the Auto mode of Easee, Zaptec, Tinkerforge WARP and Bender chargers, and of a KEBA whose phase switching source is not set to Modbus. These chargers do not report their phases, so Phaeton presents them to the GX as three-phase chargers, as a Victron EV Charging Station does with Multiple relay charging off. The GX then limits the charging power to the phases the car is measured to charge on.

Phaeton v0.66.99

• Tinkerforge WARP, Bender and Mennekes chargers: when charging resumes, Phaeton now sends the charging current twice. Charging behavior is otherwise unchanged.
• Tinkerforge WARP: some charging currents with decimals are now sent up to 0.001 A lower than before, never above the current Phaeton allows. Signing in to a WARP with a password works as before.
• Easee: Phaeton reconnects to the Easee cloud after 30 seconds without a message from it, instead of 45 seconds, so a connection that has gone quiet recovers sooner.

Phaeton v0.66.98

• The Phaeton web pages load faster, especially over a slow or remote connection: Phaeton now sends the page files compressed, so the first visit after an update transfers about a third of the data it did before.
• A browser tab with Phaeton open in the background stops checking for new readings after about ten seconds, so forgotten tabs and phones no longer keep Phaeton busy. When you return to the tab, the charging controls stay locked until Phaeton has confirmed fresh readings again, which normally takes a moment.
• On chargers rated above 25 A, the manual current slider now reaches the charger's full maximum and keeps it after a current change fails. Before, the slider could stop at 25 A even though the range shown went higher.

Phaeton v0.66.97

• The charging limit in Settings can no longer be set above what the charger accepts. Phaeton refuses a value above the station max current or above the most the selected charger integration accepts, so a typo such as 160 instead of 16 no longer lifts the limit. Lowering the station max current below the charging limit asks for a lower limit too. Settings shows the highest allowed value under the field and says which setting decides it.
• Whole-number settings, such as ports, refuse a value with decimals and show "Must be a whole number" instead of quietly saving only the whole part.
• When more than one setting needs a change before your changes can be applied, the bar with Apply changes lists all of them. Choosing one takes you to it, and the cursor moves to the first. A setting with an error now also shows the focus outline while you are in it.
• Settings search puts the cursor in the setting you choose instead of on its question-mark help.
• Settings › Charging shows the settings card of the chosen Auto mode only. Its start thresholds, steps and delays are under Advanced, and search still finds them. With Feed-in, a button shows the Battery-powered settings that apply off-grid. Saved values do not change.
• On the Victron GX page, the choice between MQTT discovery, Legacy Modbus and no GX connection is shown directly in its card instead of under Advanced.
• While Settings has changes that are not applied yet, the Settings item in the navigation shows a dot, also on the other pages. The changes are kept, and the dot goes away once they are applied or discarded.

Phaeton v0.66.96

• The Schedule page no longer undoes a schedule change made on another phone, computer or browser tab. Before, saving from a page opened earlier could silently restore an older schedule, for example switching a charging window back on after someone had switched it off. Now that save is refused, the page shows the current schedule, and you can make your change again.
• When Phaeton refuses a schedule save, the schedule editor now shows the reason, such as a restart in progress. Before, some refusals were shown as saved.
• If Phaeton does not answer a schedule save within half a minute, the editor no longer waits without end. It says it is not known whether the change was saved; reloading the page shows the current schedule.
• Closing the schedule editor with Escape, Cancel or a tap outside it now asks before discarding changes you have not saved.
• The panel for the selected charging window no longer covers the weekend rows of the week, and the edges you drag to change a window's start or end are easier to grab.

Phaeton v0.66.95

• When the Charging page shows readings that are no longer live, the power figure, energy sources and session values turn grey and the page says how old the last reading is, for example "Last reading 42 s ago".
• System › Health no longer shows old values as current after your browser loses contact with Phaeton. Values that cannot be confirmed are marked "Last known", the charger and GX connections read Unknown, and the last poll age keeps counting.
• A Phaeton error now shows in red instead of amber, with a link to the logs. Out-of-date readings and a lost charger connection link to System › Health.
• While the page first loads, the connection badge says "Connecting…" instead of "Offline".
• When Auto mode or a schedule is waiting to start charging, a note beside Stop charging explains that charging is switched on and will start by itself.
• After you press Start charging or Stop charging, the button keeps its label until Phaeton confirms the change, and the message says the change was requested rather than applied. If your device cannot reach Phaeton, the message now says so instead of pointing at the charger connection.
• The next charging window and past sessions on the Charging page now use the installation's time zone, and name it when your browser is in another time zone.
• With no car connected, session time shows "—" like the other session values.
• Screen readers now announce the charging current slider in amps, and the Start charging and Stop charging buttons have play and stop icons.

Phaeton v0.66.94

• The Updates page and the navigation now work on narrow phone screens and with large text. On the Updates page, the cards, buttons and version list stay on screen at a 320 pixel wide screen and at twice the normal text size, and long button labels wrap between words. The navigation bar at the bottom of a phone keeps all five items, including Logout, on screen at large text sizes. The tabs above the System pages wrap onto a second row instead of hiding a tab.
• Text fields and drop-down lists have a clearly visible outline in light and dark mode, in Settings, the schedule editor, sign-in, setup and the log filter, also while a field shows an error. The field you are typing in gets a thicker outline in the accent colour.
• The question-mark help in Settings now opens its explanation right below the setting's name when you press it, without covering the settings below. Press it again or press Escape to close it. This works with a mouse, the keyboard and touch.

Phaeton v0.66.93

• KEBA P30 and P40 chargers with an RFID reader now show the RFID card used for the charging session on the System page, under Charger readback, while a car is connected. Phaeton only shows the card; it does not use it to identify the car. Support bundles leave the card number out.

Phaeton v0.66.92

• Setup now shows each problem right under the field that needs a change and moves the cursor there, instead of one message at the bottom of the step.
• Setup no longer skips the charger silently when its address is left empty. Enter the address, or choose Skip for now to finish setup and choose the charger afterwards.
• Sign-in and setup have a Show button to check the password you typed. The sign-in page also explains how to set a new password if you forgot it.
• Pressing Enter in setup now moves to the next step instead of finishing setup early.
• The setup progress bar marks finished steps with a check, so it no longer relies on colour alone.
• Starting online activation no longer warns that a pop-up was blocked when the portal did open. The activation page explains the steps once and offers Change charger below the activation options.

Phaeton v0.66.91

• The phase choice on the Charging page is now two separate buttons, 1 phase and 3 phases. Tapping the option that is already selected no longer switches the charger to the other phase count; only choosing the other option sends a change. Screen readers announce the choice as a group named Phases with the selected option marked.
• In Auto mode the phase choice now says beside it that Auto sets the phases and that you can switch to Manual or Scheduled to change them.

Phaeton v0.66.90

• Easee, Zaptec, Tinkerforge WARP and Bender chargers, and a KEBA whose phase switching source is not set to Modbus, do not report their phases. Connected to your Victron GX over MQTT, the GX can now start them, set their current, switch them between Manual, Auto and Scheduled and change their Autostart, as it already could over Modbus TCP.

This update includes every change since Phaeton v0.66.86. Read the upgrade notes first: some installations need an action.

Upgrade notes

Phaeton v0.66.88

• For Easee, Zaptec, Tinkerforge WARP and Bender chargers, and a KEBA whose phase switching source is not set to Modbus, the GX over MQTT still cannot start them, set their current, switch them between Manual, Auto and Scheduled, change their Autostart or take over their Auto mode. The GX can stop them and change other settings. Choose Battery-powered or Feed-in as the Auto mode for these chargers.

What changed

Phaeton v0.66.89

• Maintenance release with stricter internal code checks. Charging, your settings and the connection to your Victron GX are unchanged.

Phaeton v0.66.88

• Easee, Zaptec, Tinkerforge WARP and Bender chargers, and a KEBA whose phase switching source is not set to Modbus, do not report their phases. Connected to your Victron GX over MQTT, they now show their status, power and current on the GX and in VRM, as they already did over Modbus TCP. Before, the GX showed them as disconnected at 0 W, even while charging.

Phaeton v0.66.87

• On your Victron GX, Settings no longer offers values that every save changed back without a message. Read solar & battery data and the GX address and port for readings are now shown as fixed, with the reason: Phaeton installed on the GX always reads them from that GX. The charger connection to the GX no longer offers No GX connection, because Phaeton on the GX always keeps a connection to it.
• On a new installation on your GX, and on chargers added under Chargers on this GX, Settings also shows these as fixed, with the reason: the MQTT client ID, the charger device ID, the web port, where the state and log files are kept, and the port, unit ID and model of Phaeton's own Modbus TCP server, which stays off there.
• On the GX, Settings refuses port 502 for Phaeton's own Modbus TCP server, because the GX's Modbus TCP server uses it, and suggests 1502. Before, a save moved it to 1502 without a message.

This update includes every change since Phaeton v0.66.83.

What changed

Phaeton v0.66.86

• On a new installation on your Victron GX, and on chargers added under Chargers on this GX, Settings no longer offers Legacy Modbus or No GX connection. Phaeton installed on the GX always connects to it over MQTT, so saving either choice switched back to MQTT without a message. The Victron GX settings now show the connection as MQTT discovery and say why. How Phaeton connects to the GX is unchanged.

Phaeton v0.66.85

• Maintenance release. Phaeton no longer saves a charging value that it has not used since an earlier update. Your settings, Mode, Start/Stop, charging current and energy total load as before after the update, and charging is unchanged.

Phaeton v0.66.84

• The help for Off-grid stop at battery charge now says that, off-grid, charging starts again only once the home battery is at least 2% above that level and has reached Start at home battery charge. How Auto charges is unchanged.

This update includes every change since Phaeton v0.66.80. Read the upgrade notes first: some installations need an action.

Upgrade notes

Phaeton v0.66.81

• If you open Phaeton through your own reverse proxy at an unencrypted address, or through VRM or another proxy on an older iPhone, iPad or browser, saving changes can now be refused. Add the start of the address you open Phaeton at, from the https or http at the front, with its colon and two slashes, up to and including the host name and any port number, but nothing after it, under Settings, System, Access, Advanced, Allowed CORS origins. Or use an up-to-date browser on an encrypted address. If that address changes, add the new one.

What changed

Phaeton v0.66.83

• With the dummy adapter, the automatic phase switching check now passes. It no longer logs a warning at every start that the charger could not be switched back.

Phaeton v0.66.82

• When Phaeton runs on a computer other than the Victron GX, setup no longer fills in this computer's own address as the GX address; the field stays empty for the address of your GX.
• Change charger no longer asks you to pair with the GX when Phaeton is already paired with the GX entered in setup.

Phaeton v0.66.81

• Another website you visit can no longer change Phaeton's settings, upload an update or control charging through a password your browser saved for Phaeton. Phaeton now accepts changes from a browser only when they come from its own pages, or from a website you listed under Allowed CORS origins in the Access settings. Apps and scripts that talk to Phaeton directly work as before.

This update includes every change since Phaeton v0.66.67. Read the upgrade notes first: some installations need an action.

Upgrade notes

Phaeton v0.66.78

• If Phaeton runs on its own device and you want the Victron GX to take over Auto charging, pair them: in Settings, choose the Auto mode Controlled by the Victron GX on the Charging page (if it is already chosen, choose MQTT discovery in the Advanced part of Charger connection to GX on the Victron GX page instead), enter the GX address as the GX broker address on the Victron GX page, apply the changes and choose Pair with GX. Then on the GX open Settings, Integrations, MQTT Devices and activate Pairing mode, or press the button on the GX twice. Pairing needs Venus OS 3.80 or later. After pairing, MQTT Access on the GX can be set to Paired devices only.

Phaeton v0.66.77

• Tools that upload older update packages without the web interface must now confirm the downgrade. The web API documentation describes how.

Phaeton v0.66.75

• If Phaeton cannot recover the administrator account of a device that was set up before, finishing the setup wizard first needs a file created over SSH on the GX. The wizard shows the exact command.
• If you set a custom log file or state file location outside Phaeton's data folder, Phaeton uses the default location again after updating and shows a notice in Settings. The state file keeps your charging preferences, which then start from their defaults once.
• If Settings, Logging, Backups was set below 2, Phaeton keeps 5 log files again after updating. A setting of 0 kept every log, so at its first start Phaeton removes the older logs and keeps only the newest few.
• If Phaeton updates from a private release repository and you change its address, enter the access token again in Settings.

Phaeton v0.66.74

• Phaeton on a computer other than the Victron GX: the Auto mode Controlled by the Victron GX works only when Phaeton runs on the GX itself or is paired with it, because current Venus OS versions accept a charger's MQTT messages only from the GX or from a paired device. If the GX does not show your charger, pair Phaeton with the GX on the Victron GX page in Settings (Venus OS 3.80 or later). Without pairing, choose Legacy Modbus in the Advanced part of Charger connection to GX on that page, add Phaeton in the GX's Modbus Devices settings, and choose the Auto mode Battery-powered or Feed-in.

Phaeton v0.66.72

• Phase switching: with Multiple relay charging on, a charger whose switching Phaeton has not seen yet changes its phases once and back while it is idle after the update. Nothing charges during the check.

What changed

Phaeton v0.66.80

• The Logs page, log downloads and support bundles always show the log file Phaeton is writing, also after it continued in a new file because the previous one reached the maximum size set in the Logging settings.

Phaeton v0.66.79

• Licenses activated online include a daily check-in with the Phaeton portal, as the license terms describe for online activation. Phaeton now sends it for every license that includes it. Charging never depends on the check-in: Phaeton keeps running when the portal cannot be reached. Licenses activated offline do not check in.
• When the device clock was behind at startup, Phaeton could stop checking in with the portal until its next restart. It now keeps its daily check-in. A check-in the portal received is also no longer repeated every hour when the device cannot save its time.

Phaeton v0.66.78

• When Phaeton runs on its own device, it can now pair with a Victron GX over MQTT the way a Victron EV Charging Station does. Current Venus OS versions accept a charger's MQTT messages only from the GX itself or from a paired device, so pairing lets the GX show the charger and take over Auto charging. Once paired, every connection to the GX is encrypted and signs in with Phaeton's own access key from the GX, so the GX no longer needs to allow unencrypted MQTT on your network.
• Pairing remembers the GX's security certificate. Phaeton does not connect when another device answers in the GX's place, and Settings says so.
• Settings shows a warning when Phaeton connects over MQTT to a GX on another device without encryption, and when the GX no longer accepts Phaeton's access key. Installations where Phaeton runs on the GX itself work as before.

Phaeton v0.66.77

• An update package you upload that is older than the installed version now asks you to confirm before anything is installed. The question names both versions. Reinstalling the version you already run needs no extra confirmation. A package without a version number, such as a preview build, asks the same way.
• After you sign in, Phaeton always takes you to a page on the device itself.
• If the sign-in or setup page cannot load completely, for example while the GX restarts, the password you typed is no longer added to the page address.
• The web interface now runs only scripts that come from the device itself.
• After an update, the sign-in page always loads its new version instead of an older copy your browser kept.

Phaeton v0.66.76

• Phaeton stays in control when a device on your network keeps changing charger settings over Modbus or MQTT very quickly. Stop and start commands, and changes made on the Charging page, still take effect at once. When changes arrive faster than Phaeton can apply them, it applies the latest value of each setting.
• Settings changed from the Victron GX are saved right away. When they change again within a few seconds, Phaeton saves the latest values a few seconds later, which spares the storage of your device.
• The Victron GX keeps its Modbus connection to Phaeton when other devices on the network open many connections, and the Modbus server keeps running after a temporary network or system error. Modbus connections that send no request for two minutes are closed; the GX and most Modbus tools reconnect by themselves.
• Connections and repeated requests from other devices on your network no longer add lines to the Phaeton log each time. The details remain available when you switch the Logs view to debug.
• The maximum log file size in the Logging settings now takes effect. When the log file reaches it, Phaeton continues in a new file and keeps as many files as the Backups setting allows, which limits the space the log takes.

Phaeton v0.66.75

• Sign-in protection now also covers apps and scripts that send a username and password with every request. After five wrong passwords from one address, further attempts from that address wait a few seconds, at most about half a minute, before they are checked again. Sign-ins through the GX Control Panel share one such wait.
• Checking passwords no longer slows down charging control, also when many sign-in attempts arrive at once.
• When its settings cannot be read, for example after a damaged file or a return to an older version, Phaeton keeps your administrator account and starts in configuration recovery. It no longer offers first-time setup to whoever opens it first.
• While first-time setup is waiting, no account can sign in; only the setup wizard opens.
• Phaeton keeps a private copy of the administrator account next to its settings, so the account also survives a settings file that cannot be read at all.
• An update that comes up without the settings or account your Phaeton ran with before is rolled back automatically, like an update that does not start.
• Custom locations for the log files and the state file must now be inside Phaeton's own data folder, and log downloads and support bundles only include the log files Phaeton writes there.
• For updates from a private repository, the access token is now sent only over a secure connection to that repository's own server, and changing the repository clears the saved token.

Phaeton v0.66.74

• When Phaeton runs on a computer other than the Victron GX, setup now starts from the Auto mode Battery-powered and explains how to connect the charger to the GX after setup. Setup on the GX is unchanged.
• On a computer other than the Victron GX, Change charger now keeps a working Legacy Modbus connection: if the Auto mode was Controlled by the Victron GX, Change charger starts from Battery-powered, which is how the charger already charged over Legacy Modbus. You can still choose Controlled by the Victron GX.

Phaeton v0.66.72

• Phaeton now checks by itself that your charger switches between one and three phases. With Multiple relay charging on, it changes the phases and back while the charger is idle, without charging. You no longer switch phases by hand before the Victron GX can choose one or three phases. Settings shows the result.
• Phaeton now remembers that check for Peblar and go-e chargers too, as it already did for Alfen, so it does not repeat after a restart. A KEBA charger is checked while no car is plugged in.
• When the charger refused a phase change, or did not take a phase change three times in a row, Phaeton keeps checking while the charger is idle and switches phases again by itself once the charger does.

This update includes every change since Phaeton v0.66.56. Read the upgrade notes first: some installations need an action.

Upgrade notes

Phaeton v0.66.67

• Inverter temperature protection is on after updating. If your inverter reports high temperature warnings, charging now slows to the minimum current while they last. You can turn it off under Settings, Charger & installation, Inverter protection.
• To use overload protection, check that the wiring position under Settings, Charger & installation, Inverter protection matches where the charger is connected, set the input current limit when it sits on the AC input, then turn overload protection on. Both protections need the solar & battery readings from the GX.

Phaeton v0.66.65

• Phaeton installations that switched phases automatically keep doing so: Multiple relay charging is on and Auto mode phase is One or three phases. The waiting times you had keep their values. Auto now compares the charger's own power with 4,800 W and 4,300 W.
• On one phase a charger delivers about 230 W per ampere, 3,700 W at a 16 A charging limit, so with the default thresholds Auto does not switch to three phases. To let Auto switch, lower Three phases above and One phase below in Settings, Charger & installation, Phases, below what one phase delivers.
• Phaeton installations with automatic phase switching turned off keep the phases last chosen on the Charging page in every mode: Multiple relay charging is on and both the Manual and Auto mode phases are set to that choice. Auto now moves to those phases when a session starts.
• New installations start with Multiple relay charging off, as a Victron EV Charging Station does.

Phaeton v0.66.64

• With Auto mode Controlled by the Victron GX, charging no longer stays stopped after the GX hands control back: Battery-powered Auto continues by itself. Stop charging on the Charging page if it should stay off.
• A pause by the GX no longer switches Start/Stop to stopped. A lost connection to the GX, stale charger readings, an interrupted phase change and a restart still stop charging and end GX control.

Phaeton v0.66.63

• Auto mode now waits 30 seconds before it starts, and longer after short sessions, and steps the current gradually instead of jumping to the available solar power. Charging also starts at the minimum current.
• Battery-powered and Controlled by the Victron GX now start only when the home battery is at the start level and leave the home battery its share of the solar power first. Your start level is kept; if you had cleared it, it is now 90%. Check the start level under Settings, Charging, Solar, battery & grid after updating.
• On the grid, Auto mode no longer stops charging at a battery level: your stop level now applies only off-grid, as on a charging station, and the ESS minimum state of charge of the Victron GX is no longer used. On the grid, Auto mode lowers the current when the home battery discharges and stops after the stop delay or the battery or grid power time.
• The Auto mode settings "Continue when solar drops" with its duration, "Allow grid top-up with solar" and the start threshold overrides move to the matching new settings with their values. "Continue when solar drops" becomes "Use battery or grid power", and its duration is now set in whole minutes, at least 5. "Allow grid top-up with solar" becomes "Charge on a small solar surplus", which now also needs "Use battery or grid power".
• If you had turned on "Allow Auto mode without battery SoC" and Phaeton managed Auto mode, Auto mode now uses Feed-in, which charges from solar power sent to the grid and needs no battery readings. With Controlled by the Victron GX, the option is switched off and the Auto mode stays, so without battery readings Auto mode charges only while the GX controls it; if there is no home battery, choose Feed-in. Check the Auto mode under Settings after updating.
• The settings for PV excess smoothing and the Victron low battery limit are removed. A charging station has no equivalent for them. Automatic phase switching now follows the solar surplus without smoothing; its pending delay still prevents switching back and forth.
• New installations allow battery or grid power for up to 30 minutes when the solar surplus drops, as a new charging station does. Existing installations keep their previous choice.
• Feed-in now starts once the grid exports more than 500 W, or more than 1,400 W for a car that charges on more than one phase, unless you had set your own start thresholds.

Phaeton v0.66.61

• Installations where the Victron GX managed charging now use the Auto mode Controlled by the Victron GX. Installations where Phaeton managed charging now use Battery-powered. Check the Auto mode on the Charging page of Settings after updating.
• If Phaeton runs on a separate device and connects to your Victron GX over MQTT, it now waits about 17 seconds after starting before it connects to the GX, so the GX registers the charger again and shows its current readings.

Phaeton v0.66.60

• Phaeton cannot install Victron EV Charging Station firmware. If VRM offers such an update for a Phaeton charger, skip it; Phaeton updates come through the Phaeton app.
• For a Phaeton charger connected over Modbus, when it has no VRM Control Panel access or Phaeton runs on a computer other than the GX, VRM can still offer a Victron charger firmware update and may not report it as failed. Nothing is installed on Phaeton.

Phaeton v0.66.57

• Easee: if your Victron GX is connected to Phaeton over Modbus, after this update the GX may not show an idle Easee charger for up to an hour, until the Easee cloud next reports its total energy. Charging is not affected.

What changed

Phaeton v0.66.67

• Phaeton now protects your Victron inverter the way a Victron EV Charging Station does, in every charge mode.
• Inverter temperature protection is new and on by default. While the inverter reports a high temperature, the charger keeps charging at the minimum current, and returns to its current 1 minute after the last report. As on a charging station, Feed-in Auto mode follows the grid export instead.
• Overload protection is new and off by default, as on a charging station. When the charger sits on the inverter's AC output, charging follows the inverter's overload warnings. When it sits on the inverter's AC input, each phase is kept below the input current limit, 15 A unless you change it. An overload drops charging to the minimum current at once, pauses it after 5 seconds, and lowers the current by 20% for 5 minutes. An overload alarm from the inverter pauses charging at once. Charging starts again by itself 10 seconds after the overload has passed.
• While overload protection holds charging, the Charging page and the Victron GX show Connected, and the Charging page explains why. A start command during that time is refused. Over an MQTT connection, the Victron GX also shows the overload and high temperature warnings of a charging station.
• Settings, Charger & installation, has a new Inverter protection card with these settings and the wiring position, which moved there from Victron GX. The Victron GX can read and change these settings too.
• Without readings from the GX, or when no inverter answers, these protections do not act. On the AC input, overload protection needs only the grid readings.

Phaeton v0.66.66

• Uninstalling Phaeton, or removing a charger from Chargers on this GX, now says what happens to its license: a reinstalled Phaeton needs a new activation, and when it was activated online, the license portal recognizes the same GX and moves the license without counting a device replacement.

Phaeton v0.66.65

• Phaeton now switches between one and three phases the way a Victron EV Charging Station does. The phase settings are in Settings, under Charger & installation, Phases: Multiple relay charging, Manual mode phase, Auto mode phase, the switch thresholds and times, with the charging station's defaults. The Victron GX can read and change them.
• With Auto mode phase One or three phases, every Auto session starts on one phase. Auto switches to three phases when the charger's own power stays above 4,800 W, and back to one phase below 4,300 W, no sooner than 60 seconds after the start or the last switch. It no longer switches on the solar surplus.
• Every phase change stops charging, waits until the charger confirms that no current flows, changes the phases, checks them and starts again; in Auto at the minimum current. The Charging page, the Victron GX and VRM show Switching to 3 phases or Switching to 1 phase meanwhile.
• The phase choice on the Charging page sets the Manual mode phase, used in Manual and Scheduled. Changing it while charging stops charging, switches and starts again.
• When the Victron GX controls Auto charging, it chooses the phases only with Multiple relay charging on and Auto mode phase One or three phases. With a fixed Auto mode phase the charger uses that phase count, once Phaeton has seen it switch; otherwise it stays on its phases.

Phaeton v0.66.64

• When the Victron GX controls Auto charging, the charger now follows the GX the way a Victron EV Charging Station does. A request outside the charger's limits charges at the nearest limit instead of ending GX control, and a phase count the charger cannot switch to is ignored.
• When the GX pauses charging, the Victron GX and VRM now show Waiting for sun, or Low SOC when the GX pauses for the home battery, instead of Waiting for start. Phaeton's Charging page shows Paused by GX, as before.
• When the GX stops sending charging commands, the charger keeps charging at the minimum current for up to 2 minutes, then waits for the GX, instead of stopping at once.
• When the GX hands Auto control back, the charger continues with its own Auto mode from the present current instead of stopping. When charging was paused, it starts again after the usual start delay.

Phaeton v0.66.63

• Auto mode now charges exactly like a Victron EV Charging Station. Feed-in follows the power your system exports to the grid and adjusts the current in 0.2 A steps. Battery-powered charges from the solar surplus while your home battery keeps its share, and adjusts in 1 A steps. Controlled by the Victron GX charges as Battery-powered until the GX takes over, and every Auto mode charges as Battery-powered when the system runs off-grid.
• Charging now starts after a short start delay of 30 seconds once the conditions hold. After repeated short sessions the delay grows, up to 4 minutes, so charging does not switch on and off all day. A start command or a car plugging in starts charging at once when the conditions already hold.
• At the minimum current, charging stops after a stop delay of one minute, or after the battery or grid power time when using battery or grid power is allowed.
• The dashboard and the Victron GX now count down to a start and to a stop, and explain which condition Auto mode is waiting for, such as the solar surplus, the grid export or the home battery charge.
• Settings has new cards for the Auto mode settings of a charging station, with the charging station's defaults: Solar, battery & grid for the shared settings, and Battery-powered and Feed-in for each algorithm. The Victron GX can read and change these settings too.
• Auto mode no longer uses the ESS minimum state of charge of the Victron GX, as a charging station does not.

Phaeton v0.66.62

• The Phaeton dashboard now names a fault that a go-e, KEBA, WARP or Bender charger reports, such as a residual current, a welded contact or a charger error.
• When a go-e or WARP charger names the cause of its fault, Phaeton passes it to the Victron GX as a Victron EV Charging Station does: as an alarm such as residual current, missing earth, welded contacts or over temperature on a GX connected over MQTT, and as the matching fault status over Modbus. A charger error without a named cause shows on the dashboard only.
• On a Victron GX connected over MQTT, Phaeton now raises the charging station's GX communication warning when it has received no solar, grid and battery data from the GX for more than two minutes, and the initial setup warning while setup or activation is not finished. With either connection, the dashboard also tells you when the GX data is missing.
• The charging status now shows Charged when the vehicle is connected but no longer takes the power offered, and Stopping right after you stop a charging session until the vehicle stops drawing power.
• The support bundle lists the active charger alarms and warnings.

Phaeton v0.66.61

• The setting "Charging managed by" is replaced by Auto mode, the same choice a Victron EV Charging Station offers: Feed-in, Battery-powered or Controlled by the Victron GX. New installations start with Controlled by the Victron GX, as a new charging station does.
• With Controlled by the Victron GX, the charger now charges with Phaeton's solar, battery and grid preferences until the GX takes over, for example with Opportunity Loads, instead of waiting at zero. When the GX hands control back, charging stays stopped until it is started again, as before.
• In this version, Feed-in and Battery-powered both charge with Phaeton's solar, battery and grid preferences.
• The Victron GX can now change Mode, Start/Stop, the charging current and AutoStart over an MQTT connection without a separate setting, as with a Victron EV Charging Station. It can also read and change the Auto mode over MQTT and Modbus. Over Modbus it can choose only Feed-in or Battery-powered, as on a charging station.
• The Victron GX takes over Auto mode only when the Auto mode is Controlled by the Victron GX and the charger connects to the GX over MQTT.

Phaeton v0.66.60

• VRM's firmware update list for your Victron GX now also shows a Phaeton charger that is connected over MQTT with VRM Control Panel access, as it shows a Victron EV Charging Station.
• If VRM offers a Victron charger firmware update for a Phaeton charger with VRM Control Panel access, VRM now reports the upload as failed straight away. Nothing is installed or kept, and Phaeton's own updates are unchanged.

Phaeton v0.66.59

• When Phaeton connects to your Victron GX over MQTT, it now reads the solar, grid and battery data for Auto mode from the GX over that same connection, the way a Victron EV Charging Station paired over MQTT does. These installations no longer need the Modbus TCP service on the GX for Auto mode, and the GX address and Modbus port for solar and battery readings are no longer used.
• Over MQTT the inverter information in the support bundle shows the GX system state, and the overload warning of a Multi RS is not available, as on a Victron EV Charging Station.
• The setup wizard no longer asks for the GX Modbus address for solar and battery readings when Phaeton connects to the GX over MQTT.

Phaeton v0.66.58

• Phaeton now reads solar, grid and battery data from your Victron GX the way a Victron EV Charging Station does: once a second over one connection, with the same waiting times when the GX is slow to answer.
• A single missed reading no longer stops charging in Auto mode. If the GX data is late, Auto mode keeps the charging current as it is; after two minutes without data it stops charging and shows "Waiting for GX data" instead of a low battery message. Charging starts again by itself when the data returns.
• Phaeton also finds the Victron inverter on the GX, as a charging station does, and shows its state, input current limit and overload and temperature warnings in the support bundle. Charging does not act on these values yet.
• Solar power from inverters connected to a generator input is no longer counted as solar surplus, as on a Victron EV Charging Station.
• The "Maximum data age" setting under Solar & battery readings is removed. It had no effect.

Phaeton v0.66.57

• When your Victron GX manages charging over MQTT, it can now also change the charger's name, minimum current, maximum current and wiring position, as it can on a Victron EV Charging Station. Name and minimum current changes made on the GX, over Modbus or MQTT, are saved and kept after a restart, and the GX now shows the minimum current set in Phaeton.
• When you change the charging limit in Phaeton, a Victron GX connected over MQTT now shows the new limit as its maximum current straight away and lets you set the charging current up to it. Before, the GX kept the limit from when Phaeton started and refused higher currents with a communication error.
• Over MQTT, Phaeton now confirms its connection to the GX every 4 seconds, as a Victron EV Charging Station does. This leaves more room for network delays before the GX shows the charger as disconnected.
• Over Modbus, the charger's total energy counter no longer reads zero right after Phaeton starts, so VRM cannot count the whole counter as new consumption. On a new installation, and once after this update, the GX finds the charger when Phaeton has read its energy counter, usually within seconds of starting.
• Saving a charging schedule no longer undoes settings changed on the GX while the schedule page was open.

This update includes every change since Phaeton v0.66.52.

What changed

Phaeton v0.66.56

• Charging, Auto mode, settings, and the connection to your Victron GX and VRM are unchanged.

Phaeton v0.66.55

• Easee: the charger's total energy now rises during a charging session instead of waiting for the Easee cloud's hourly update, so charged energy shows up in Phaeton, on the GX and in VRM sooner.
• KEBA: when Phaeton switches between one and three phases while charging is off, it now switches charging off again two seconds later. Some P30 x-series chargers otherwise allowed charging again after the phase change.
• KEBA, Bender and Mennekes: a reading that fails because the charger closed the connection is now retried once straight away on a new connection, instead of failing that reading.
• Bender and Mennekes: a meter reading that the charger marks as unavailable, for example while it restarts, is no longer shown as a real power or energy value.
• Mennekes AMTRON 4You and 4Business: setup now skips the user ID reading, which these chargers do not support, and reads their protocol version instead.

Phaeton v0.66.54

• On a Victron GX running a recent Venus OS 3.90 beta, Phaeton connected over MQTT now appears as a charger. That beta did not show it before. Victron GX devices on earlier Venus OS versions are unaffected.

Phaeton v0.66.53

• Updated the TLS security library and other built-in components with their latest security fixes. Charging, settings, and the connection to your Victron GX are unchanged.

What changed

• Opportunity Loads reconnects after switching from Manual or Scheduled mode back to Auto, so charging can resume under Victron GX control without waiting for the old session to time out.
• Updated the TLS security library and replaced the discontinued YAML library with its maintained successor. Existing settings remain supported.

This update includes every change since Phaeton v0.66.7. Read the upgrade notes first: some installations need an action.

Upgrade notes

Phaeton v0.66.51

• Uninstalling deletes the settings, administrator account, license and charging history from the GX and cannot be undone. Make a backup first if you may want them again.
• Take out a Phaeton USB installer stick before uninstalling. A stick with the installer installs Phaeton again when the GX restarts, so Phaeton refuses to uninstall while one is inserted.
• Remove any other chargers added on the same page first. Phaeton uninstalls only when it is the last charger on the GX.

Phaeton v0.66.50

• A manual stop still shows "Waiting for start", and Phaeton's own reasons to hold charging, such as a low home battery, a closed charging window or waiting for solar surplus, keep their usual status while they apply.

Phaeton v0.66.49

• No action is required for a KEBA without a phase switch on contact X2; it behaves as before.
• For a KEBA with a phase switch, set its phase switching source to Modbus in the charger, then enable automatic phase switching in Phaeton's settings if you want it.
• Phase switching on KEBA has not been tested on a physical charger yet. If a switch cannot be confirmed, Phaeton keeps charging on one phase and reports the failed switch.

Phaeton v0.66.48

• If a KEBA P30 does not report its charging state when Phaeton starts, Phaeton asks again on the next poll, as it already does for its other startup readings.

Phaeton v0.66.47

• Putting the previous version back after a failed update applies to updates made from this version onwards, not to the update that installs this version.
• Putting the previous version back after a failed update covers installations made with the GX installer or USB stick. Other installations keep the previous version for manual recovery.
• If the GX restarts while an update is still being checked, the check continues after the restart only on installations set up or reinstalled with this version's installer or USB stick.

Phaeton v0.66.43

• If you use a Peblar charger and upgrade from Phaeton 0.66.17 or earlier, enable Modbus ReadWrite access and a zero-current fallback on the charger, then enter its address and port in Settings and restart. Your other settings are kept.

Phaeton v0.66.42

• Before this version, a car charging on an Easee charger below its maximum current in Auto or Scheduled mode could stay paused after a short drop in the Easee cloud connection, or after Phaeton restarted or was updated. That no longer happens.

Phaeton v0.66.41

• Turning the light blue turns off any basic or weekly charging plan set in the Easee app, and setting a plan there turns the light white again. Use one or the other.
• If you turn the setting on and later go back to an earlier Phaeton version, turn it off first. Earlier versions do not recognise it.

Phaeton v0.66.26

• If automatic phase switching is enabled on a WARP3 charger, turn it off in the charger's web interface to let Phaeton control the charging current.

Phaeton v0.66.21

• Set the go-e app's phase switching to one or three phases before using phase switching in Phaeton. While the charger chooses the phases itself, Phaeton leaves that choice alone; automatic charging asks again on its next attempt and a manual phase change can be repeated, so switching starts working once the app setting changes; no restart is needed.

Phaeton v0.66.19

• After Phaeton starts or updates, a Peblar charger can take up to ten minutes before charging resumes, because Phaeton cannot see how often the charger paused before it started.
• Phaeton counts a stop even when the charger's reply to it is lost, because the stop may still have happened. If that occurs while two other stops are less than ten minutes old, the next resume waits until the oldest of them is ten minutes old. Stops that never reach the charger, for example while it is unreachable, do not count.

Phaeton v0.66.18

• On your Peblar charger, enable Modbus ReadWrite access and a zero-current fallback, then confirm its address and port in Settings. Existing Peblar REST connections remain stopped until you complete this setup.

What changed

Phaeton v0.66.51

• Phaeton can now be uninstalled from its own web interface. Open System, then Chargers on this GX, expand this charger and choose Uninstall Phaeton. Phaeton stops, removes its VRM Control Panel access and its automatic start, and deletes its files from the GX. The GX drops it from its device list within a minute.
• For installations where the web interface cannot be opened, the same removal is available as a terminal command on the GX. The user guide describes it.

Phaeton v0.66.50

• When a vehicle is plugged in but the charger is waiting for an RFID card or app authorization, the Victron system now shows "Waiting for RFID" and Phaeton's dashboard shows "Waiting for authorization", with an explanation of why charging has not started. Before, this looked like a connected vehicle that simply was not charging.
• Supported chargers: go-e (local API v2), KEBA P30 and P40 models with an RFID reader, WARP when its user authorization is on and no charging current has been released yet, and Easee.

Phaeton v0.66.49

• KEBA P30 and P40: Phaeton can now switch between one and three phases, manually or automatically, when the charger has a phase switch on contact X2 controlled over Modbus. Phaeton confirms each switch by reading the charger's phase state back.
• KEBA with a phase switch: when charging stops, the charger returns to one phase, which saves the switch's standby power while it is idle. When charging resumes with three phases selected, Phaeton first switches back to three phases. In automatic mode, the solar planner decides again as usual.
• All chargers with phase switching: a manual change between one and three phases made while charging now completes. Phaeton pauses charging, waits for the charger to settle, switches, and then resumes. Before, charging could resume on the old phase count and the change was dropped.

Phaeton v0.66.48

• KEBA P30: after Phaeton allows charging and the car is then unplugged, the status page no longer says that the charger is blocking charging. The P30 reports the same state for "no car" and "not allowed", so Phaeton now remembers what it last told the charger.
• KEBA P30: at startup Phaeton also reads the charger's charging state. A charger that is paused at startup shows as blocking charging, and any other charger shows as permitting charging, until Phaeton next starts or stops charging.

Phaeton v0.66.47

• GX: when Phaeton installs an update, from the Updates page or automatically, and the new version does not start within three minutes, Phaeton now puts the previous version back and starts it again. A version waiting for setup, activation or a settings repair counts as started, so it is not rolled back. The log names the version that failed and the version restored.
• This only happens right after an update. Ordinary restarts and reboots never roll back. If the GX restarts three times before an update could be checked, for example because the new version keeps restarting it, the previous version is put back as well.
• Automatic updates do not install a version that was rolled back on this device again. You can still install it yourself from the Updates page.
• While a new version is still being checked, another update waits: the Updates page asks you to try again in a few minutes, and automatic updates try again later.

Phaeton v0.66.46

• If you choose to share product diagnostics, Phaeton now reports the Venus OS version family of your GX on release versions of Venus OS, for example 3.80. Before, it was always reported as unknown on a GX. No other information is added.

Phaeton v0.66.45

• The GX, VRM and the GX dashboard now show the charging power for chargers that report only their total power and not the power per phase. When the GX was connected to Phaeton through MQTT, these chargers were shown at 0 W while charging, even though current, voltage and energy were correct. This affected KEBA, WARP, Zaptec, Bender, Peblar and Easee chargers, and Alfen chargers that do not report power per phase, which the GX showed at 0 W from version 0.66.12 onward.
• For those chargers, Phaeton divides the measured total power over the phases by each phase's share of the load, so the total on the GX matches the charger's own reading. The Phaeton dashboard still shows power per phase only when the charger reports it.

Phaeton v0.66.44

• Maintenance release. Phaeton's automated checks now load the settings and saved state written by the previous public release, Phaeton 0.66.7, for every supported charger type, and confirm that an upgrade keeps them. Charging behaviour and settings are unchanged.

Phaeton v0.66.43

• Peblar: after an upgrade from a version that used the charger's REST connection, the dashboard and the System page now say that the Peblar connection needs updating and that your other settings were kept. They no longer say that Phaeton started with safe defaults.
• Peblar: the setup message now says plainly that, until the new connection is saved and Phaeton restarts, Phaeton does not control the charger and the GX shows no readings from it.

Phaeton v0.66.42

• Easee: a charging car is no longer paused when the connection to the Easee cloud briefly drops and returns, for example when Phaeton renews its sign-in, or when Phaeton restarts or is updated. Readings stay valid for their normal age while the connection comes back, as in the reference implementation Phaeton is verified against.
• Easee: Phaeton sends no stop before the Easee cloud has reported the charger's state after Phaeton starts.
• Easee: an outage longer than the maximum reading age still stops charging, with one pause sent to the charger.

Phaeton v0.66.41

• Easee: a new Smart charging light setting, off by default. When it is on, the charger's light turns blue in Auto and Scheduled mode, when Phaeton decides when to charge, and white in Manual mode. It is in setup and in the charger settings, under Advanced.
• The light only shows the mode. Phaeton still controls charging the same way in every mode.

Phaeton v0.66.40

• Bender: setup no longer asks Mennekes AMTRON 4You and 4Business chargers for battery and smart-vehicle information. Their firmware is known to close the connection on these requests instead of declining them, which would make setup fail.

Phaeton v0.66.39

• Zaptec: Phaeton now keeps its minimum pause between requests to the Zaptec cloud as the cloud sees it, even when a request is delayed on the way, including sign-in requests. Previously a slow request could leave a shorter pause before the next one.
• Easee: the same pause is now also kept after a request that was cancelled before it finished.

Phaeton v0.66.38

• Easee: the minimum gap between requests to the Easee cloud now also counts from when the previous request finished. On a busy system a request that left late could otherwise be followed by the next one sooner than intended.

Phaeton v0.66.37

• Easee: when no car is connected, the charger's power now reads 0 W. At the end of a session the Easee cloud can report the last charging power and 0 W at the same moment and keep repeating the old power afterwards. Phaeton could briefly show that phantom power and count it when working out how much solar power was spare. When the two values arrive together, the lower one is now kept.
• Easee: power is no longer shown while the charger is offline, in an error state or reports an unknown state, because it cannot be told apart from an outdated value.
• Easee: an unreadable or negative power or current value now makes only that reading unavailable until a valid one arrives. Previously Phaeton dropped its live connection, which blanked every reading and could keep reconnecting while the cloud repeated the same value.
• The automated Easee verification now also covers these cases, a lost reply to a command, a cloud request to reconnect, connection keep-alive, a silent connection and session meter records.

Phaeton v0.66.36

• WARP2 Pro and WARP3 Pro chargers are now set up as soon as Phaeton starts or the charger settings are saved, instead of at the first reading. The charger's model, features, automatic phase switching and external control are checked right away. If setup fails, Phaeton keeps retrying as before.
• The WARP connection test now says why setup failed, for example when automatic phase switching is still on, the password is rejected, the charger does not answer at its address, or the address belongs to a device that is not a WARP2 Pro or WARP3 Pro.
• The automated WARP verification now also covers chargers whose meter does not report every value, charging commands the charger rejects or does not answer, and the first reading after setup.

Phaeton v0.66.35

• go-e chargers: Phaeton now uses the charger's power, current and voltage readings only when the charger reports the complete set of meter values described by go-e. A reading with a different number of values is now shown as unavailable instead of being interpreted by position. As with any other missing reading, Phaeton allows no charging current until complete readings return. The reference implementation Phaeton is verified against reports such a reading as zero power.
• The automated go-e verification now also covers the lowest and highest charging currents, vehicles that are not connected or have finished charging, firmware 60 and later, a lost connection, a timed-out reading, a setting whose reply is lost, a change on the charger within a second of the previous reading, and a lost first reading after start.

Phaeton v0.66.34

• If you finish online activation in another browser tab and then return to the activation page, it now opens the dashboard without checking with the licensing portal again, even when the device responds slowly.

Phaeton v0.66.33

• The Schedule page now names the time the known VRM prices end instead of always saying "next 3 days". VRM often publishes prices for less than three days ahead, so no eligible period may simply mean the prices are not known yet.
• The Charging page does the same in Scheduled mode when a window with a price limit is waiting for prices that are not published yet: it says no charging window is known before the time the VRM prices end. While charging is already waiting for a lower price or for price information, it keeps showing that instead. When no window depends on missing prices, both pages still say nothing is available in the next three days.
• Hovering, touching or using the arrow keys on the Schedule page price chart shows each hour's price, its quarter-hour price range and how much of the hour the saved rules allow.

Phaeton v0.66.32

• Easee: when the charger's clock runs a few seconds ahead of Phaeton's, its readings are now accepted as current instead of being discarded, so charging control no longer stalls on small clock differences.
• Easee: a stop is now sent even while the live connection to the Easee cloud is interrupted. Phaeton sends one stop per interruption and reports it as unconfirmed, because the charger cannot confirm it until the connection returns; after that, stops are confirmed as usual. Raising or resuming charging still waits for fresh readings.
• The automated Easee verification now runs setup, charging limits, stop, resume and start, command confirmation, reconnection and sign-in renewal against the reference implementation Phaeton is verified against. Where Phaeton deliberately differs, for example by refusing to resume below the charger's maximum current, that behaviour is checked separately.

Phaeton v0.66.31

• When the charger cannot be reached, the log now shows one warning when the problem starts, a reminder every ten minutes while it lasts, and one message when the connection is back, instead of a warning every few seconds. This applies both to setting the charging current and to the regular keep-alive Phaeton sends to Alfen chargers.

Phaeton v0.66.30

• The automated Bender verification now also covers CC613 controllers, the lowest and highest supported charging currents, fractional currents, and currents below or above the supported range. Each is compared with the reference implementation Phaeton is verified against.
• The verification also records how Phaeton handles Bender-based chargers outside its supported range. Setup refuses controllers that use the older register layout and controllers that do not report a model name. Mennekes AMTRON 4You and 4Business chargers are not yet supported, and setup may not complete on them. Charging behaviour for supported Bender controllers is unchanged.

Phaeton v0.66.29

• The automated go-e verification now runs setup, charging limits, stop and resume, phase switching and recovery from failed readings against the reference implementation Phaeton is verified against. Where Phaeton deliberately differs, for example by reading more of the charger's state before acting or refusing to leave automatic phase mode by itself, that behaviour is checked separately.

Phaeton v0.66.27

• The automated WARP2 Pro and WARP3 Pro verification now runs setup, charging limits, stop and resume, the live reading stream and its reconnection against the reference implementation Phaeton is verified against. Where Phaeton deliberately differs, for example by refusing new charging current while automatic phase switching is on instead of changing that charger setting, that behaviour is checked separately.

Phaeton v0.66.26

• Phaeton once again holds back new charging current on WARP3 Pro chargers whenever automatic phase switching is turned back on in the charger. It now checks the setting again before every reconnect, and as soon as the charger reports a change, instead of only when the connection was first set up. Stopping a charge is always still possible.
• The WARP setup guide now explains how an upgrade from an older release keeps the existing charger settings, and how to go back to the previous release.

Phaeton v0.66.25

• Zaptec Pro and Go 2 chargers are now recognised when the cloud reports their model details with different capitalisation. Previously such a charger could be shown as a Zaptec Go. Charging limits, stop and resume are unchanged.
• The automated Zaptec verification now runs setup, charging limits, stop and resume, sign-in renewal, rate limiting and lost responses against the reference implementation Phaeton is verified against. Where Phaeton deliberately differs, for example by checking fresh charger state before a stop, that behaviour is checked separately.

Phaeton v0.66.24

• Bender CC612/CC613 setup now reads the controller in the same order as the reference implementation Phaeton is verified against. The firmware version is read on first use of the identity view instead of during setup, and the session user ID is only read when the controller answers the smart-vehicle check. Fault handling, current limits and the safety checks before a positive current budget are unchanged.
• The automated Bender verification now replays the paired reference comparison as a required check: identical setup and readout traffic for permitted cases, and separately asserted Phaeton behaviour for fault admission, unavailable meter values and the identity read.

Phaeton v0.66.23

• Maintenance release. A check of the temporary log-level control that could occasionally report a false failure during Phaeton's automated verification is now reliable. Charger control, logging and the settings pages are unchanged.

Phaeton v0.66.22

• WARP chargers stay controllable for as long as their live data stream is connected instead of losing control about fifteen seconds after connecting, reconnect promptly after an outage, and regain control automatically when external control is switched back on at the charger.
• An Alfen charger no longer has its charging interrupted by Phaeton's own keep-alive right after a charging current was accepted; a stop still stops it.
• Bender chargers report the first real error for each value, stop a failed poll early instead of waiting through several timeouts, say which phase current or voltage the meter reports as unavailable, and are never reported as identified while the connection is actually down.
• The "Retry delay" control setting, which had no effect, is removed from the settings page. Existing configuration files that still contain it keep loading.

Phaeton v0.66.21

• go-e chargers on the local network can now switch between one-phase and three-phase charging. Phaeton confirms the charger's phase setting after each accepted change before it relies on it, and the dashboard shows the phases the charger is set to rather than the phases the car happens to draw.
• In automatic charging mode a temporary network failure during a phase change is retried, and a charger left in automatic phase mode is asked again on the next attempt. A manual phase change that fails this way reports the reason; it is retried once when Phaeton knows the charger's current phase setting and the GX device is not connected for control, and otherwise fails at once with the reason so it can simply be repeated. The dashboard shows that reason until the charger reports the requested phases. A change the charger refuses turns phase switching off.
• The dashboard's phase choice is disabled, with the reason shown, for chargers whose integration does not offer phase switching. A connected Peblar charger reports whether it can switch phases only after Phaeton has read its relay configuration, so the dashboard no longer shows that choice as unsupported before the first successful read; installation settings still treat Peblar as unable to switch phases.

Phaeton v0.66.20

Maintenance release for Zaptec cloud chargers. Charging limits, stop and resume commands, and cloud sign-in behavior are unchanged; their documentation now describes that behavior more precisely.

Phaeton v0.66.19

• Peblar charging now follows the charger's documented limit of three pauses in any ten-minute period. Charging can resume right away after one or two stops; after a third stop within ten minutes, Phaeton waits until the oldest of those stops is ten minutes old before it resumes. Stops are never delayed.

Phaeton v0.66.18

• Peblar chargers now use Modbus TCP.

Phaeton v0.66.17

Bender telemetry now reports whether charging is enabled from the controller's current limit.

Phaeton v0.66.16

Bender chargers now use the documented Modbus current, status, telemetry, and recovery behavior across supported hardware variants.

Phaeton v0.66.15

KEBA Modbus recovery now closes failed connections before reconnecting and validates malformed replies without replaying guarded writes.

Phaeton v0.66.14

• Easee acceptance checks now use the charger’s published integer current-limit contract while retaining stream and REST lifecycle verification.

Phaeton v0.66.13

• WARP2 Pro and WARP3 Pro telemetry now uses the charger's live WebSocket stream while current-limit control remains guarded and authenticated.
• Easee cloud charging now keeps its stream and REST requests aligned through token refresh, pacing, reconnect recovery, and command readback. Session energy and charger state remain protected by fresh telemetry and current control grants.

Phaeton v0.66.12

Alfen charging now keeps successful current settings through stop and resume, refreshes them while control remains valid, and recovers cleanly after connection errors.

Unavailable charging power stays unavailable, while existing stopped-state and phase-switching protections remain in effect.

Phaeton v0.66.11

Easee connection checks now cover signing in and receiving charger readings from a simulated service. Charging behavior is unchanged.

Phaeton v0.66.10

KEBA chargers now report their charging permission directly and use the correct current and pause commands for each model. A temporary measurement failure no longer prevents a stop request. Charging control continues to require a valid current allowance and fresh measurements.

Phaeton v0.66.9

This maintenance update leaves charger setup and charging behavior unchanged.

Phaeton v0.66.8

Charger setup guides are now organized by manufacturer. Existing guide links continue to work. Charging behavior is unchanged.

What changed

• Fixes Phaeton disappearing from the GX device list after selecting Phaeton under Charging managed by. Charging readings now continue updating while Phaeton manages Auto mode.
• Removes an unnecessary inverter reading that could cause repeated errors in the GX Modbus TCP server.

Upgrade notes

• Your saved choice under Charging managed by remains in effect. This update does not give Victron GX control when Phaeton is selected.

What changed

• Fixes the Charging managed by choice on Settings and in the setup wizard reverting to Victron GX after saving. Installations created with the 0.59.0 installer or later, and named charger instances, silently kept GX in control of Auto mode. The saved choice now persists, so Phaeton can manage Auto charging with the local solar, battery and grid preferences. New installations, a configuration reset and configuration recovery still start with Victron GX managing Auto.

What changed

• The Schedule page now shows a price forecast under the weekly overview: one bar per hour of known VRM import prices for the next three days, with the hours a saved price limit would allow charging filled in. It appears only when a schedule uses a price limit and prices are available.

What changed

• Charging permission now survives a planned Phaeton restart. Charging output still stops safely while the service restarts.
• When automatic start is enabled, a connected car can start charging after Phaeton starts or when the setting is enabled. A manual Stop still takes priority until the car is reconnected or charging is enabled again.
• Manual and Scheduled modes now retain charging permission and automatic start when Victron GX is selected to manage Auto mode.

Upgrade notes

• In Auto mode with GX charging control enabled, Victron GX still controls when charging starts.
• If charging was already saved as disabled by an earlier version, enable it once after upgrading.

What changed

• You can now remove a charger that you added on Chargers on this GX. Phaeton stops that charger, removes its VRM Control Panel route and startup entry, frees its port, and deletes its settings, account, license and charging history from the GX. Other chargers keep running.

Upgrade notes

• Stop charging on a charger before removing it. Removal cannot be undone, so back up its settings first if you may need them again. Chargers installed over SSH are not removed from this page.

What changed

• The Charging page now keeps completed sessions across restarts. Past sessions show energy, solar share, cost and savings, with totals and a spreadsheet download.
• The current session shows how much solar power saved, its effective price, the next Scheduled charging window and the vehicle's target on the charge meter.
• Chargers on this GX is now a System tab alongside Health, Logs and Updates. The app navigation stays visible, and your entries and update selection are kept when you switch tabs.
• The website lists supported charger models, how they connect and what each model requires. The complete online guide is available in English and Dutch.
• You can send a support request from Phaeton with a support bundle attached automatically. The bundle includes logs, charging status and settings to help investigate the problem. You can review or remove it before sending.
• The SSH installer selects a native ARMv7 or ARM64 package for your Venus OS device.
• Phaeton handles interrupted update responses from a VRM proxy and reconnects to check whether the restart completed.
• Fixed false EV energy spikes in VRM after setup, restarts or updates when using MQTT. Phaeton now reports charger energy as unknown until a valid reading arrives, while GX discovery and control stay available.

Upgrade notes

• Past sessions are retained for up to 400 sessions or 400 days. Older entries are removed automatically.

Chargers on this GX is now a tab in the System section and a button on the activation page, and it appears only when this installation can manage other chargers. The page shows which entry is this charger, describes each charger's state in plain words, confirms restarts and updates in the same dialog as the rest of Phaeton, and reports the result next to the action you took. Restarting this charger from the page now waits for Phaeton to return and reloads. The installation guides explain more clearly how to add a second charger.

USB installation now restarts the previous installation after early failures and restores its backup without extra storage. Reinstalling also removes stale update backups that could undo the installed version after a reboot.

Valid settings remain active if an upgrade cannot save them. Settings shows the storage warning, configuration notices and the original backup location together. Configuration backups have a fixed retention limit, and saved decimal values remain readable.

Installation checks use the configured web address and distinguish the setup wizard from configuration recovery. USB progress logging uses fewer resources.

• Fix the web login's “Keep me signed in” checkbox layout on mobile and desktop.

• Add a “Keep me signed in” option to the web login.
• Persist remembered sessions across Phaeton restarts for up to 30 days.

Fixes stable Cloudflare release promotion when the prepared release tag is not propagated into the promotion job environment. The job now derives and checks the tag directly before publishing.

What changed

• Fixed missing Alfen charging power when the charger provides total real power but individual phase-power readings are unavailable. Phaeton now reads the charger's total-power meter independently, retaining valid phase readings as a fallback.

What changed

• Existing local MQTT and Modbus installations on GX now prepare VRM Control Panel access automatically after an update and restart. Charger identities, login details, licenses and control settings are preserved; previously disabled access stays disabled. Modbus users do not need to enable MQTT.
• Managed EV charger discovery reports compatibility firmware v1.29, separately from the Phaeton version. Disabling Control Panel and restarting restores the original local connection. An occupied extra listening address leaves the existing connection available.
• Updated the installation guide with both upgrade paths, requirements and recovery. Automatic repair, remote sign-in, live updates, restart and disable/re-enable were verified on a Cerbo GX. Modbus needs completed setup and activation before remote access is available.
• Includes the new Easee cloud Beta for explicitly selected Home, Charge, Charge Lite and Charge Core chargers. Setup verifies the model and keeps credentials local. Current, pause and guarded resume/authorization use response and observation checks. Resume requires a budget covering the charger maximum; automatic authorization requires at least 7 A. Physical qualification and vendor-approved access are still required; phase switching and positive GX MQTT control remain unavailable.
• Includes corrected Zaptec session and stop/resume preconditions, removes the extra zero-current write before final stop, and bounds setting-confirmation timeouts.

What changed

• Added Easee cloud Beta for explicitly selected Home, Charge, Charge Lite and Charge Core chargers using REST and SignalR. Setup verifies the selected model and keeps credentials local. Physical qualification and vendor-approved access are still required.
• Added current, pause and guarded resume/authorization with asynchronous response and observation confirmation. Easee resume requires a budget covering the charger maximum; automatic authorization requires at least 7 A. Phase switching and positive GX MQTT control remain unavailable.
• Corrected Zaptec cloud session and stop/resume preconditions, removed the extra zero-current write before final stop, and bounded setting-confirmation timeouts.
• Added independently authored regression scenarios based on pinned evcc behavior and tests, plus credential, stale telemetry, reconnect, cancellation and setup coverage. API acceptance is never treated as proof of physical charging.

What changed

• Auto mode now explains when charging is waiting for unavailable GX battery or power readings. Missing battery-protection data is distinguished from a low battery, even when another reading still shows a high charge level. Charging limits and timing remain unchanged.

What changed

• Failed updates restore the previous web interface alongside the existing binary. If filesystem recovery is blocked, Phaeton retains the original interface backup and reports how to recover it before retrying.
• A failed update restart keeps the current process running when the replacement cannot be launched. Successful restarts preserve the original process arguments.
• Unavailable required charger telemetry now shows a warning and keeps affected controls locked until fresh valid readings return. Unsupported optional measurements remain separate from control availability.

What changed

• Charger settings show readable current steps, including 0.1 A for Zaptec and 0.001 A for KEBA, WARP and Peblar.
• Decimal settings, schedule current limits and Electrical details no longer show long numerical tails. Saving unchanged settings keeps their original values.

• Choose Dummy — no license required during ordinary setup to try Phaeton without a physical charger or license.
• The activation page now offers Change charger, returning to setup with your saved settings and existing account.
• Change simulated connection states directly from the dummy dashboard; measured power and energy always remain zero.
• Setup and changes between dummy and physical adapters restart Phaeton automatically. Sign in again afterward; physical charging still requires a valid license.
• Existing demo deployments migrate to the regular adapter selector while preserving their identity, credentials, and stored license.

• First setup now offers an optional “Share usage and diagnostics” checkbox, unchecked by default. Check it to enable reporting; existing configured installations remain disabled after upgrading.
• Settings → System lets you change sharing and preview the report data. Reports summarize compatibility, reliability, performance, feature use, setup and update outcomes without device identifiers, raw logs, charging schedules or energy readings.
• Product diagnostics use an independent daily sender. Turning sharing off clears queued reports, and delivery failures do not affect charging or licensing.

• Software updates now use Phaeton’s own download service. After installing this version and restarting, check Software Updates again for subsequent releases. Existing custom update sources and update preferences are preserved.
• USB installation downloads automatically follow the published stable release.
• Installation files and recovery instructions are available from Phaeton’s download service without a separate account.

What changed

• Phaeton now has a gold Solar P icon in browser tabs, bookmarks and home-screen shortcuts. The app and licensing portal share the same icon, including on sign-in and setup screens.