Ocular IQ Wallbox - Working

[kwanm84]

Just thought I'd post, I have an australian charger, the Ocular IQ Wallbox (https://ocularcharging.com.au/ocular-iq-wallbox/) - IOCAH10-22S

Ocpp works well... the following sensors are functioning;

Energy.Active.Import.Interval
Energy.Active.Import.Register
Energy.Meter.Start
Energy.Session
Power.Active.Import
Time.Session
Transaction.Id

Controls:
charger.Reset
charger.Unlock
Availability
Charge_Control
Maximum_Current

Diag:
Connectors
Error.Code
Error.Code.Connector
Profiles.AUTH|REM|RES|SMART|FW|CORE
Heartbeat
2 hours ago
ID
Id.Tag
Latency.Ping
Latency.Pong
Model
Reconnects
Serial
Status
Status.Connector
Stop.Reason
Timestamp.Config.Response
Vendor
Version.Firmware
22103101-22050701-22050701

---

Note: For me... on 3 phase... setting maximum current below 6 will stop all charging. I guess a limit in the charger. It will charge upto 15 amps (limited 11kw by car). Don't have a compatible ev to test 32 amps.

[iJuiceman]

Hi mate, I also have the Ocular IQ Solare and have it connected and working with HA.
One thing I am not sure what is wrong, is that none of my sensors are showing data, they are all showing unknown.
Sensors:
Energy Active Import Register
Energy Meter Start
Energy Session
Time Session
Transaction ID

Any ideas ?

Everything else is working fine.

[kwanm84]

Not sure what is extra in the solar. I assume it has ct clamps and can self manage itself. I use "charger maximum amps" and my solar goes through ha. So I use ha to manage the charging when I have excess solar. It's a little complicated but works well. I have all the sensors you listed. If you still get some info and can control it then I assume it setup correctly. As for missing sensors... honestly no idea. Can you manual change Max amps and availability / charge control? I'm away from home for another 3 days so I can't help much until I'm back.

…

On Fri, 29 Sept 2023, 10:45 am iJuiceman, ***@***.***> wrote: Hi mate, I also have the Ocular IQ Solare and have it connected and working with HA. One thing I am not sure what is wrong, is that none of my sensors are showing data, they are all showing unknown. Sensors: Energy Active Import Register Energy Meter Start Energy Session Time Session Transaction ID Any ideas ? Everything else is working fine. — Reply to this email directly, view it on GitHub <#789 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASFSYDGAX23LSNZFYUUSNI3X4YY4BANCNFSM6AAAAAAVV4SIDU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[bradmatt275]

Out of curiosity does this prevent the app from working?

I just got this charger installed myself. I can see the option to set the OCPP endpoint. It's currently pointing at ocpp.ocularcharging.com.au which makes me think it's required for the app.

[kwanm84]

Yea, I had a go at adding my charger to the app, but it couldn't find it, so confirmed won't work.

I do have my charger running purely off solar with my HA. It definitely not easy to setup as I have batteries as well, and I wanted to make sure it didn't charge off them... obviously you need all your energy stats... at a minimum, solar and house usage. Needs a few work arounds with automations to make it run well. But should work as well as the app (if not better) with some effort.

I see how much excess energy I produce... this is a little complicated with my setup as I want the battery to always charge 2.5kw until its full

then set the amps for the charger based on that, and adjust it every 30 seconds.

e.g. <4kw - 0 amps
4-4.4kw - 6 amps
...
10.7-10.9kw - 16 amps

10.9kw - 32 amps

This is for 3 phase.

But it does work really well... I can override it and tell it to charge off the grid.

I don't have functions such as start and end timers, or charge a specific amount of energy... but I really don't need it with the setup I have. It will always charge off solar... avoid charging between 4pm and 8pm on weekdays (we have demand charges in QLD)... or I can override to charge off grid... and even during the demand time if I really need charging.

These are my current stats, I don't think we've used the grid for months.

