-
Notifications
You must be signed in to change notification settings - Fork 285
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
Add echarge_cpu2 to latest #2294
Conversation
The close was a mistake. |
Link to adapter repo: https://github.com/LembkeM/ioBroker.echarge_cpu2 |
Result from manual adapter checker run: [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.echarge_cpu2" |
First of all - THANK YOU for the time and effort you spend to maintain this adapter. I would like to give some (preliminary) feedback based on my personal oppinion. This is NOT an offical review and @Apollon77 might have several additional suggestions or even a different oppinion to one or the other statement. Please feel free to contact him (or wait for a response from him) if you cannot follow my suggestsions or before you spend major effort.
further checks aborted Some more quick check notes only: The main code seems to read information from the device exactly ONCE. I cannot assume that this is the desired behavior. If any exception is raised nothing is logged at all (catch area is empty) onStateChange code exists but is not used Several paramaters seem to be unused at code, passwords should be encrypted
roles should be checked. See info.* roles for matching roles to avoid the general text role if possible. I suggest to close this PR as this adapter seems to be work-in-progress currently. Please create a new PR as soon as the adapter is complete and has all functionality implemnted desired for the first release. Adapters added to latest repository must be already working. Thanks for reading and evalutaing this suggestions. |
These steps are already done. |
OK, adapterchecker is OK now, llogo is OK and Releasenotes are a little bit short - would be fine to read what functionality the adapter provides - but this will be definitly no blocking point. BUT An the other remarks (like template code without any functionality recogniozed) is still present. So please could you describe a little bit more in detail, what you think the adapter is doing and check the unused onState code and explyin the password checking routines expected functionality. Maybe I'm incorrect - but the code looks like a proof of concept currently with not much real functionaliy. If I missed soimething - I'm sorry - but please respond to the sugestions:
|
Hi, almost done.
Thanks |
Roles see https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/stateroles.md JsonConfig /react |
Discord woild be ok too as it is mirrored at telegram |
Thanks for the link. So last one needs to be finished. |
Hi, |
No - currently no action required from your side as far as I can see. Sorry for the long delay. Apollon77 will take care of the (meantime large) number of open latest request after his holidays. Please be patient one or two additional weeks. |
That's not a problem, thanks for the reply. Holidays are important and hope he will have good ones. Thanks for your help. |
Automated adapter checkerioBroker.echarge_cpu2👍 No errors found
Add comment "RE-CHECK!" to start check anew |
I would like to give some additional (preliminary) feedback based on my personal oppinion. This is NOT an offical review and @Apollon77 might have several additional suggestions or even a different oppinion to one or the other statement. Please feel free to contact him (or wait for a response from him) if you cannot follow my suggestsions or before you spend major effort.
Thanks for reading and evaluating this suggestions. Please add a comment when you have reviewed and fixed the suggestionsor at least commented the suggestions and you think the adapter is ready for a re-review! |
How shall we continue? |
Any news? Please let us know if you still are woirking / maintain this adapter - a simple I'll continue as soon as I have time would be ok. If there is no reaction until 15.12.2023 this PR will be closed. @Apollon77 FYI |
A kind reminder. Please drop any comment if you still maintain this adapter and will fix testing matrix in a resonable time. If there is no reaction until 15.12.2023 this PR will be closed. @Apollon77 FYI |
As there has been no reaction to latest comments.I will close this PR now. THANKS that you spent time to implement an adapter. If you find time to finalize and release the adapter at any tim ein future you are very welcome. Please simply create new PR in this case. If you have any quetsions, feel free to contact us |
No description provided.