#Packages
1 messages ยท Page 1 of 1 (latest)
You add the first two lines to your configuration.yaml
Then
To have all this sensors available on your Home Assistant you just need to copy
moonraker.yamlto your packages folder and make sure you update the IP address
That would be /config/packages/moonraker.yaml
Ok so you don't need the pack1 part?
that was point to the moonraker.yaml
(Had a network outage)
Packages
You only need that if you're embedding the package in configuration.yaml, which you're not
You should see the entities or errors in your log
Thank you!! Sorry for the delay was have mega network dropouts
This seems to be taking the thumbnail art from the printer instead of the camera feed would you know how I would add a video feed to the card?
You need a camera entity for that
ok which it has but to the wrong url
camera:
- platform: generic
name: "3D Printer Thumbnail"
still_image_url: http://<moonraker-ip-address>:7125/server/files/gcodes/{{ states("sensor.3d_printer_object_thumbnails") }}
verify_ssl: false
to get that working as it was old code I changed it to gcodes/.thumbs/
Then it displayed the jpg there.
but for the camera its at http://<moonraker-ip-address>/webcam/?action=stream
That's done in the UI these days, see https://www.home-assistant.io/integrations/generic#stream-source
What "rotation settings"?
Interesting... #cameras-archived may know more about that
Ok thank you for all your help!
@clear geode
I'm using the moonraker packages with good success except for one thing. If the printed file is within a subdirectory of the gcodes folder, the relative_path used for the thumbails is not the right path. If I go in the Developer tool and change the state of the 3d_printer_object_thumbnails and add the subdirectory in front of it, then the Picture Card displays the thumbnails.
Also another issue but that one I found a fix was if the file name contained a "+" character, the API would fail for the metadata or anything that used the sensor.3d_printer_current_print in the api call.
I modified the call and urlencoded the path
resource_template: "http://<moonraker_ip_address>:7125/server/files/metadata?filename={{ states(('sensor.3d_printer_current_print')) |urlencode}}"
@tardy robin Ok? ... and ... you tagged me because?
Sorry I thought you were one the developer. My bad ๐ฆ
Tagging devs to demand their attention goes down even more poorly ๐
If you've found a bug, open an issue
Want to see what issues are open (or were open and are now closed)?
- The core (backend) - for HA itself, and integrations
- The frontend (UI) - for cards and display issues
- The Supervisor
- HAOS
- The documentation
Don't forget to check for any alerts
If you think an upgrade broke something then:
- Downgrade to the previous version to check if it works correctly there
- If it does then change the
loggersettings for that integration todebug - Upgrade to the new version again
- Look in the logs for errors
- Open an issue, following the template provided and including the log information
I did open an issue but since many people did a pull-request on that package I'm not sure who is the original developer for this package therefore not sure I opened the issue on the right code...
Should I simply open an issue on Home Assistant, I guess not
I opened an issue here:
https://github.com/NonaSuomy/Moonraker-Home-Assistant
which is actually the person you were chatting with right before
but this seems to be a pull from 2 others