Re: Quinta 65
Posted: Tue Dec 20, 2022 1:15 pm
I originally just made the OTGW for myself. I spend time and money to make it available to others and try to help them as best as I can. Most people appreciate that, but all you can do is complain. And you're wrong about most of your claims too.
The OTGW does not attempt to emulate a thermostat of a given brand. Of course it could, but that should not be necessary with boilers that follow the opentherm specification correctly. So that has never been a design goal.
The equipment matrix does record which thermostat, if any, was connected when the data was received. If you select a boiler and then click "Show details", the information of the last 10 log files that were uploaded for that boiler is shown. Each column has a header that shows the date and time the log was uploaded. If you hover the mouse over that header, a pop-up message shows the thermostat used. Granted, this may not be very obvious. I didn't point it out on the site because this information isn't usually terribly useful.
Having an OTGW with just a boiler and no thermostat works fine for everyone but you. Why it doesn't work for you is still unclear. So maybe you should not assign blame until that has been figured out. You have verified that the OTGW works with another boiler. For all I know, you may just have connected or configured your Quinta 65 incorrectly. But because of your refusal to do some simple measurements, we don't know.
Diagnostic test #5 dates back to at least 2013, as can be found on the internet archive. So no, that was not based on your suggestion of a few months ago.
The Nodo shop makes the hardware for the OTGW available at pretty much material cost. They definitely do not charge a commercial price. If you want to know what that would be, take a look at this web shop. And I seriously doubt you would get any better support there. At least the video they link to in their description shows that they don't have a deep understanding of the device.
I agree that the linux kernel is better than the Windows kernel. But the linux kernel is developed by over 15000 developers (2017 figure). You can not really compare that to a project that I basically develop on my own. I have one boiler and 3 thermostats. Especially boilers are expensive. It is unreasonable to expect me to be able to test against a large variety of equipment. The web site clearly mentions which boiler and thermostat I use. By the time there are 15000 OTGW developers, you may expect the majority of boilers and thermostats to be verified.
Figuring out the reference voltage only needs to be done once. I would have had to sacrifice a lot of resources to do this automatically in the main firmware and properly handle all eventualities, like the thermostat or boiler not yet being connected. It made more sense to me to provide a simple way to update the firmware and put the things that would rarely be needed in a separate piece of firmware. That leaves resources available for more frequently used functionality. Plus, in most cases the default value just works.
Sure, I could have put a much more powerful processor in the OTGW and made a very fancy dynamic plug-in based system. But that would have made the device more expensive, bigger, and use more power. The development of such a system would also have taken much longer. The choices I have made to come to the current implementation seem to be sufficient for the vast majority of people using the OTGW. So far, you are the only exception.
The only thing you have achieved with your pompous attitude is that I am no longer willing to spend any more time trying to help you. So good luck. I hope you figure it out.
The OTGW does not attempt to emulate a thermostat of a given brand. Of course it could, but that should not be necessary with boilers that follow the opentherm specification correctly. So that has never been a design goal.
The equipment matrix does record which thermostat, if any, was connected when the data was received. If you select a boiler and then click "Show details", the information of the last 10 log files that were uploaded for that boiler is shown. Each column has a header that shows the date and time the log was uploaded. If you hover the mouse over that header, a pop-up message shows the thermostat used. Granted, this may not be very obvious. I didn't point it out on the site because this information isn't usually terribly useful.
Having an OTGW with just a boiler and no thermostat works fine for everyone but you. Why it doesn't work for you is still unclear. So maybe you should not assign blame until that has been figured out. You have verified that the OTGW works with another boiler. For all I know, you may just have connected or configured your Quinta 65 incorrectly. But because of your refusal to do some simple measurements, we don't know.
Diagnostic test #5 dates back to at least 2013, as can be found on the internet archive. So no, that was not based on your suggestion of a few months ago.
The Nodo shop makes the hardware for the OTGW available at pretty much material cost. They definitely do not charge a commercial price. If you want to know what that would be, take a look at this web shop. And I seriously doubt you would get any better support there. At least the video they link to in their description shows that they don't have a deep understanding of the device.
I agree that the linux kernel is better than the Windows kernel. But the linux kernel is developed by over 15000 developers (2017 figure). You can not really compare that to a project that I basically develop on my own. I have one boiler and 3 thermostats. Especially boilers are expensive. It is unreasonable to expect me to be able to test against a large variety of equipment. The web site clearly mentions which boiler and thermostat I use. By the time there are 15000 OTGW developers, you may expect the majority of boilers and thermostats to be verified.
Figuring out the reference voltage only needs to be done once. I would have had to sacrifice a lot of resources to do this automatically in the main firmware and properly handle all eventualities, like the thermostat or boiler not yet being connected. It made more sense to me to provide a simple way to update the firmware and put the things that would rarely be needed in a separate piece of firmware. That leaves resources available for more frequently used functionality. Plus, in most cases the default value just works.
Sure, I could have put a much more powerful processor in the OTGW and made a very fancy dynamic plug-in based system. But that would have made the device more expensive, bigger, and use more power. The development of such a system would also have taken much longer. The choices I have made to come to the current implementation seem to be sufficient for the vast majority of people using the OTGW. So far, you are the only exception.
The only thing you have achieved with your pompous attitude is that I am no longer willing to spend any more time trying to help you. So good luck. I hope you figure it out.