Ideas
0
Completed
HWID Problems
Theo Derks - NL (distributor) 10 years ago
in i2 Control V2.2
•
updated by Olga (expert) 10 years ago •
2
Hi,
i think many, many installers have had problems with the update to 2.2.3 the last weeks.
This was a very bad situation, and not very good for our reputation.
My idea is the next:
Make it possible to save the HWID that is used in the i2 Control. --> save the 'history' of used HWID's in the project file, (like a system-token). If the i2 Control is discovering the HWID is changed, give the user a warning, but don't DE-ACTIVATE the license!!! The end-user can call his installer with the warning: "Help, my app is warning me the HWID is changed'; and the installer has some time (for example 1 week) to fix this problem.
2 advantages: the user can continue to control his smart-house, and the installer can schedule an appointment to fix the problem and change the license.
It's a safe solution, because the HWID can only change locally, inside the project; so mis-use is (in my opinion) not possible.
Everybody happy!
Thanks
Theo
i think many, many installers have had problems with the update to 2.2.3 the last weeks.
This was a very bad situation, and not very good for our reputation.
My idea is the next:
Make it possible to save the HWID that is used in the i2 Control. --> save the 'history' of used HWID's in the project file, (like a system-token). If the i2 Control is discovering the HWID is changed, give the user a warning, but don't DE-ACTIVATE the license!!! The end-user can call his installer with the warning: "Help, my app is warning me the HWID is changed'; and the installer has some time (for example 1 week) to fix this problem.
2 advantages: the user can continue to control his smart-house, and the installer can schedule an appointment to fix the problem and change the license.
It's a safe solution, because the HWID can only change locally, inside the project; so mis-use is (in my opinion) not possible.
Everybody happy!
Thanks
Theo
Customer support service by UserEcho
We are working under this mechanism. We'll take into account your idea!
Thank you!
Best regards,
iRidium mobile Support Team