Total EV Charge: 2941.54 kWh
Charge from Solar: 87.51% (2574.11 kWh)

[bradmatt275]

Amazing. I never thought of doing that. Sounds like I could have saved some money by getting the regular one (without the CT clamp).

I'll have a play around and see if I can replicate your setup. I have my inverter connected to HA through their API. The data is a little delayed but not too bad.

Thanks again for all that info.

[Surk91]

I know it's been a while, but has anyone here found a fix for this reset issue? I've been trying to connect mine to HA today and it did the reset and dropped all the settings and reverted back to "N/A" for the SN/model/vendor fields which are now grey for some reason. I briefly had the charger come up in the OCPP integration and then everything went to unavailable like the posters above.

[dsmackie]

I know it's been a while, but has anyone here found a fix for this reset issue? I've been trying to connect mine to HA today and it did the reset and dropped all the settings and reverted back to "N/A" for the SN/model/vendor fields which are now grey for some reason. I briefly had the charger come up in the OCPP integration and then everything went to unavailable like the posters above.

The issue is within the OCPP app within the charger. It has a bug where it can only accept a finite length response from the HA OCPP agent. When it receives a response that is larger than it can handle, there is an error and the string HA sent overwrites memory where the charger config is stored. The charger then saves this "garbage" into the settings config, and on next reboot the settings are corrupt so it loads up a default setting file. This default setting file does not have any details specific to your charger, so S/N, model, vendor etc are now lost.

I raised an issue with both Ocular and the Chinese manufacturer whom which Ocular just re-badge with no joy.

Do you have the details of the S/N, model and vendor from the box or sticker on the unit? I am fairly sure at the moment your unit is bricked with the lose of these settings. If you know the S/N, etc, I can probably help you craft a command to send to your unit to re-populate these details and unbrick it. I had to do this with mine, but I was fortune to have a good set of values from a previous session of trying to "fix" it.

[StroppyOz]

Do you have the details of the S/N, model and vendor from the box or sticker on the unit? I am fairly sure at the moment your unit is bricked with the lose of these settings. If you know the S/N, etc, I can probably help you craft a command to send to your unit to re-populate these details and unbrick it. I had to do this with mine, but I was fortune to have a good set of values from a previous session of trying to "fix" it.

@dsmackie I have these details. If you're still happy to help craft a command to repopulate these fields, I'm happy to be the guinea pig.

[iJuiceman]

I worked out its HA or the App, not both. I contacted OcularIQ, but have not had a reply from them about the ability to poll their API for the details, so I can put it into HA. Having used the charger for a few months, I think I will scrap the App and just use HA with the OCPP plugin

[jay510-dev]

Sorry for digging up an old thread - how did you manage to get the Ocular talking to HA? I've tinkered with the setup page with no luck - should I be changing the server path or identity?

[MikeatLorne]

for domain: use the ip of your hass
server port: 9000
server path: /

that should then show a "reference url" at the bottom - fine is: ws://192.168.86.110:9000/Alkdsfajdjldf

[MikeatLorne]

I am having trouble getting the sensors working - fine for 10 months but has not worked for about 4 weeks now. I am unable to track it to anything I have done: Controls and some information is coming through okay

I am getting this in debug files (sample):

2023-12-26 15:39:02.005 DEBUG (MainThread) [custom_components.ocpp] 'A14223215317' trying measurand 'Energy.Reactive.Import.Register'
2023-12-26 15:39:02.005 INFO (MainThread) [ocpp] A14223215317: send [2,"4da1b115-d5b1-42a1-9b18-7a9a1c67aa6f","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Energy.Reactive.Import.Register"}]
2023-12-26 15:39:02.105 INFO (MainThread) [ocpp] A14223215317: receive message [3,"4da1b115-d5b1-42a1-9b18-7a9a1c67aa6f",{"status":"RebootRequired"}]

any ideas?

[julianjwong]

