[ur63Participant 2022-12-18 at 12:59 Post count: 70]

#33656 In reply to: xxx |

@debbe
Not sure if you understand some german language? Regardless, if not already done, I’d recommend to join KNX-User-Forum.de and to parse the “Open KNX” and “DIY” sub-forum.

There is a small but very good and professional community developing and building their own devices (HW and SW) which they also sell for comparably small money (<<100€) to interested users. However, as the components are being sold as “DIY sets”, mainly for liability reasons, you need to be capable of soldering some components.
If you have any questions, it is no problem to write in english and you still get replies.

• This reply was modified 2 years, 4 months ago by ur63.

[sinn3rParticipant 2022-12-18 at 11:16 Post count: 369]

#33646 In reply to: xxx |

@debbe
I recommend you try to fit most functionality of your new house in KNX devices and not mixing up different smart home standards for base functions. This may cost a few bucks more but leads to a stable system. And don’t ever think about using anything wireless with batteries for functions you use often.
Did you already buy all KNX devices or do you need some recommendations? In most parts the German MDT company offers the best value for the buck and the most complex on device software features. Now sure where you are from and which devices you can buy at your location.

For logics, visualisation and remote control there are several options available, but here I recommend going the Gira Homeserver way (as that’s the main theme of this forum, which is by far the most “oldschool” software available, but it’s stable, very powerful and works fine virtualized (needs x64) – the cracked one at least ;) But it also runs fine on some Fujitsu ThinClient devices, which share exactly the same hardware and are available used for small money, if virtualisation is not an option.
Using QuadClient (which is a part of the homeserver) as visualisation is fast to setup, easy and visually appearing.

For adding non-KNX devices to KNX there are a few options available with Home Assistant being one of them. I never tried it though, as I chose ioBroker to connect all the different protocols in my home to my KNX backbone. I am also running node.red (within ioBroker) for complex datatransfers between ioBroker and KNX.

P.S. Do you think it’s possible to create an automatic patcher for ETS6 that searches for the needed byte patterns and patches the code so you don’t need to start over for each new ETS6 update again? As @ur63 already mentioned ETS6 is not perfectly stable at the moment and most system integrators I know are still working with ETS5 because of this, but they release ETS6 updates on a regular basis and it gets better each time.

[ur63Participant 2022-12-18 at 10:26 Post count: 70]

#33637 In reply to: xxx |

@debbe
THANK YOU for all the efforts and time you put into this. Excellent Work.
As ETS6 is still in kind of “pre-mature state”, it would be great if you continued supporting, when updates get released.
Anyways, big thanks again.

• This reply was modified 2 years, 4 months ago by ur63.

[intesisParticipant 2022-12-18 at 03:03 Post count: 10]

#33597 In reply to: xxx |

it seems strange to me that some guys didn’t succeed..

The cracking method has not changed compared with Ets5。
Just no one likes to share.

the Ets5 “Knx.DevKit.dll” crack is master level.
If you are interested, you can check it out

[sinn3rParticipant 2022-12-17 at 13:38 Post count: 369]

#33576 In reply to: xxx |

Wow this really looks good now.

I did a large check:

ETS6N:
Import of a signed ETS5 knxproj: OK
Import of an unsigned ETS5 knxproj: OK
Export knxproj: OK

ETS6C:
Import of a signed ETS5 knxproj: OK
Import of an unsigned ETS5 knxproj: OK
Export knxproj: OK
Backup to archive: OK

Installed some apps:
License check: OK

Congratulations to @debbe for all his hard work!!!

I think you will get alot of support (ETS and Homeserver) here, when you build your own house :)

Now all that’s missing is a way to sign the exported knxproj file. But we also did not have that in the past. And the embedded dummy file way seems to work as a workaround.

And guys, please don’t spread this cracked version to other forums so gira will not notice it so fast and create countermeasures in the next updates.

And @debbe, maybe you could outline us, how you cracked it. I know that some other guys tried to crack it in the past and did not succeed. Sharing knowledge is the key ;)

