I’m thinking that maybe is better to open a new thread or wait to that someone notices
syncthru hasn’t changed since October. First step would be to see what http://your.printer.ip/sws/app/information/home/home.json returns
Is there any progress made somewhere?
No change until now 0.110, right?
Ill add to this. I just enabled ssdp and it shows up as discovered. However when I click on configure and enter http://your.printer.ip/sws/Index.html I get
Device does not support SyncThru
If I just enter the IP address I get
Printer state unknown, verify URL and network connectivity
However, when I go to http://your.printer.ip/sws/app/information/home/home.json I see:
{
status: {
hrDeviceStatus: 2,
status1: " Ready to Copy",
status2: "100% 01",
status3: "",
status4: ""
},
identity: {
model_name: "Samsung CLX-3180 Series",
host_name: "SEC001599876941",
location: "",
serial_num: "Z50UBAHB600049X ",
ip_addr: "192.168.1.22",
ipv6_link_addr : "FE80::215:99FF:FE87:6941/64",
mac_addr: "00:15:99:87:69:41",
admin_email: "",
admin_name: "",
admin_phone: ""
},
toner_black: {
opt: 1,
status: 0,
remaining: 60,
cnt: 479
},
toner_cyan: {
opt: 1,
status: 0,
remaining: 60,
cnt: 166
},
toner_magenta: {
opt: 1,
status: 0,
remaining: 54,
cnt: 394
},
toner_yellow: {
opt: 1,
status: 0,
remaining: 58,
cnt: 166
},
drum_black: {
opt: 0,
status: 0,
remaining: 0
},
drum_cyan: {
opt: 0,
status: 0,
remaining: 0
},
drum_magenta: {
opt: 0,
status: 0,
remaining: 0
},
drum_yellow: {
opt: 0,
status: 0,
remaining: 0
},
tray1: {
opt: 1,
paper_size1: 4,
paper_size2: 0,
paper_type: 64,
capa: 130,
status: 2
},
tray2: {
opt: 2,
paper_size1: 4,
paper_size2: 0,
paper_type: 0,
capa: 0,
status: 0
},
tray3: {
opt: 2,
paper_size1: 0,
paper_size2: 0,
paper_type: 0,
capa: 0,
status: 0
},
tray4: {
opt: 2,
paper_size1: 0,
paper_size2: 0,
paper_type: 0,
capa: 0,
status: 0
},
mp: {
opt: 0,
paper_size1: 4,
paper_size2: 0,
paper_type1: 64,
paper_type2: 63,
capa: 1,
status: 1
},
outbin: [
["BIN1", 0, 1]
],
capability: {
hdd: {opt: 2, capa: 0},
ram: {opt: 262144, capa: 262144},
scanner: {opt: 0 , capa: 0}
},
options: {
fax: 1,extendedMem: 2,wlan: 0
},
GXI_ACTIVE_ALERT_TOTAL: 0,
GXI_ADMIN_WUI_HAS_DEFAULT_PASS: 1
}
Any ideas? I will try and look at the code but pointers are appreciated. I am on 0.113.1
I get the same problem as OzGav with a samsung M2020W printer. Running HA 0.113.2.
Dear All,
I am also having the same issue with a Samsung ML-2525W printer. I have had the same problem for the last year or so, but todya, after upgrading to 0.118.0 things have changed: Now, after the update, it finds the printer as a new device:
When I click Configure, the popup window is correctly populated, but when I click Submit I get “Device does not support SyncThru” error message and the printer is not added:
If I go to the URL suggested above, I get the following response from the printer:
Invalid Request. Some Error
Apart from this, the printer works as expected, its web url works too.
If somebody has figured this out, please don’t hold it back…
Hello,
He also wants to join the topic.
Samsung printer ML-1630W.
I have exactly the same problem with adding this Syncthru printer to HA
I try: http://192.168.88.184/sws/app/information/home/home.json
result: Invalid Request. Some Error
and http://192.168.88.184/sws/Index.html
result: Invalid Request. Some Error
HA recognizes this printer but cannot add it.
Message: “The machine does not support SyncThru”
Has anyone solved this problem or have any suspicions what is wrong?
Regards
I think you will be best opening an issue on GitHub https://github.com/nielstron/pysyncthru/issues
I see from the web that your printer does support syncthru but I am pretty sure that the python library interrogates the json data that is returned from home.json. Since your printer is returning an error with that URL it may be impossible to get it to work. If you can find a different URL for your printer that returns the JSON data then it might be possible to get a fix…
Hey @OzGav @blackskull182 are your issues still unresolved?
@Tyski I still don’t know what causes this error. I’ve had a conversation with @viktak on resolving this issue (see Issue when conneting to ML-2525W · Issue #43563 · home-assistant/core · GitHub), maybe you are able to figure something out here? There are two ways to resolve this: either we find out how to block those printers that do not actually support syncthru in the json manner I use them currently - or we find how they are actually publishing their data
No I am all good since the last updates to the library. Was just trying to help out here…if I could?!
@Tyski If you still have this issue, you might want to try the custom component I made that is a bit more powerful than the core syncthru component