core icon indicating copy to clipboard operation
core copied to clipboard

Samsung Printer Failed to setup

Open zinsas opened this issue 2 years ago • 3 comments

The problem

With 2023.11.1, my Samsung ML-3050 printer integration not work.

What version of Home Assistant Core has the issue?

core-2023.11.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Samsung SyncThru Printer

Link to integration documentation on our website

https://www.home-assistant.io/integrations/syncthru/

Diagnostics information

The device does not support SyncThru. The integration does not connect to the Samsung ml-3050 printer, although SyncThru is present at 192.168.x.x. SSDP is enabled.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

zinsas avatar Nov 07 '23 13:11 zinsas

Hey there @nielstron, mind taking a look at this issue as it has been labeled with an integration (syncthru) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of syncthru can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign syncthru Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


syncthru documentation syncthru source (message by IssueLinks)

home-assistant[bot] avatar Nov 07 '23 13:11 home-assistant[bot]

I had similar issues with some old Samsung printer and have shifted to the custom component by @nielstron. You might consider trying that instead.

It's working for me with (by design) limited functionality.

https://github.com/nielstron/ha_syncthru

metbril avatar Nov 08 '23 19:11 metbril

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.