I'm trying to get my Ocular Solar IQ connected and wondering if there's any extra settings needed other than the path and HA IP address via the Ocular installer config portal? Mine appears to connect briefly with HA and displays some updates to sensors in HA which tells me the comms partly works. But then within about a minute everything goes Unavailable. The charger beeps quite a few times as this happens. Is there anything specific I need to do in the OCPP integration? Any help or ideas appreciated!

[bradmatt275]

I ended up giving up on mine. It kind of did the same thing as yours where it would reboot and one time it even factory reset the device.

I suspect it has something to do with the energy management component of the Solar IQ.

If I had to guess id say it's getting conflicting instructions from the HA OCPP and the energy management OCPP causing it to freak out.

[dsmackie]

I ended up giving up on mine. It kind of did the same thing as yours where it would reboot and one time it even factory reset the device.

Just so you know you are not crazy, mine did the same as yours and factory reset today. I changed the OCPP settings to talk to HA and all settings reset to N/A or defaults. I was fortunate to have a tab open with the Web UI and could reapply the previous settings.

The issue (100% the charger) comes from this HA OCPP module performing checks to determine the available measurands. It sends each measurand individually to the charger to verify it can provide the required details and builds a final list of all measurands. Once the final list is known, that is sent to the charger to set all the measurands that should be returned. The charger has an issue where the list provided is too big and it craps out. The result is a factory reset.

I've reached out to the OEM for the charger to report this issue and just waiting on a response.

[bradmatt275]

I ended up giving up on mine. It kind of did the same thing as yours where it would reboot and one time it even factory reset the device.

Just so you know you are not crazy, mine did the same as yours and factory reset today. I changed the OCPP settings to talk to HA and all settings reset to N/A or defaults. I was fortunate to have a tab open with the Web UI and could reapply the previous settings.

The issue (100% the charger) comes from this HA OCPP module performing checks to determine the available measurands. It sends each measurand individually to the charger to verify it can provide the required details and builds a final list of all measurands. Once the final list is known, that is sent to the charger to set all the measurands that should be returned. The charger has an issue where the list provided is too big and it craps out. The result is a factory reset.

I've reached out to the OEM for the charger to report this issue and just waiting on a response.

I would be interested to see if they fix it. Their support was pretty good and did their best to help me, but I wasn't impressed with the charger.

Had so many issues where it would just stop charging for no reason. When the charger was bricked after a firmware update it was the final straw.

I ended up getting a partial refund and buying a Zappi to replace. I've been super happy with the Zappi. It just works and was really easy to add into HA.

[dsmackie]

I would be interested to see if they fix it. Their support was pretty good and did their best to help me, but I wasn't impressed with the charger.

Had so many issues where it would just stop charging for no reason. When the charger was bricked after a firmware update it was the final straw.

I ended up getting a partial refund and buying a Zappi to replace. I've been super happy with the Zappi. It just works and was really easy to add into HA.

I've only had the charger for 48hrs so cannot make any concrete reviews, but the app does not fill me with much hope. The solar only feature seems to just sit at "Suspended" and never actually charges. Unsure if I have a CT clamp backwards or some config needs to change. Still looking at it all to try and figure out how best to use it.

I think controlling via HA will be best, if they can fix the OCPP issues. I have gone direct to the manufactures who make the device in China. Unsure if I would have any joy through the Australian retailed who is just rebranding the device with their own cover plate.

If I ever hear anything I'll throw up an update.

[bradmatt275]

I would be interested to see if they fix it. Their support was pretty good and did their best to help me, but I wasn't impressed with the charger.
Had so many issues where it would just stop charging for no reason. When the charger was bricked after a firmware update it was the final straw.
I ended up getting a partial refund and buying a Zappi to replace. I've been super happy with the Zappi. It just works and was really easy to add into HA.

I've only had the charger for 48hrs so cannot make any concrete reviews, but the app does not fill me with much hope. The solar only feature seems to just sit at "Suspended" and never actually charges. Unsure if I have a CT clamp backwards or some config needs to change. Still looking at it all to try and figure out how best to use it.

