I can’t find the PM function for this forum. Can you give me a hint?
Tap the avatar icon, then select “message”.
I got the app running.
When i try to “start” the charging in homey, it doesn’t work.
Also when i try to trigger a flow with “charging started” it doesn’t react.
Anyone else tried?
Thank you for your feedback. I have found a potential bug, but that might not solve all. I have uploaded a new version. Could you install this and test please?
- Update to v1.0.10 via the App Store (no unpair, no re-pair, no device deletion).
- In the Flow editor, look for flows with an orange warning badge. Open each one, pick the Wattpilot device in the card, save.
- Try “Force start charging” from the device tile or a flow. If it still doesn’t charge, Settings → Debug log → Copy and paste into the
community thread. The merged timeline will show whether setValue(‘frc’, 2) went out, whether the charger echoed back frc=2, whether car
transitioned, and what state it was in at the moment.
Thank you.
Best regards, Remco
V1.0.11
- Fix: changing charge mode, current or force on/off on a Wattpilot Flex (firmware 42+, including Nordic Laddbox models) silently failed — the charger was rejecting every write. Message format corrected. Older Wattpilots unaffected.
Hi Remco,
sry for my late test review but i made some changes in my hardware setup.
Well now i had time to implement your App, i use the Wallbox from Fronius Wattpilot Home 22J,
Software Version 42.5 and Homey Pro 2026 v13.5
The Login was easy without any problems, the app in homey recognize immidetialy when i plug on my car and reports the right values, i compared them with Fronius Solar Web App data.
For one point i have a question:
- Why i cant see my Wallbox in the Energie Dashboard, i only see them like other energy measurment devices under “Top Consumers”, i found a thread where they discuss this topic
Where is my ev (charger)
Many thx for providing us this app!
Hi,
Had to fix that one there. Obvious small mistake.
Car connection detected, but evcharger_charging_state stays plugged_out
Hi,
I have found what appears to be a connection-state synchronization/mapping issue in the Fronius Wattpilot app for Homey.
My setup
- 2 × identical Fronius Wattpilot chargers
- Both are brand new and were supplied and installed at the same time
- Wattpilot firmware: 43.4
- Fronius Wattpilot mobile app: 2.1.2
- Both chargers show exactly the same behaviour
How to reproduce
- Disconnect the charging cable from the car.
- Wait a few seconds.
- Connect the cable to the car again.
- Do not start charging.
The Homey Flow trigger “Car connected” fires immediately and reliably.
The “Car disconnected” trigger also fires immediately when the cable is removed.
However, after connecting the car, Homey’s standard EV charger capability:
evcharger_charging_state
remains:
plugged_out
even though the vehicle is physically connected.
After a short while, the Wattpilot-specific state changes to:
wattpilot_car_state = WaitCar
while:
evcharger_charging_state = plugged_out
remains unchanged.
I created a diagnostic Advanced Flow to log the different states. For example, when connecting the car I get:
Wattpilot Norr: Car connected | state=plugged_out | carState=Idle | charging=false | power=0 W
Shortly afterwards the device can be in this state:
evcharger_charging_state = plugged_out
wattpilot_car_state = WaitCar
The same behaviour is reproducible on both chargers.
So the app clearly detects the physical connection, because the “Car connected” trigger works, but the generic Homey EV charger connection state does not seem to be updated accordingly.
If I start charging, the charger status gets refreshed and the state becomes correct.
Expected behaviour
When the Wattpilot reports WaitCar, I would expect Homey’s EV charger state to indicate that a vehicle is connected, for example:
plugged_in
or possibly plugged_in_paused, depending on how the Homey EV charger capability is intended to be mapped.
The same probably applies to Complete: the car is still physically connected even though charging has finished.
Why this matters
I want to use the physical cable connection as an automation trigger. My plan is eventually to retrieve the vehicle SOC when the charging cable is connected and pass that information to my HEMS.
The dedicated “Car connected” trigger already seems to work reliably, but the generic evcharger_charging_state and connection condition can disagree with the actual state of the charger.
It looks like the physical connection detection itself is working, but the mapping/update of evcharger_charging_state may be missing for states such as WaitCar.
I can provide screenshots, additional diagnostic Flow logs or a Homey diagnostic report if that would help.
Thanks!
Thanks for the very precise report — you found two bugs. The standard charging state was being written with values Homey doesn’t accept, so it silently stayed at “Not plugged in” whenever the car was connected but not charging. And the “Car connected” trigger fired a moment before the device state was updated, which is why your log showed carState=Idle. Both are fixed in the next version: WaitCar now maps to Paused, Complete to Plugged in, and the triggers fire only after the device is updated. After updating, unplug and replug once so the state refreshes.
I am uploading the version now. Available as test. I would love to hear your feedback please.
best regards,
Remco
Hi Remco,
Thanks for the quick fix. I have now installed 1.0.19 test and tested it with my two identical Wattpilot chargers, both running firmware 43.4.
The connection-state fix appears to work correctly.
I tested disconnecting and reconnecting the car without starting a charging session:
-
Cable disconnected:
evcharger_charging_state = plugged_outwattpilot_car_state = Idle
-
Cable connected, waiting to charge:
evcharger_charging_state = plugged_in_pausedwattpilot_car_state = WaitCar
I also verified the other states:
-
Charging completed / car still connected:
evcharger_charging_state = plugged_inwattpilot_car_state = Complete
-
During charging:
evcharger_charging_state = plugged_in_chargingwattpilot_car_state = Charging
So the mapping now looks correct and, most importantly, the charger no longer remains at plugged_out while the vehicle is physically connected.
I have tested this on both chargers and have not seen the previous behaviour again.
I also use a diagnostic Advanced Flow for the connection and charging events, and the states now look consistent with the actual charger state.
I’ll continue running the test version in normal use with both cars and will report back if I notice anything else.
Thanks again for the very fast response and fix!
Best regards,
Richard
Hi Remco!
First of all, thanks for developing this app!
I have two Fronius Wattpilot Flex Pro 11 kW chargers, controlled by Gravio HEMS (Home Energy Management System), and I’m using Homey Pro 2023.
Gravio HEMS dynamically calculates how much charging power should be available based on solar production, battery status, household consumption and grid limitations.
My problem is that Gravio HEMS cannot control the switching between single-phase and three-phase charging. It can provide a requested charging power in watts, but the existing Homey Flow actions control charging current in amperes.
This makes it difficult to achieve smooth charging control across the entire power range.
Would it be possible to add a new Flow action card that sets the requested charging power directly in watts (W), instead of amperes (A)?
Ideally, I would like the following functionality:
-
Accept a dynamic power value from a Homey Flow tag, ranging from 1,380 W to 22,000 W, depending on the charger’s maximum capacity.
-
Automatically select single-phase or three-phase charging based on the requested power.
-
Automatically calculate and adjust the corresponding charging current.
-
Handle phase switching safely, preferably using the Wattpilot’s built-in phase-switching functionality, including appropriate delays to avoid frequent switching.
For example:
-
2,300 W requested → Single-phase charging at approximately 10 A.
-
6,900 W requested → Three-phase charging at approximately 10 A.
My chargers are limited to 11 kW, but supporting up to 22 kW would make this useful for other Wattpilot models as well.
The goal is to let Gravio HEMS handle all energy management decisions, while your Homey app translates the requested power into the appropriate charging current and phase configuration.
This would allow me to send the power value directly from Gravio HEMS through Homey to the Wattpilot, without having to build complicated Flow logic for phase switching and current calculations.
Do you think this would be technically possible with the Wattpilot’s local API? And would you consider implementing such a Flow action?
I’d be happy to help test it with my two Wattpilot Flex Pro chargers!
Best regards,
Richard
Hi Richard,
Thanks again for the clear request. It’s built, and v1.0.20 is on the Test channel: Fronius Wattpilot | Homey
What’s new
- A “Set charging power” action card. You give it a power in watts, for example a tag from Gravio HEMS, and the app works out the rest:
- Single-phase from 1,380 to 3,680 W (6–16 A).
- Three-phase from 4,140 W up to the charger’s maximum current. On your 11 kW units, that maximum is the “Maximum current” device setting.
- Between 3,680 and 4,140 W it stays on single-phase at 16 A. The card never charges above the requested power.
- Your examples come out as expected: 2,300 W gives one phase at 10 A, and 6,900 W gives three phases at 10 A.
- Below 1,380 W you choose on the card: pause charging, or keep charging at the 1,380 W minimum.
- Hold time between phase switches. After a switch, the charger stays on that phase for a minimum time. The default is 5 minutes, and you can change it under “Phase switch hold time” in the device settings. During that time only the current is adjusted.
- Default mode. The card puts the charger in Default mode, so the Wattpilot’s own Eco logic doesn’t override Gravio.
- Repeated requests. Only values that actually change are sent to the charger, so it’s fine if Gravio sends the same value often.
- Two chargers. The settings page and the Charging Status widget now let you choose which charger to show. Before, they only ever showed one of them.
What I’d love you to check
- Use the new card while the car is charging, with values that cross the 4,140 W boundary. Does the Wattpilot actually switch between 1 and 3 phases on your Flex Pro, and does the car keep charging after the switch?
- If anything looks wrong, open the app settings, pick the charger, and send me the debug log with “Copy”. Every card call is logged there with the phase and current it chose.
- Let me know which car(s) you charge. Some cars handle phase switching better than others.
Best regards,
Remco
Hi Remco!
Wow, that was incredibly fast! 
Thank you so much for implementing my request so quickly. I really appreciate the effort you’ve put into this, and the new functionality looks exactly like what I was hoping for!
I’ve already installed v1.0.20 and done a quick test of starting and stopping charging through Gravio HEMS, which works fine so far.
I’ll do some more thorough testing during the coming week, especially the automatic phase switching, and report back with my results.
Thanks again for the amazing support and your great work on this app!
Best regards,
Richard