[intesisParticipant 2022-12-17 at 11:46 Post count: 10]

#33559 In reply to: xxx |

“ETS6C” lost

[hsdudeParticipant 2022-12-17 at 02:23 Post count: 37]

#33532 In reply to: xxx |

oh, one more Info. The ETS “C” runs perfect in Win 32 Bit (Win7 with me) without these “shi…” plugins. SO I think this is not directly related to 32 / 64 Bit

[hsdudeParticipant 2022-12-17 at 02:11 Post count: 37]

#33528 In reply to: xxx |

Just checked myself
– ETS5 “C” (cracked) project with 21 devices imported to ETS6 (N) without problems.
– Exporting the same project works perfect.
OS is Windows 10 just for info.

I do have a project with more than 100 devices (with long history starting ETS1.3, but this requires Compatible mode. Currently running with ETS5C cracked). I’ll try when sinn3r is successful with his smaller project :-)

[sinn3rParticipant 2022-12-16 at 19:12 Post count: 369]

#33520 In reply to: xxx |

@magicuf Strange that this works for you!

@debbe
I reset ETS6, cleared all projects, disabled compatibility mode and tried to import another project, that does not need compatibility but comes from a cracked ETS5 (unsigned).

>>Importing a cracked ETS5 .knxproj with 20 devices does work for me (ETS6N), so its perhaps a ETS6C issue?
I also got the license error when trying to import the unsigned project to ETS6N.

Then I imported a signed project from a licensed ETS5 -> no error here

Then I tried to export the same signed project from ETS6N and got the same “This project cannot be exported with the licenses installed” error.
So ETS6N and ETS6C behave exactly the same for me.

Then I created a fresh new project, added 5 devices and was able to export the project. After adding another device (6) I got the error on export again. So ETS6 is checking the demo devices count.

[magicufParticipant 2022-12-16 at 18:56 Post count: 5]

#33517 In reply to: xxx |

compatibility mode, ETS6C

[sinn3rParticipant 2022-12-16 at 18:54 Post count: 369]

#33514 In reply to: xxx |

@magicuf and are you running in compatibility mode or in 64bit mode? ETS should have noticed you on project import if it needs to switch compatibility mode on.

[m00Participant 2022-12-16 at 18:09 Post count: 41]

#33507 In reply to: xxx |

@debbe you can get a Lite-Cloud-License for free if you complete the ETS6 Web Training:
https://wbt6.knx.org/login/index.php
Just register with fake name/address/phone etc., complete the course, fill out the survey and you’ll get a cloud license which can sign a project with up to 10 devices. There should be a possibility to trick the ets6 to use that lite license to sign (or certify, as thats how its called in the ETS6 code) a project with more devices while exporting.

I think the issue is that the converter from ETS5 to ETS6 also checks for a valid certificate. That could possibly be patched out in the “Knx.Ets.CvNext.dll” File.

Importing a cracked ETS5 .knxproj with 20 devices does work for me (ETS6N), so its perhaps a ETS6C issue?

[sinn3rParticipant 2022-12-16 at 17:36 Post count: 369]

#33504 In reply to: xxx |

@magicuf How many devices are in your project?
Are you logged in to knx.org with ETS?

My project has 85 devices and I always click cancel in the login window.

[magicufParticipant 2022-12-16 at 16:49 Post count: 5]

#33501 In reply to: xxx |

ETS6C works now and importing unsigned file from ETS5 (with dummy workaround) works as well!!!
@sinn3r: with my project also the export from ETS6 works without error message.

[sinn3rParticipant 2022-12-16 at 15:59 Post count: 369]

#33498 In reply to: xxx |

Ok, new problem:
When trying to export a project from your cracked ETS6 it won’t work.
The error is “Dieses Projekt kann nicht mit den installierten Lizenzen exportiert werden.” which means something like “This project cannot be exported with the licenses installed.”
You can try it yourself in the project overview window if you hover over your project and select “Export”.