I think controlling via HA will be best, if they can fix the OCPP issues. I have gone direct to the manufactures who make the device in China. Unsure if I would have any joy through the Australian retailed who is just rebranding the device with their own cover plate.

If I ever hear anything I'll throw up an update.

Oh yeah I had that problem. Might be unrelated, but if it helps, that happened to mine because the safe current limit was setup incorrectly.

It's actually the reverse to what you think it would be. I thought it needed to be the max current allowed so it doesn't trip the breaker (e.g. 28.8 amps for a 32 amp circuit). But turns out it's actually the reverse. You need to enter 3.2 amps instead.

[vicinigit]

I'm using the Ocular IQ and can control it fairly well with Home Assistant using OCPP integration. Issues I'm keen to get help with are:

1. I don't know what "Availability" does. It's usually false (but everything still works) and if I set it to true it just switches itself back to false
2. The sensors don't seem to update quickly at all. Lags of hours is not uncommon. Any ideas how to force an update?

[vicinigit]

Ok #1 was easy. Availability is true when the charger in not being used.
#2 is still an open question.

[bradmatt275]

You can try using a REST integration in HA.

I don't have my Solar IQ anymore. It was bricked after a firmware update and I returned it.

But back when I had it running I ended up making HTTP calls:

You can then setup something like this in HA:

rest:
  - resource: http://192.168.2.64/cgi-bin/action.exe
    username: !secret car_charger_username
    password: !secret car_charger_password
    authentication: basic
    method: POST
    payload: '{"action":"statistics","data":"ModbusMaster"}'
    scan_interval: 30
    sensor:
      - name: "Car Charger Mode"
        value_template: >
          {% set outer_json = value_json %}
          {% set inner_json = outer_json.data | from_json %}
          {{ inner_json.ecoMode }}

      - name: "Power Grid Current"
        unique_id: sensor.power_grid_current
        unit_of_measurement: 'A' 
        device_class: "current"
        value_template: >
          {% set outer_json = value_json %}
          {% set inner_json = outer_json.data | from_json %}
          {{ inner_json.sampledValue.powerGrid[0].current[0] }}

      - name: "Power Grid Voltage"
        unit_of_measurement: 'V'
        device_class: "voltage"
        unique_id: sensor.power_grid_voltage
        value_template: >
          {% set outer_json = value_json %}
          {% set inner_json = outer_json.data | from_json %}
          {{ inner_json.sampledValue.station[0].conns[0].voltage[0] }}

It actually worked really well for me.

There are other things you can get from that but those were the ones I was interested in at the time.

[julianjwong]

Thanks for sharing the REST approach.
Not working for me unfortunately.

I'm getting this error

{
"code": 1004,
"message": "NO FOUND /tmp/Ioc/ModbusMaster.json",
"data": null
}

[julianjwong]

Dam, well you could try something like this:

I actually did get it working but I was a bit hesitant to use it. It was more of a test case.

When you save a setting in the WebUI you can see it calls this endpoint with the full JSON payload.

But I found you can just send individual properties like the EcoMode. Which from what I found is the charging mode.

This didn't work for me. Setting EcoMode as 1 or 0 had no effect to starting or stopping charging.
I was able to change the Max current limit but it doesn't become active until a reboot.

[bradmatt275]

Dam, well you could try something like this:

I actually did get it working but I was a bit hesitant to use it. It was more of a test case.
When you save a setting in the WebUI you can see it calls this endpoint with the full JSON payload.
But I found you can just send individual properties like the EcoMode. Which from what I found is the charging mode.

This didn't work for me. Setting EcoMode as 1 or 0 had no effect to starting or stopping charging. I was able to change the Max current limit but it doesn't become active until a reboot.

We must have different models or perhaps different firmware. I noticed when you sent that payload example earlier, it was quite a bit different to mine (when I had it).

