I have rooted my Toon because of this.
There is a very useful binding for Rooted Toon thermostats
Ah, this quality response after eight months does also not represent the community?
The user community here is separate from the developers who work on the software. All are volunteers though and would gladly refund the money you paid for this software. You are free to demand a refund of the money you paid for this software.
Many concerned users have used bountysource to offer a bounty for developers to fix bindings that are important to them.
Bruce, thank you, clear story.
I do not mind paying for some fix or solution, the problem is that I cannot rely on a quick fix when a hardware supplier changes something in a key part. After waiting for a couple of months, I had to abandon Openhab.
When a developer then shouts ‘do it yourself’ after eight months silence, I do think the community has a problem. I hope not, Openhab is a great solution.
You misspelled developers. 
If you would have searched, you quite easily would have found that tread
which shows the original developer and you could have addressed him directly using
@jongj
in your post instead of waiting 8 month and blaming others for beeing silent.
Wow constructive answer! Blame the stupid user… But did you notice the project and the link you sent is dead? I sure could have made a mistake, but maybe you are not completely flawless yourself.
Fyi, I did search, I did write a message to the developer, and finally I posted this question.
So why didn’t you tell us that there was no response from the developer, or did I miss that ? Such information is very important for us, so we can update the CODEOWNERS list on github and possibly mark the binding as no longer maintained. This then would prevent users from frustration like yours.
2 Likes
So why can’t you communicate without trying to blame me for everything? I was not frustrated at all, I only tried to address two issues: the Toon plugin is dead, and the community did not seem to care about this dead plugin in the store. Note that a couple of people asked questions about this and did not get any response too.
I thought that was a pity because I know OpenHab is a great product, but with answers like yours you are destroying the community.
Nb I would have rewritten the plugin if I could count on proper support here.
I am not a developer, by the way. Just a satisfied user who gives back the way he can. I help the forum. If I could write a binding, I would.
1 Like
To make one point clear: the community is not responsible for development or maintanance of any binding or bundle. Some developers are very active in the community, others are not, so how should the maintainer-group know about an unmaintainded binding ?
If a developer stops actively maintaing his binding, it is his choice, but he should inform the maintainers about that changed situation. As all developers are volunteering into openHAB, it is very hard to find a new one to do the requested/needed updates like in your case. Development can be very difficult without having the device at hands, that’s my expirience from the WeMo binding.
2 Likes
In the issue linked earlier the developer responded in the comments last August that he lo longer has the thermostat or a subscription.
But it also states that this is not needed, as Toon offers a developer account 
1 Like
To avoid further disappointments of users installing this non-functional binding I’ve removed the toon binding: https://github.com/openhab/openhab-addons/pull/6802
3 Likes
This might be a good moment to promote my Toon binding. It only works on rooted Toons, mind you. Introduction is here: Rooted (locally accessible) Toon, download link is here: https://gofile.io/?c=kjbHgU
Why isn’t this done after almost a year, and it seems like this has been abandoned completely?
Thinking of configuring my house with openHAB but if support is this slow and i can’t even bind my own thermostat to this system, i’ll consider a different software package…
That is a problem when working with a completely volunteer developer community. Yes, it has been abandoned until somebody finds it important enough to develop further.
it seems quite unbelievable that the people who started this topic didn’t feel any need after all, and nobody else wishes this to be solved… Considering how many Toon thermostats exist, I simply can’t imagine nobody feels this may be important…
The learning curve of the system increases exponentially if I can’t even hook up my existing system by using configuration files but directly requires me to dive deep in the code and fix stuff myself that isn’t even documented. Someone who already went trought the hassle of learning the architecture of this program might be able to solve / change the binding to the new Eneco endpoint (?) without much of an effort while this very problem actually deters new users like me.
It may be regional. I am in the US and had not heard of this before the thread.
It’s a Dutch thermostat. Its name Toon in Dutch translates to ‘show’ or ‘display’ and is also used as a male name.
I don’t think there are that many Dutch homes using a Toon thermostat that are also using openHAB. I do not own one myself neither do I have any interest in buying one.