New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Create Token" isn't possible without PIN #532
Comments
I have activated "Einstellungen->Benutzerverwaltung->Benutzerrechte" and hereby generated an "Administrator-PIN". Using this PIN but Token Request fails. |
That's because if you activate "Administrator-PIN" the "System-PIN" will be deactivated. Unfortunately the "System-PIN" is still necessary for activate the token button.... |
I don't know if this information is helpfull for fixing the bug: with version 1.21.1 (2024-01-15) the create token button is still working. |
The button is only working, if you still have a system PIN. EQ3 removed the system PIN. The API is working fine without PIN. it is just the adapter frontend that is designed to get the system PIN as a mandatory input to make the Generate button active. Shouldn’t be a big thing. |
workaround see #539 (comment) |
@Apollon77 @mcm1957 This issue is not the same like #539 , in 539 there is wrote from impossibility to connect the current version of this adapter to HMIP. And it's right, it's of course a very significant bug! Currently nobody can connect his new HMIP to iobroker with latest version of this adapter, it's not working, yet. Here at this topic we tell about the ability to type in no pin to create a token. But it dosen't matter...on no way you can create a token and get your HMIP working with iobroker, not with and not without pin, if you try to create a token everytime in logs comes this error: Just a fallback to an older version ≤1.19 gives the ability to Set up an new HMIP connection to iobroker. Please fix it highly prioritized! |
@GermanBluefox Please make the PIN an optional field in jsconfig and mainly also in the custom component. Thank you |
@GermanBluefox I just pulled the 1.23 from the beta repository and created a new instance from that. Token creation without filling the PIN Field is still not possible. Wasn't this the aim of that fix? |
I'm not aware that 1.23.0 conatins any code changes. Please see changelog. I'll check why this issue has been marked fixed. |
The dev seems not understand, which the problem is about, isn't it? 🙈 |
No that's definitly not the problem. Either the change was lost on the way between dev system and githubg (aka was not comiited) or the setting of "fixed" was done on error. At the moment this issue must be considered "not fixed". Release 1.23.0 was created due to chnages in test enviroment is independent of this issue. |
As this adapter is not usable for any Access Point that needs to be connected to ioBroker it would really be great if there could be a fix. It was reported almost 2 month ago. |
In fact 1.23 was never supposed to contain the fix and was published before ... so please donot confuse things. es we will clrify why Denis set fixed :-) |
Ok, now commit is there. So if anyone likes please try GitHub version ... |
I corrected the second part - F711 - no difference |
Ok I will prepare a release |
@loskrachos wrote at 29.4.2024:
One additional question / remark - not really related to problem but to clearify what you have installed at which time: |
I switched to Beta releases and was able to install 1.23 from the release list 🤷♂️ |
fixed with 1.23.1 |
You do not spam if you report a problem. Don't worry. BUT: Nobody told you to install from github. Installing from github should be done ONLY when adviced by developer. Releases at Github can contain any intermediate and even non working or broken code, Please install using latest repository and either admin interface (preferred) or iobroker cli command. |
Thought it might be helpful… testing it asap. when do you think it is released? I have no experience how long it takes from commit to the release. |
npm released, should become in latest over night |
Was available short after creating the release. I did an extra update due to urgency. So attime of my last posting it was already available at latest. Please check latest always when waiting for a fix. And use Check for updates" button to refresh your local cache too (local cache is normally updates only once a day) |
I am going nuts... "TOKEN GENERIEREN" is now active, as soon as I enter anything. Thanks for that! But Token generation isn't working. I have set up a completely new ioBroker on Raspi4 - only adapter I installed additionally was hmip 1.23.1 from beta repository. (in stable only 1.22 is available) I enter SGTIN and get immediately "Während der Token-Generierung ist ein Fehler aufgetreten. Sehen Sie sich die Protokolle an" System completely new and clean --> if you like we can have a remote session to give you the chance to get more information Protocol:
|
OK - I'll reopen of course and ask dev to check. |
Thanks for the complet log provided. In the meantime I would like to ask whether you could try to install an older working adapter version and to create a debug log with working token generation. Maybe we could detect the difference with this information. |
anything that might be helpful... but is there really an older version, that can handle the APs with the "switched off" System PIN? As written, I can also offer to support a remote session with my hardware. It is a test system, we can do whatever neccessary. We can temporarily switch to mail or other communication channels (WA etc.) I would really be happy to support! just mailto:loskrachos@gmx.de |
Well, there : I do not have any HMIP HW so I do not really know hwo to use and it makes no sense to try a remote session. Sorry. The main dev is currently busy outside germany and cannot work on this at the meoment. |
Hi Guys, i agree to that, with a version >1.20 it's not possible to generate a token yet and in last consequence this adapter in newest version is broken and for new users or new installed systems currently useless caused of impossibility to register/first connect with an hmip gateway. The used hardwae dosen't matter, i've tested it on proxmox, fully installed Debian, Ubuntu and in rpi4 and 5 with raspbian and ubuntu, in every systemscenario the same issue (No token generation possible). Strongly need a Dev now to check/analyze and fix, it's a major bug (this adapter is partly unusable a few months ago since release of 1.20!) and should be max prioritized. My workaround at #539 (comment) works well, but this shouldn''t be best solution to get the iobroker work with hmip. Kind regards |
I just tried the workaround and indeed it is working! Here is the Log: (only debug, not silly)
|
Congratulations 😉 But this adapter in latest versions is still not working for token generation, strongly a bugfix needed. |
Hi there. |
The old version (1.21.1 from January) of the adapter is still working fine. So I assume its just a bug in the newer versions. Probably no one tested to add a new device. |
Can you please recheck the following commit:
|
It's most likely a problem with the adapter. And thanks to all who provided logs. Maybe this will help to identify the difference. |
Adapter version: 1.22.0
JS-Controller: 5.0.19
The "Create Token"-Button has to be clickable without specifying a PIN.
For more information please see:
ioBroker-Forum
The text was updated successfully, but these errors were encountered: