Open chrispi68 opened 1 year ago
same here :-(
Adapter version: 0.6.3 Unify Controller: V 7.3.83 (current version) Unify Device: UniFi OS UDM SE 3.0.18
and same here.
Adapter version: 0.6.4 Unify Controller: V 7.3.83 (current version) Unify Device: UniFi OS UDM SE 3.0.20
Still not working? I have the exact same error when i try to disable POE for a Port
Still not working?
As the issue is still open, the problem is still not solved and its no surprise that you can reproduce it. I cannot tell when a developer who has access to a testing environment has time ti check / fix this.
Everybode is welcome to provide a PR.
cannot tell when a developer who has access to a testing environment has time ti check / fix this.
In this case, the feature should be removed because it costs a lot of time to find out, that it does not work.
I know, the developers are working for free, but the basic functionality should be present.
cannot tell when a developer who has access to a testing environment has time ti check / fix this.
In this case, the feature should be removed because it costs a lot of time to find out, that it does not work.
I know, the developers are working for free, but the basic functionality should be present.
This too requires a developer to do it :-)
This too requires a developer to do it :-)
In this case, this project is dead.
This too requires a developer to do it :-)
In this case, this project is dead.
Feel free to go ahead and join the project and fix and enhance the project to your liking. Complaining is always easy, taking initiatives is the hard part!
Feel free to go ahead and join the project and fix and enhance the project to your liking. Complaining is always easy, taking initiatives is the hard part!
This is not about complaining. The point is that no one feels responsible for this GitHub repository and users think that it is maintained. If needed, I would be happy to add a note to the readme file.
This project is maintained as you can see in the commit logs. Probably not enough for your personal feeling, but this is not the most relevant point here. And no, just changing the README is not what we are interested in, thus come back if you have more knowhow to share than just complains..
This project is maintained as you can see in the commit logs. Probably not enough for your personal feeling, but this is not the most relevant point here. And no, just changing the README is not what we are interested in, thus come back if you have more knowhow to share than just complains..
Your statement is a disgrace to all software testers.
This project is maintained as you can see in the commit logs. Probably not enough for your personal feeling, but this is not the most relevant point here. And no, just changing the README is not what we are interested in, thus come back if you have more knowhow to share than just complains..
Your statement is a disgrace to all software testers.
As yours' is for all developers investing lot of their free time into free software for others.
But lets come back to the point: If there is a bug and it is well reproducible then simply keep this issue ticket open here and if a developer feels it is important / relevant enough he will fix it.
As yours' is for all developers investing lot of their free time into free software for others.
No, I am just reporting a bug and answering questions like "Still not working?I have the exact same error when i try to disable POE for a Port" from other users.
But lets come back to the point: If there is a bug and it is well reproducible then simply keep this issue ticket open here and if a developer feels it is important / relevant enough he will fix it.
As you may know, software development is an interplay between developers and testers and participation in discussions. If you don't like that, you haven't understood open source software development.
As yours' is for all developers investing lot of their free time into free software for others.
No, I am just reporting a bug and answering questions like "Still not working?I have the exact same error when i try to disable POE for a Port" from other users.
Understood.
But lets come back to the point: If there is a bug and it is well reproducible then simply keep this issue ticket open here and if a developer feels it is important / relevant enough he will fix it.
As you may know, software development is an interplay between developers and testers and participation in discussions. If you don't like that, you haven't understood open source software development.
Well, looking at yours' and mine GitHub profile tells me a different story. But as said, lets stop this. I will have a look at that issue if time permits it.
Great, thank you guys. I wish I had the skills to do my part on this or other projects. But that’s way ahead of what I can do.
Just a hint, if you want to deactivate PoE o ports you have to go into Unifi controller and change the port to manual mode otherwise it will not work! For me it works perfectly, switching poE Power on ports on and off every moring and evening.
When I change port-per-enabled to "False", I get this error:
[switchPoeOfPort site undefined] error: Cannot set properties of undefined (setting 'poe_mode'), stack: TypeError: Cannot set properties of undefined (setting 'poe_mode') at Unifi.switchPoeOfPort (/opt/iobroker/node_modules/iobroker.unifi/main.js:1051:62)
Enabling or disabling PoE power does not work. The error appears only once in the log, although I have tried several times to disable or enable PoE without success.
Adapter version: 0.6.3 Unify Controller: V 7.3.83 (current version) Unify Device: UniFi OS UDM SE 3.0.13