In the balance screen (in the web interface) I had the ability to change the energy mode. Which is where I got the idea to try setting it via the REST API.

I was able to getting it working via Postman but never looked into adding it into HA.

[Dav0815]

@bradmatt275 / @julianjwong do you have an example of the REST call to change a setting for the charger (limit or mode) ? Thanks !

[julianjwong]

@Dav0815 - sorry been some time since I tried getting this working so I can't remember. Try using my code example above and Chrome inspector to view the REST calls. Once you find the right command you can test it using Postman or an equivalent app (I used a similar app on my Android phone).

[dsmackie]

@bradmatt275 / @julianjwong do you have an example of the REST call to change a setting for the charger (limit or mode) ? Thanks !

@Dav0815 Are you referring to the settings you can apply from the Ocular Smart Home app for limiting how much current is used for a charging session, and whether it be "Solar Assist, "Solar Only,"or "Full" in the meter page?

[Dav0815]

I have the reporting working fine with the code samples above, thanks for all the input. What I am looking for are REST calls to change the charger mode from HA and not using their app.

…

On 20 Mar 2025, at 4:48 pm, dsmackie ***@***.***> wrote: @bradmatt275 <https://github.com/bradmatt275> / @julianjwong <https://github.com/julianjwong> do you have an example of the REST call to change a setting for the charger (limit or mode) ? Thanks ! @Dav0815 <https://github.com/Dav0815> Are you referring to the settings you can apply from the Ocular Smart Home app for limiting how much current is used for a charging session, and whether it be "Solar Assist, "Solar Only,"or "Full" in the meter page? — Reply to this email directly, view it on GitHub <#789 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIOGNAEMWXOX7XETDVUGZ732VJQEBAVCNFSM6AAAAAAVV4SIDWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENJVHE2DOOA>. You are receiving this because you were mentioned.

[bradmatt275]

This worked for me but @julianjwong didn't have any luck with it.

[julianjwong]

@bradmatt275 Using my rest client app I can send this successfully

{"action":"setConfig","data":{"AmpLmt":"32"}}

Can you try on yours?

[bradmatt275]

Nice! In theory you can update any value available in the WebUI using setConfig.

Unfortunately I can't test it on mine. I returned it after a failed firmware update.

[Dav0815]

This works for me too. The new value is reflected on the charger admin interface. Do you have any success to change the mode ? That would be the sweet spot as I could then change it depending on energy cost through the day with an automation.

…

On 21 Mar 2025, at 8:05 am, julianjwong ***@***.***> wrote: @bradmatt275 <https://github.com/bradmatt275> Using my rest client app I can send this successfully {"action":"setConfig","data":{"AmpLmt":"32"}} Can you try on yours? — Reply to this email directly, view it on GitHub <#789 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIOGNADAJA4D5UVEQPXHVCL2VM3TVAVCNFSM6AAAAAAVV4SIDWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENJWHE4DQMA>. You are receiving this because you were mentioned.

[dsmackie]

@Dav0815 "AmpLmt" will set the max Amps that the charger can provide. If you want to change between "Fast", Solar Assist" and "Solar Only", "EcoMode" is what you want to set.

EcoMode 0 = Fast, 1 = Solar Assist, 2 = Solar Only

Using the REST query that @bradmatt275 has provided should suffice to set these values.

[Dav0815]

Thanks ! This works for me too. The only thing that I found is that the setting is changed in the web interface, but the output of statistics does not change.  

…

On 21 Mar 2025, at 2:06 pm, dsmackie ***@***.***> wrote: @Dav0815 <https://github.com/Dav0815> "AmpLmt" will set the max Amps that the charger can provide. If you want to change between "Fast", Solar Assist" and "Solar Only", "EcoMode" is what you want to set. EcoMode 0 = Fast, 1 = Solar Assist, 2 = Solar Only Using the REST query that @bradmatt275 <https://github.com/bradmatt275> has provided should suffice to set these values. — Reply to this email directly, view it on GitHub <#789 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIOGNADZVEEW4YL377BQHSD2VOF4DAVCNFSM6AAAAAAVV4SIDWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENJXGIZTAMI>. You are receiving this because you were mentioned.

[StroppyOz]

Okay. I have the Ocular IQ Solar. Like many, I wiped it when first using the tool. I had no backup configs (the firmware was 2023 and the option didn't exist). However, the installer configuration is available online in the installer PDF manual so entered that. Wouldn't work with the Ocular OCPP server until I set it up with this integration (I went back and checked and Ocular's server worked). The SN, Model and Manufacturer details are still absent from the Server tab! If anyone knows how to push these back that would be great. Not needed but nicer. Ocular themselves didn't have a way to do it either but they did update my firmware from 2023 to a 2025 variant (I guess you have to call them and request it!). I guess their app which checks for firmware doesn't!

Easy to setup just make sure you turn off automatic checking of measurands.

Incidentally, I also got it working with evcc (OCPP template) but had some issues with other meters and with spurious errors and this one will work better with the wife (just a on/off switch).

[dsmackie]

@StroppyOz Mine never appeared to have received any updates until I bricked it and the Oculus rep forced a firmware update.

The OCPP client for the charger allows remote commands to be executed from a request pushed from the OCPP server, which is defaulted to Oculus. That is how mine received the update from Oculus, I suspect. That in itself is a bit of a security concern but I guess no different to them pushing a dodgy firmware.

I have not looked in to it too much but I suspect the OCPP server is meant to push new firmware in release, but to avoid mass issues Oculus only do it when people call/email about an issue.

My pokings around have not found any remote location where I can check for new firmware versions.

[StroppyOz]

@dsmackie they're my sentiments also. After I broke the charger with the automatic measurand issue, I got the device to work again using this integration. Only after that did it then work again with the Ocular OCPP server. The functionality between the firmware I had originally (circa 2023) and the firmware I got (2025) is marked. As for security, moving it off the Ocular OCPP server will cease their ability to push updates.

[dsmackie]

@StroppyOz An option to disable remote commands would be a nice addition in a future update from iocharger. There does not appear to be any validation of the charger binaries so a potential option is to change the OCPP command string that is used to execute remote commands.

I have not looked at the HA integration since i borked my charger the first time but I'll have to take a look at some time in the near future. The app for Oculus is not all that amazing and any features that HA does not support could be added I am sure.

Glad it has all worked out for you in the end. I spend more time trying to break the charger than I do helping fix it so a big win.

[StroppyOz]

@dsmackie Definitely a good outcome. I struggled with getting evcc to work and this integration is much much easier... It's also free whereas evcc was not for the Ocular chargers (as there's no integration developed for it). It may be easier to set this up with evcc given the updated firmware but who is going to pay?... it does look really nice but I'd say total overkill for what most folk need. Having Amber VPP control my inverter and battery means I don't need the smarts that evcc comes with.

This OCPP integration works but doesn't have any fancy dashboard to go with it. I'm okay with that because what do I really need (now that I say that I think I'll look to include a schedule option)? I did discover in doing all of this that the charger itself is pretty dumb and has no real fancy functionality. When I bought it a few years back I thought it was the ducks guts! ha! How ignorant I was back then. lol. The app itself is even more dumb but it does the job it needs to and scheduling does work (but not always as it has some weird errors that requires you to force close the app for the schedule to stick and work).

[dsmackie]

@StroppyOz I have the charger set to start at 01:10 and stop at 05:50. Embrace those off peak rates. That is all the functionality I need really. The Solar Only option has not worked too well for me in the past as it just keeps starting and stopping. Likely need a gigawatt solar array for it to be stable.

[julianjwong]

Has anyone got a way to get the power consumption data into Home Assistant for this charger? Im somewhat hesitant trying the integration for this charger but I've seen various updates pushed so am somewhat hoping it's easier to integrate now.