-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
Zigbee Console grep is not working anymore since upgrade M4 -> M6 #766
Comments
The zigbee console commands come from a different project so the integration has limitations - I've had a quick look and don't see any easy way to change this. I think it's pretty minor so propose to close as "Wont Fix" if you're ok with that. |
Hi chris, Thanks for the fast supply. BR |
I can only assume something has changed in the core or karaf then as nothing changed in the binding.
You can normally search in other ways - it's not like there's thousands of lines like a logfile. Certainly if you use linux or mac it's easy to use the search option in the console - possibly this doesn't work in Windows (I don't use windows so am not sure). We can leave this open, but I am not able to spend time looking at this and really consider it a small inconvenience where the pain of trying to fix it right now doesn't balance the benefit (IMHO of course :) ). |
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/openhab-3-3-milestone-discussion/132715/163 |
Perhaps it's caused by openhab/openhab-core#2961? |
I propose that this should be closed or moved to the core as it doesn't seem to be an issue with the binding - certainly nothing changed in the way the console works. |
THX @wborn , @cdjackson , |
Short final feedback from my side I've just updated to OH 3.3.0.RC1. |
Great! It was fixed with openhab/openhab-core#3012. |
Hi all,
it seems the grep cannot filter the output of the Zigbee command.
For ohter commands like bundle:listr it seems to work.
BR
/Franz
The text was updated successfully, but these errors were encountered: