An API so that charging can be controlled locally through wifi without need for internet access. This can be used for integration with home automation software, smart charging and so on.
suggestion, release a "API Gateway box" that are able to communicate on you Local easee wireless network.
Why? The Easee box already has a local API, it's just that it's locked for "partner" companies only to access. Actually, an approved partner company could make that box hehe. But it would be an extra unnecessary cost for us users, just to sell more boxes and make more money.....
Yes, we need this especially now with high energy costs where we could use excess solar
to reduce energy costs and use surplus solar energy, you can very easily and free of charge connect the Easee charging box to "CLEVER-PV" www.clever-pv.com and thus use PV surplus. very easy!
Integration into clever-PV
To connect the easee wallbox to clever-PV and charge it with excess solar power, you only need the access data from your easee app.
This does not fix the problem that the easee wallbox needs sometimes 3-5 minutes to adapt to new settings in the cloud. The cloud service is also not reliable and had multiple outages in the past. At the moment i can‘t recommend the easee wallbox if you need a smart solution
Absolutely! This product feels dated in 2022 without the option to connect via LOCAL connection and API and to simplify. As the owner of a product you should be given ALL access. Think the advice from som of you on this forum to get another unit is a good idea. Wont recommend Easee and thinking of selling it.
This is absolutely a must for a modern device.
Documented and open MQTT interface - now please!
The sad thing is that there IS a local API already in place since a long time back but it is locked and for select partner companies only to use.
I'm also since some time back warning friends from buying Easee.
I have changed to zaptec instead. And I will also warn about my experience in other forums. I have had to many nights without no charging of my car due to cloud API problems. Not a reliable product,
I’m out. Changed to Zaptec. Easee have certainly not their customers as first priority… From now on I will be active on forums and Facebook groups and warn about Easee experience…
It's been 2,5 years now. We might start to think you don't care about your customers....
Remember that tech savvy people tend to recommend products to friends and family. Some of us also work at or run companies selling your product....
This cloud stuff sucks. Ever Few days they are offline or buggy. This thread is 2 and a half years old and u do nothing. This product and the Support sucks This way....
I also need a local API as the API Servers are offline too often or do not responde to requests in time.
Please give some feedback if this feature will be implemented or not.
Server issues are showing: Local API is needed!
This is ridiculous. This is the worst support I have ever seen.
Please create the local API as soon as possible.
api is offline again (502, 504 error). Please give feedback about the development status of this local api. Is it really planned or not? From my opinion, there can be only one answer.
I need a simple local API to control my Easee charger with my Loxone system, which also will be used in conjunction with PV and home battery.
you have been offline for a few hours and again it shows how important a local API is!
Totally agree here - I also need a local API to be able to read the info
Local API is highly needed. Setting dynamic charge limit should be done locally in order to maintain stable charging control. Slow response via cloud or if the internet falls out, mess up the possibility to maintain stable total power usage below or close to the kWh/h rates.
A local API would be superb. Right now I have a Prometheus exporter github.com/daverstam/easee-exporter but the granularity is not great since the upstream cloud api returns a timeout too often. A local functional API would probably solve this and also take off the load from the upstream servers
I am trying to find the best EV charger for solar, but without a local interface the Easee simply do not do the job. Relying on Internet is not an option. Please prioritize this as I really do like the product.
Hello, joined the club today. Owning a PV since May and having several issues with surplus charging due to cloud problems I highly recommend finally developing this requested local API.
This morning your shitty system is offline and i can't change current values. Where is this promised local API?
Easee, could you please post an approximate schedule (weeks, months, years...). I mean reading the posts here, this is an important feature for a lot of people here.
I try to recomend the easee wallbox to everyone who asks but meanwhile i start to think about the last 2 years and it seems there is no development in this essential part giving the users access to a local API. Cloud API is slow, unresponsive and sometimes i can´t set values via API.
Please, please get this running soon.
OK, this is getting ridiculous. Right now the API is incredibly sluggish, reaction times are measured in minutes - if it does react at all. Charging current always goes back to maximum and 3 phase mode when trying to set a lower current and only one phase. I always supported Easee and recommended the wallboxes to friends and family, but I am out of patience now. As soon as possible, I will replace the Easee box with a (much more expensive to be fair) OpenWB box.
I was really hoping the local API would arrive and therefore solve these issues, but the last bits of communication even sounded like Easee is not willing to provide a local API at all.
We need this to enable smart home features for clients that already have easee installed. I am sorry to say that for other clients we install a different solution because of this issue. Having this feature would enable us to also recommend easee. We would need:
- trigger start/stop
- get state
- get consumption statistics
got feedback from support. Quote: "unfortunately we won't be able to do that. At Easee, everything is cloud-based."
Tbh. The anwer is wrong in several ways. It's from the support team and not from the po/pm.
Nobody knows if Easee even reads in here... Write to them in my Thread at Twitter please. They need to react NOW!
This night my car was not charged since there were issues with the cloud service. Please give me local API to make the product work. I have zero interest in the cloud service, but I need to communicate with the charger from my home automation system.
Cloud has been "503 Service Temporarily Unavailable" for over an hour. How's that local API coming on?
Please support mqtt for local API, so that currentPower is availabe by push. Like SignalR just local.
Hello, i love your small wallbox, but please realize a local open API for Start/Stop/Current/Phase. I need this for PV loading. Thank you!
@Tor Erik Skårdal,
my doubts are growing that easse is not serious enough with their customers needs. This request has been raised two years ago, during the last months supported with more and more user requests. Two months ago you started a poll to ask why we as customer need a local api and which features are most wanted. Since then…..total silence, NOTHING ! I see it almost daily, sunshine plus here and there clouds. Your cloud control is currently totally useless when it takes up to 30 seconds until a request for increase or decrease of max. dynamic charging current has been executed by the charging robot. During EV charge I am buying electric power for three times the price because it . takes too long to reduce the charge power and I am additionally loosing money because of selling to the grid. It takes too long until charge power is increased again when much more pv power is available.
I am really disappointed!
If you don´t give us customers are credible statement within the next week to implement the local api within a few weeks I will go for the go-e chargers. There I have to accept other disadvantages but their local current control works with acceptable reaction time.
I have no need for a just „nice looking“ EV charger with insufficient controllability.
Have a look at the Myenergi Zappi charger.
I have that installed.
There is no local API at the current stage, but they are working on it. However, I don't feel that I miss it to much. The charger comes with a mode to only charge with surplus power. Have not paid a cent for my charging sine the start of May.
Got to love my solar panels! :)
But if there is situations you need it to charge despite cloudy days, it is easy to control the device with Home Automation or app. The respons is a lot quicker compared to the Easee.
I replaced the Easee with the Zappi and I have never looked back!
Easee was a good product in the beginning, but sadly they are not keeping up with the rest of the industry. At least when it comes to "smart" EV chargers.
I would love this feature as well.
I'm not so unhappy with my easee home. But I really start to regret having chosen a wallbox without local api for at least controlling current. Cloud API is just to slow and not reliable enough.
Could you please communicate a release date for local API?
Any news update to annonce? Amount of PV energy rises from day to day - as do the prices for electric power in Germany. When will be the first beta testing? I am already using iobroker for easee control und could share my experiences. Or will it never come? Then I will have to go for the go-e chargers pretty soon.
Just so we are clear. There IS a local API so that external balancers can work offline as advertised. So this local API 100% is closed and not accessible in any way?
That is correct :) there is a way for the Equalizer and other chargers to talk to each other over Easee Link (mix of wifi and radio) so that they can preform load balancing offline.
Unfortunately Easee Link is not designed to be open and used by others.
Worth starting wireshark? Or did you encrypt it in some way? 🤔😉🙂 (you should so probably yes 😁)
I'll need to write a load balancing bridge for a Shelly Em3 anyway 🙄
Also for me an easy implementation would do it. I do not need fancy topics like consumption, just start, stop charging and phase select would be sufficient
I need a basic local API.
Start/Stop and charging-current.
I got solar cells on my roof and I need to control the EV-charging depending on the SOC on my house-battery. Using the cloud-API sometimes ended up in complete draining of my house batteries.
A simple STOP would be a great start for me :)
I need a local, reliable and unlimited connection. This is needed for fast feedback in PV loading. Locally available operations must be starting/stopping charging and setting the circuit and charger limits. An upper bound on these limits, set via remote from the operator, must be respected of course.
And by the way: Getting the mail about a change in this idea made me first thinking that it is implemented at last. Enough time has past already ...
Auth: have an API token than can be auto generated on the app and reset when need, use it as a header for requests
REST: by far the most used and “default” nowadays, check status, be able to get reporting data for the sessions, and so on
In v2, one could introduce WebHooks or WebSockets, to subscribe to events, so we don’t need to keep asking every minute if the charge session has started or ended
Apologies for the lack of updates on this topic. We changed the status to planned a while back because we want to provide a local API and still plan to do so.
Unfortunately we don't know when, yet. But we would love to get your feedback on what type of features you would like to see using a local API: forms.office.com/r/puTJDGMEz0
Thanks for at least giving us some sign of life. What makes this task so challenging for y'all? Hardware limitations? Bandwidth on the charger? I appreciate that designing a proper local API can take a while. However, folks including myself are looking into selling their Easee wallbox because updates from your team come infrequently and there's no clarity on your approach (to this request). Would you be willing to commit to more frequent updates (let's say 1 a month) to help manage expectations and give us an outlook for how long we will be waiting for this feature to be released?
Just start, now. With your answer I don't believe there will be any change soon. Start simple for single installation. State, start/stop, phase change, power change. Then continue with the rest. Don't overcomplicate it (the more you do, the never you start).
The task it self is not the challenging I think. There are a few things we need to figure out, like how to provide support and how to do access control.
But the reason for why we have not done it yet is prioritisation. We are spending all our time scaling internally and the service we provide to our partners.
I wish I knew how long it would take, but to be honest I don’t know until we prioritise it and start on it.
Right now the plan is to collect as much insight and information as possible so that we can move it up in our priorities.
Ouch. I'm getting my Easee box installed next week. Sounds I need to get another box instead. I need tight, fast and reliable load balancing and limiting, hence cloud won't work.
A local API is a must. Charging an EV with PV is useless with the current cloud API when it takes up to 20s until a request for a new current limitation is executed. I DO NOT want to BUY current nor do I want to sell my PV current when it should go instead inside my EVs battery - just because easee's cloud control is so time lagging. I will wait one more month, if the local API is not available then I will sell my 2 easse home charger and will instead go for the fast, http-controllable go-e chargers. What a pitty, shame on you easse !
I guess everyone is looking for an update on it, having local API would be a game changer for my lovely Easee Charger. It is by far the best product I cam across and really looking forward to a local API for the monitoring and some controls.
Also looking for a charger with local api, but seeing this request with planned tag for ½ year, makes me belive this is not coming.
I thought there already is a local web socket API on port 9000? Not that I can find any proper documentation?
Local is a must. Cloud is a bonus. Not the other way around IMHO. But the whole world is cloud-crazy....
Would also like to see a local API, besides all the good features of the Easee Home this unavailability is really an issue. I have two Easee Homes installed and now plan to go for a PV, the choice for the Easee Home might become a wrong decision then.
We also would also like to sell and use easee chargers in our company. But with more companies ending up with unreliable Cloud solutions, a local API is needed urgently.
Even privately now, I think of returning my easee wallbox as well.
Any status update here? The addition of Enova financial support for smarthouse has made this a rater pressing matter. When is this expected to be completed? Kind of regretting buying easee now, when it seems wallbox has point and click integration towards HA. Design is nothing without function...
@Easee please update the current status and/or post some more details. I think a lot of people are waiting here. Thanks.
I would like there to be a local API and that the easee app uses both local API and connect to cloud. One should always be able to handle basic charging, scheduling, power level etc locally.
Local API also means possibility to use e.g. home assistant
Some months ago I recommended an easee to a friend of mine for his Audi GT. Now I'm also looking for a wallbox for my Taycan that allows the integration into our home automation (including pv).
Cloud is not an option for me.
Seems that easee is no longer on my list - what a shame. Design is great and some ideas (like the locking of the plug) are neat.
Any news on this?
We have several easee chargers at our company. We'd like to introduce an overview on our intranet similar to the easee dashboard to have a look for everybody at our company to see the status of our chargers. For sure without logging in to easee cloud.
Too bad they keep referring to the cloud. They even implemented a cloud based standard for charging that doesn't not follow the OCPP1.6J standard meaning that it won't be able to talk to inverters like ferroamp etc meaning it will be worthless for anyone with solar panels... most people with solar panels will want to charge their cars.. big big deal breaker..
If I knew this, I would never bought it in the first place. Now I'm probably gonna sell it cheap and buy something else.
Very disappointed with Easee and their customer service.
Hi all, it's been about two months since this feature request was marked as "Planned". Would you be able to elaborate what your plans are, if there's a way to beta test, and if possible share a rough timeline?
Many people, including myself, are eager to leverage their PV effectively and we'd need a proper local API to do so.
As other folks on this idea have indicated: while I purchased my Easee wallbox already, I wouldn't be able to wholeheartedly recommend it to others until this is fixed.
Thanks and happy holidays,
How long do they actual review this? Should be an easy thumbs up/down decision
There’s a few tickets in here related to this. Don’t want to go in too much detail yet because we have some ground work to do first before we can say what’s planned. I very much want to see a flexible local API, but we have to do it properly :)
If what Stian said a few days ago is still valid, the local API will not be what is requested here, unfortunately. Maybe someone from Easee can confirm what is actually planned? Hopefully I'm wrong and it is indeed a real local API that will work even when the charging robot does not have internet access.
Right now the sun is shining again here and I can not charge my car automatically (again) since there are issues with the cloud API (supposedly the charger can't be reached). :(
Sure, but for now if it will be the possibility to start/stop and change the current/phase locally it will be great for start.
But as berlinerbolle mentioned, please confirm what is planned.
Start / Stop / Pause / Resume and changing the current and number of phases would be fine for me, too. Oh, and maybe the value of total current power.
Under review since 2 years!
Ignoring customer requests for so long is really unprofessional and sad.
I will replace my boxes soon.
I‘m very disappointed that there is no statement or explanation from Easee even though this is one of the most requested features.
I will sell my Easee Box and already stopped recommending the box to others.
It really is a shame since the box is designed well and has good capabilities - but right now it's not a good choice for someone with own solar panels.
We are sorry to hear that you are leaving us as a customer based on this. We will implement local control but it will be through a local common protocol like the Matter protocol for example. Easee is a member of the Matter initiative and that is where we will enable local control. This is something all users can utilise not just those who know how to use an API which is a very small customer base.
In addition we are looking into a local control through the Eaeee app.
For special cases like PV control or other home automation purposes we suggest using the cloud API directly the documentation can be found here developer.easee.cloud/
This will allow you to control your Easee products as long as you have an internet connection.
Alternatively one of the open source alternatives like Homey or Homeassistant can be used 😆🙌🏼
Thank you for the reply, I really appreciate it. I think you underestimate the size of the userbase that would benefit from a local API though. Using the cloud API is no alternative, since it (sorry to say it) has been proven unreliable, and needs a working internet connection.
Providing a local API would not just benefit users that are developers themselves, but ALL users that want to do surplus solar charging - since there already are various working software solutions for this, but Easee is not yet supported for lack of a local API.
In hindsight I know that I'm obviously not the target demographic (same goes for all the other people in this thread) and should have bought another wallbox because of the expectation of having a local API.
I refuse to rely on cloud based solutions for controlling my home. It's just too important. A lot of manufacturers are seeing this the same way, and so far I was able to keep almost everything locally.
Just to add to this, in case it wasn't clear: for lack of a better alternative, I am currently using the cloud API. That's why I know that it is not reliable, and it's just too slow and does not allow enough requests/minute. Also, having to rely on a cloud solution for my home, especially for something existential as a charged car, is just not right (sorry).
When will you release the mentioned local api?
1. We will implement local control but it will be through a local common protocol like the Matter protocol for example.
--> Is matter even ready to use? Are the data models for wallboxes, inverters and so on already defined and agreed upon? What about the whole message routing, security stuff? If it is easy to implement go for it. Otherwise I would strongly suggest you provide a *simple* local API soonish and plan on providing a matter based API in the long run.
2. Easee is a member of the Matter initiative and that is where we will enable local control. This is something all users can utilise not just those who know how to use an API which is a very small customer base.
--> Not everybody needs to be a programmer to make use of APIs. There are well established projects (e.g. openwb for solar driven wallbox charging) which do all of the magic behind the scenes.
The matter protocol approach only holds true if there is such a thing as the "matter eco system". From my (very personal) standpoint this is more of a wish than (todays) reality. I would argue that a simple API is in fact more important TODAY. Matter might be a thing for the future really.
Since getting my car and trying to do surplus charging throughout the day, I came to realize how often the cloud API does not work. It's not really an outage, but sometimes it's just not working - a few seconds or minutes later, it does work.
So a local API would be much better for this. I understand that Easee wants to keep the possibility for power suppliers to remotely control the charging of the wallbox. But a local API would not stand in the way of this. Just let remote commands through the cloud override commands that have been issued locally.
Also, local commands could be issued much faster, as well as status updates could be requested much more reliably.
Today I really miss a local api since the Cloud api is down :(
Any progress or roadmap for implementation? Would be great to get some commitment from Easee. I dont want to rely just on cloud API.
We're a company installing solar and EV-charging stations, and since the products have to work together, we would like to use easeee products but will only do so, once we get stable local APIs...
My Homeassistant would be so happy to have a local API to connect. Hope this feature will come soon.
We are working with a swiss company who are looking at massive rollout of this WB - but a local interface/API is required for a local smart charging system.
What is the status with this request?
Any progress or target for implementation? Would be great to get some commitment from Easee side.
I also need the local API. When I realized that this was a problem I become very disappointed. So for now on I will tell everyone about this limitation.
I Need a local API too
I am a small step before ordering a easee wallbox. What is the plan regarding a local API?
I need it for smarthome integration
How is it going on with the local API? I would like to buy an Easee Home but a local Api is necessary for my smart home integration.
Currently I‘m searching for a high flexible box as a recommendation for my electrician. This box was one option but currently I cannot continue to recommend this box for several reason. The customers expect from a professional installer a high reliable box. Besides other things, one main question is to use a PV to charge the car. Without any local API this box stays too inflexible.
For now I can handle this box. But for a professional usage the whole easee stuff still feels to much as a hobby. The app, the permission stuff and the dependency to a cloud does unfortunately destroy a lot of business on your side.
Just a comment. If you do not change your mindset, the marketplace will show you the direction. It will work for now because the box is new and fancy, but I see already in the forums and on the fact that the most electricians does not know this box, that it might run into a wrong direction. Might, must not, but killer features like a local api to connect easily the PV, is a Game changer.
I had two easee chargers installed at my house before realizing this limitation.
A friend just called and asked if he should get the same charger for his house and I (currently) advised him against it. So that is -1 sale for you guys because of this limitation.
Just to add briefly to my earlier post. Easee Home is supported within this project ( github.com/andig/evcc). Nevertheless and unfortunately, only via the cloud API. So a local API would still be a killer for this wallbox!
Local API is necessary to purchase the wallbox!
With which smarts meters (HAN interface) is the equalizer compatible?
Can you give a rough timeframe estimate on what you're planning here?
There's currently another outage, wallboxes are in offline mode. A simple locale API for current limiting would enable home automation systems to continue working even if your servers aren't reachable.
Please add a local API to make the solution flexible. THX
Local API is crucial to a functioning home with solar panels and integrated home automation! We cannot depend on a Cloud solution only.
I want to integrate my Fronius inverter. It would be so easy, if i could integrate the ip.adress in my eassee to control, that i only charge with photovoltaik power
Got tired of waiting for any response or action fra easee, so I went for MyEnergi Zappi 2 instead.
Vibrant community and developers that is quick to respond and communicate in their own forums!
Works offline and also possibilities to control locally. Have integrated it with my home automation software!
Wondering why the most wanted feature is not considered by Easee after such long time.
We need this to make Easee compatible with openWB.
Local API. YES. Secure it via WiFi and a local address. Simple and much needed.
i would also appreciate a local API, i would like to use openWB to better utilize the 70% rule for my PV system. With the 70% rule I am not allowed to feed more than 70% of my PV power into the grid, above that the system is regulated. If I charge the power in the EV then I may generate this power over 70%.
Solutions for local load balancing (i.e. without Tibber and/or relying on internet access) is highly needed.
I would also like to see a local API. Cloud solutions aren't reliable enough for me and I would like to connect everything locally in my Smart Home.
I would really appreciate the effort.
We must have this as soon as possible. MQTT as it seems to be now is fine but we can not rely on cloud which limits the rate and have other problems every so often
Yes we really need that!
+1 for a local API to be able to integrate the Easee wallbox into openHAB or openWB (surplus PV charging)
Is this also using the Cloud-API or is it using a lokal API?
Please give us a local API - the current cloud outage underlines the need even more. Ideally, the charger should be fully useable without any cloud access. At least give us a local API so we can read all datapoints and set a few things (like charging rates, cable unlock, target percentages, schedules, and so on).
MQTT support would be just fine for that.
Also, the smartphone app should be able to connect locally to the charger without the need of enabling the chargers access point. Enabling the access point, connecting to that particular WiFi, and then using the app for limited functionality is not something that is compatible with some users in my household.
We really need a local API. I charge my car when I have surplus energy. Now I cant charge my car due to the outage.
Cloud still not available! People who's chargers are not working at the moment should go to public chargers. That sounds like a bad movie to me!
I hope this helps with prioritizing of the roadmap - even if this is just one of the reasons for the need for a Local API - it will help against this type of outage.
Agreed. Things will propably get worse as state subsidies will skyrock charger Users. Together with Smart Home Integrations sending hundreds of API calls every hour In cannot See how a pure Cloud API can ne reliable.
A total of three and a half offline days in the last three months. That's pretty unreliable.
Local access via MQTT or Modbus TCP would be great and for sure a big argument for buying the easee wallbox.
The cloud api is fine, but of course only when internet access is stable! I'm living in a small village where this is not always given. 4G is also very weak.
The outage last week showed the need for a local API. As i can see the robots are communicating using mqtt, just make it possible for us to ad a private mqtt server and share you current api
Local API would me most appreciated.
Are using a BMW wallbox at home and it is easy to integrate with Loxone (home automation). Want to buy an Easee charger for the cabin, but need to know that I can be able to control it before I hit the purchase button :-)
A local API should be a given for any connected product that has privacy in mind. It should be the choice of the consumer to decide if and how usage of a device they have paid for should be available to anyone but themselves. There are also more and more examples of physical products becoming useless as the cloud services they depend on are suspended, often with little to no compensation for the consumer. Others have changed their operational models placing perviously free services into payed subscribtions.
By providing the option of a local API a company is more or less saying that when you purchase this product, you own it.
Otherwise you're just leasing it for an undisclosed amount of time.
Another compelling argument for «local» API for controlling the EVSE - cloud backend is chronically unstable.
I would also really much like a local API
A local API would make the choice of charging robots much easier. Knowing that I would still have control of it even if you for any reason went out of business. Now a small start up as you are that only support control via your cloud make me a bit cautious and worried
You asked the users to vote for features they would like, and the most wanted feature was a local api (with more than twice the amount of votes as any other feature). Please respect what your customers want.
If you are concerned about security then cutting the connection to internet is the by far best action to increase security. The second thing you could do is to implement authorization in the already existing webserver that anyone can activate by pressing the button on the charger.
You dont have to create your own solution for a local api, there are already lots of standards for local apis that you can use.
@Ola, probably because it adds highly relevant context information about how Easee’s thinking goes and their motivations for what they have been and will be doing around APIs in general. Even though I like the idea of a local API, I think the answer from Easee/Stian was solid and completely understandable.
We are currently working on the Cloud API to extend it’s documentation so that it is easy for everyone who wants to start using it. The reason for using a cloud api is mainly because of security, there are many local secure methods as well but it introduces complexity we would like to avoid having to take into account at the moment.
We promised an API and we do have one, we cannot promise at this point in time an API which is local. What we can say at this point is that we would like to implement a system that can work offline but at the same time play nicely with the rest of the home. We are closely following the development of the CHIP standard and as it matures we are hoping to implement that as The integration point into the smart home market and other possible solutions. This way we can focus our resources on implementing one standard which in turn could open many more doors and offer a lot more flexibility than our own private local API.
Read more about Connected Home over IP here www.connectedhomeip.com/
Read more about our API here:
Totally understandable. But local control of chargers with Easee app on local wifi without internet access would be much appreciated, a hybrid cloud, or edge computing strategy may be the right solution to that.
@Stian, If CHIP might be the long-term goal, does that mean that the current chargers have Zigbee radios or is that something that be added afterwards? Or will you need to purchase a new charger?
Chip is not dependant on a Special radio it it will support several radios and communication protocols. One of them is WiFi. As chip is an IP application layer we can add sopport for it on top of the existing product.
Hi Stian - the 2 link in your comment is broken
Hi Stian - The 2 link here is broken - so no god