-
Notifications
You must be signed in to change notification settings - Fork 12
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
Resolve: Moonraker warnings found #83
Comments
After the update I had the same problem today. |
why not write it. what do I need to edit in moonraker.conf? do you comment on the lines? then why is it so difficult to specify the full path? |
I don't understand what you're trying to ask? The origin of the issue is the fact that I removed the old install script in favor of a new one that uses the installer rather than a raw shell script to install the companion. |
Found this post when I ran into the same issue. I thought I would shed a little light on it if you haven't figured it out yet. It is straight forward....Log into your printer>Under your configuration tab>modify moonraker.conf (the line item might not be the exact number but it will be close) change the line to the new one>save and restart and the error should be corrected. Hope that helps. @Clon1998 - I appreciate you posting a fix, very helpful. |
I just installed opennept4une today and I'm having the same problem. Even if I rewrite it to look like your screen shot, the problem still persists.Please, what am I doing wrong? |
Did you restart moonraker after saving the file? |
I dont understand: (the line item might not be the exact number but it will be close) change the line to the new one> |
You'll need to locate the path of the mobileraker companion within the file system of the printer. |
What do you mean? Locate the old line and change it to the new one, save and restart, you should be good from there. I was simply stating that the line # might differ depending on yours, don’t go by the number, go by the content.
Hope that helps.
…Sent from my iPhone
On May 20, 2024, at 11:24 AM, MichalOrel ***@***.***> wrote:
Found this post when I ran into the same issue. I thought I would shed a little light on it if you haven't figured it out yet. It is straight forward....Log into your printer>Under your configuration tab>modify moonraker.conf (the line item might not be the exact number but it will be close) change the line to the new one>save and restart and the error should be corrected. Hope that helps.
I dont understand: (the line item might not be the exact number but it will be close) change the line to the new one>
Please, could you elaborate a little bit?
—
Reply to this email directly, view it on GitHub<#83 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKA4MA3G6UAB326YO4AJVY3ZDIPS3AVCNFSM6AAAAABDX6Q3HCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQG44DINJWHA>.
You are receiving this because you commented.Message ID: ***@***.***>
|
I am a complete amateur at this.I had no idea how to do it, what line and where to find it. |
Did you install Klipper yourself? When you log into your printer through the GUI, there should be tabs on the left side running down the left side. Go to the tab that has your config files, you will need to alter the moonraker config file. When you open the file look through the lines and locate the one that resembles what needs to be changed and change it (Onky change what needs to be changed). Then save the file and restart Klipper / Moonraker. The error should be gone if you did correctly. Hope that is a little more detailed for you. Good Luck
…Sent from my iPhone
On May 24, 2024, at 2:33 AM, MichalOrel ***@***.***> wrote:
What do you mean? Locate the old line and change it to the new one, save and restart, you should be good from there. I was simply stating that the line # might differ depending on yours, don’t go by the number, go by the content. Hope that helps.
I am a complete amateur at this.I had no idea how to do it, what line and where to find it.
It's hard to solve such things without detailed guidance.
Anyway, I solved it via Kiauh update.
—
Reply to this email directly, view it on GitHub<#83 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKA4MA4VZ7WUMWRFHT7XRV3ZD3UNLAVCNFSM6AAAAABDX6Q3HCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRYG44TQOBUGM>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Hello, I installed openNept4une about three weeks ago. I had the exact same error messages. I found this thread and went to the moonraker config to find it already set to the line change mentioned above. [update_manager mobileraker] There is one difference, and that is the 6th line. Mine doesn't say "virtualenv" So far this is the only place I can find that mentions this issue exactly as I'm seeing it , but the problem persists. |
To those who installed Open Neptune and having trouble with this I found that I had this line |
Thank you! That worked perfectly. |
As of 12/22/24, I changed it to the line above after doing a fresh install on 12/21/24. The error went away. |
If you are encountering this issue:
You will need to update the
install_script
property of the[update_manager mobileraker]
section:(Red old value, Green new value. Ignore the +,- chars)
Result:
The text was updated successfully, but these errors were encountered: