NEWS
[gelöst] synology adapter gelb
ioBroker Allgemein
59
Beiträge
7
Kommentatoren
5.7k
Aufrufe
6
Watching
-
Nur kurz ... test mal mit HTTP Verbindung ...
also Haken raus beim Adapter ... den Rest dann bei der Synology umstellen . -
@Glasfaser
Habe ich gerade versucht. Geht auch nicht.
Das Problem liegt an der Anmeldung.
Siehe Log
status gelb:
Alero -
Der Log sagt nicht viel aus ,stelle den Synology Adapter mal auf DEBUG !
Was sagt dann der Log ?
weil .... Code 400
-
@Glasfaser
hi, wo kann ich das auf debug umstellen. finde es nicht. -
@Glasfaser
Hi, ich weiss. hatte es nicht gefunden weil der expertenmodus nicht drin war. :-)synology.0 2021-01-06 10:22:51.713 debug (21472) * Get info from (firstPoll) api: DSM method: getPollingData params: {} synology.0 2021-01-06 10:22:51.713 debug (21472) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}} synology.0 2021-01-06 10:22:51.712 debug (21472) ----------------------------------------------------------------------------------------------------- synology.0 2021-01-06 10:22:51.236 info (21472) starting. Version 0.1.18 in /opt/iobroker/node_modules/iobroker.synology, node: v10.20.1 synology.0 2021-01-06 10:22:50.929 debug (21472) statesDB connected synology.0 2021-01-06 10:22:50.928 debug (21472) States connected to redis: 127.0.0.1:9000 synology.0 2021-01-06 10:22:50.924 debug (21472) States create System PubSub Client synology.0 2021-01-06 10:22:50.923 debug (21472) States create User PubSub Client synology.0 2021-01-06 10:22:50.921 debug (21472) Redis States: Use Redis connection: 127.0.0.1:9000 synology.0 2021-01-06 10:22:50.920 debug (21472) objectDB connected synology.0 2021-01-06 10:22:50.918 debug (21472) Objects connected to redis: 127.0.0.1:9001 synology.0 2021-01-06 10:22:50.912 debug (21472) Objects client initialize lua scripts synology.0 2021-01-06 10:22:50.912 debug (21472) Objects create User PubSub Client synology.0 2021-01-06 10:22:50.912 debug (21472) Objects create System PubSub Client synology.0 2021-01-06 10:22:50.911 debug (21472) Objects client ready ... initialize now synology.0 2021-01-06 10:22:50.899 debug (21472) Redis Objects: Use Redis connection: 127.0.0.1:9001 -
@Glasfaser
Hi, ich weiss. hatte es nicht gefunden weil der expertenmodus nicht drin war. :-)synology.0 2021-01-06 10:22:51.713 debug (21472) * Get info from (firstPoll) api: DSM method: getPollingData params: {} synology.0 2021-01-06 10:22:51.713 debug (21472) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}} synology.0 2021-01-06 10:22:51.712 debug (21472) ----------------------------------------------------------------------------------------------------- synology.0 2021-01-06 10:22:51.236 info (21472) starting. Version 0.1.18 in /opt/iobroker/node_modules/iobroker.synology, node: v10.20.1 synology.0 2021-01-06 10:22:50.929 debug (21472) statesDB connected synology.0 2021-01-06 10:22:50.928 debug (21472) States connected to redis: 127.0.0.1:9000 synology.0 2021-01-06 10:22:50.924 debug (21472) States create System PubSub Client synology.0 2021-01-06 10:22:50.923 debug (21472) States create User PubSub Client synology.0 2021-01-06 10:22:50.921 debug (21472) Redis States: Use Redis connection: 127.0.0.1:9000 synology.0 2021-01-06 10:22:50.920 debug (21472) objectDB connected synology.0 2021-01-06 10:22:50.918 debug (21472) Objects connected to redis: 127.0.0.1:9001 synology.0 2021-01-06 10:22:50.912 debug (21472) Objects client initialize lua scripts synology.0 2021-01-06 10:22:50.912 debug (21472) Objects create User PubSub Client synology.0 2021-01-06 10:22:50.912 debug (21472) Objects create System PubSub Client synology.0 2021-01-06 10:22:50.911 debug (21472) Objects client ready ... initialize now synology.0 2021-01-06 10:22:50.899 debug (21472) Redis Objects: Use Redis connection: 127.0.0.1:9001 -
da fehlt sehr viel !
stoppe den Adapter und dann starten ...
und dann ab Adapterstart den ganzen LOG zeigen !
@Glasfaser hi, da ist leider nicht mehr.
-
da fehlt sehr viel !
stoppe den Adapter und dann starten ...
und dann ab Adapterstart den ganzen LOG zeigen !
-
@Glasfaser
Hi, weiso port 9000 und 9001?Alero
-
@Alero sagte in synology adapter gelb:
Hi, weiso port 9000 und 9001?
Bitte nicht beachten ... das ist REDIS !
wo ist denn die Error Meldung ?
-
-
@Glasfaser
das wollte ich auch gerade fragen -
Die Error Meldung ist aber neu ... hat nichts mit deiner anderen Meldung zu tun .
Was hast du denn verändert .@Glasfaser
Fehler gefunden für die falsche IP.
hier das neue Log.synology.0 2021-01-06 10:37:20.785 debug (10931) * Get info from (firstPoll) api: DSM method: getPollingData params: {} synology.0 2021-01-06 10:37:20.784 debug (10931) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}} synology.0 2021-01-06 10:37:20.784 debug (10931) ----------------------------------------------------------------------------------------------------- synology.0 2021-01-06 10:37:20.783 error (10931) *** ERROR : src: sendPolling syno[dsm][getPollingData] To use the adapter, the user must be in the Administrators group! code: 400 message: No such account or incorrect password synology.0 2021-01-06 10:37:20.783 debug (10931) * No response, read next. synology.0 2021-01-06 10:37:19.552 debug (10931) * Get info from (firstPoll) api: DSM method: getPollingData params: {} synology.0 2021-01-06 10:37:19.552 debug (10931) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}} synology.0 2021-01-06 10:37:19.552 debug (10931) ----------------------------------------------------------------------------------------------------- synology.0 2021-01-06 10:37:19.551 error (10931) *** ERROR : src: sendPolling syno[dsm][getPollingData] To use the adapter, the user must be in the Administrators group! code: 400 message: No such account or incorrect password synology.0 2021-01-06 10:37:19.550 debug (10931) * No response, read next. synology.0 2021-01-06 10:37:18.424 debug (10931) * Get info from (firstPoll) api: DSM method: getPollingData params: {} synology.0 2021-01-06 10:37:18.423 debug (10931) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}} synology.0 2021-01-06 10:37:18.423 debug (10931) ----------------------------------------------------------------------------------------------------- synology.0 2021-01-06 10:37:18.422 error (10931) *** ERROR : src: sendPolling syno[dsm][getPollingData] To use the adapter, the user must be in the Administrators group! code: 400 message: No such account or incorrect password synology.0 2021-01-06 10:37:18.421 debug (10931) * No response, read next. synology.0 2021-01-06 10:37:16.976 silly (10931) States system redis pmessage system.adapter.synology.0.logLevel/system.adapter.synology.0.logLevel:{"val":"silly","ack":true,"ts":1609925836970,"q":0,"from":"system.adapter.synology.0","lc":1 synology.0 2021-01-06 10:37:16.955 debug (10931) * Get info from (firstPoll) api: DSM method: getPollingData params: {} synology.0 2021-01-06 10:37:16.955 debug (10931) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}} synology.0 2021-01-06 10:37:16.955 debug (10931) ----------------------------------------------------------------------------------------------------- synology.0 2021-01-06 10:37:16.458 info (10931) starting. Version 0.1.18 in /opt/iobroker/node_modules/iobroker.synology, node: v10.20.1 synology.0 2021-01-06 10:37:16.280 debug (10931) statesDB connected synology.0 2021-01-06 10:37:16.279 debug (10931) States connected to redis: 127.0.0.1:9000 synology.0 2021-01-06 10:37:16.275 debug (10931) States create System PubSub Client synology.0 2021-01-06 10:37:16.274 debug (10931) States create User PubSub Client synology.0 2021-01-06 10:37:16.271 debug (10931) Redis States: Use Redis connection: 127.0.0.1:9000 synology.0 2021-01-06 10:37:16.271 debug (10931) objectDB connected synology.0 2021-01-06 10:37:16.269 debug (10931) Objects connected to redis: 127.0.0.1:9001 synology.0 2021-01-06 10:37:16.263 debug (10931) Objects client initialize lua scripts synology.0 2021-01-06 10:37:16.263 debug (10931) Objects create User PubSub Client synology.0 2021-01-06 10:37:16.262 debug (10931) Objects create System PubSub Client synology.0 2021-01-06 10:37:16.261 debug (10931) Objects client ready ... initialize now synology.0 2021-01-06 10:37:16.249 debug (10931) Redis Objects: Use Redis connection: 127.0.0.1:9001 host.iobroker 2021-01-06 10:37:15.898 info instance system.adapter.synology.0 started with pid 10931 synology.0 2021-01-06 10:37:16.976 silly (10931) States system redis pmessage system.adapter.synology.0.logLevel/system.adapter.synology.0.logLevel:{"val":"silly","ack":true,"ts":1609925836970,"q":0,"from":"system.adapter.synology.0","lc":16 synology.0 2021-01-06 10:37:16.955 debug (10931) * Get info from (firstPoll) api: DSM method: getPollingData params: {} synology.0 2021-01-06 10:37:16.955 debug (10931) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}} synology.0 2021-01-06 10:37:16.955 debug (10931) ----------------------------------------------------------------------------------------------------- synology.0 2021-01-06 10:37:16.458 info (10931) starting. Version 0.1.18 in /opt/iobroker/node_modules/iobroker.synology, node: v10.20.1 -
@Glasfaser
Fehler gefunden für die falsche IP.
hier das neue Log.synology.0 2021-01-06 10:37:20.785 debug (10931) * Get info from (firstPoll) api: DSM method: getPollingData params: {} synology.0 2021-01-06 10:37:20.784 debug (10931) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}} synology.0 2021-01-06 10:37:20.784 debug (10931) ----------------------------------------------------------------------------------------------------- synology.0 2021-01-06 10:37:20.783 error (10931) *** ERROR : src: sendPolling syno[dsm][getPollingData] To use the adapter, the user must be in the Administrators group! code: 400 message: No such account or incorrect password synology.0 2021-01-06 10:37:20.783 debug (10931) * No response, read next. synology.0 2021-01-06 10:37:19.552 debug (10931) * Get info from (firstPoll) api: DSM method: getPollingData params: {} synology.0 2021-01-06 10:37:19.552 debug (10931) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}} synology.0 2021-01-06 10:37:19.552 debug (10931) ----------------------------------------------------------------------------------------------------- synology.0 2021-01-06 10:37:19.551 error (10931) *** ERROR : src: sendPolling syno[dsm][getPollingData] To use the adapter, the user must be in the Administrators group! code: 400 message: No such account or incorrect password synology.0 2021-01-06 10:37:19.550 debug (10931) * No response, read next. synology.0 2021-01-06 10:37:18.424 debug (10931) * Get info from (firstPoll) api: DSM method: getPollingData params: {} synology.0 2021-01-06 10:37:18.423 debug (10931) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}} synology.0 2021-01-06 10:37:18.423 debug (10931) ----------------------------------------------------------------------------------------------------- synology.0 2021-01-06 10:37:18.422 error (10931) *** ERROR : src: sendPolling syno[dsm][getPollingData] To use the adapter, the user must be in the Administrators group! code: 400 message: No such account or incorrect password synology.0 2021-01-06 10:37:18.421 debug (10931) * No response, read next. synology.0 2021-01-06 10:37:16.976 silly (10931) States system redis pmessage system.adapter.synology.0.logLevel/system.adapter.synology.0.logLevel:{"val":"silly","ack":true,"ts":1609925836970,"q":0,"from":"system.adapter.synology.0","lc":1 synology.0 2021-01-06 10:37:16.955 debug (10931) * Get info from (firstPoll) api: DSM method: getPollingData params: {} synology.0 2021-01-06 10:37:16.955 debug (10931) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}} synology.0 2021-01-06 10:37:16.955 debug (10931) ----------------------------------------------------------------------------------------------------- synology.0 2021-01-06 10:37:16.458 info (10931) starting. Version 0.1.18 in /opt/iobroker/node_modules/iobroker.synology, node: v10.20.1 synology.0 2021-01-06 10:37:16.280 debug (10931) statesDB connected synology.0 2021-01-06 10:37:16.279 debug (10931) States connected to redis: 127.0.0.1:9000 synology.0 2021-01-06 10:37:16.275 debug (10931) States create System PubSub Client synology.0 2021-01-06 10:37:16.274 debug (10931) States create User PubSub Client synology.0 2021-01-06 10:37:16.271 debug (10931) Redis States: Use Redis connection: 127.0.0.1:9000 synology.0 2021-01-06 10:37:16.271 debug (10931) objectDB connected synology.0 2021-01-06 10:37:16.269 debug (10931) Objects connected to redis: 127.0.0.1:9001 synology.0 2021-01-06 10:37:16.263 debug (10931) Objects client initialize lua scripts synology.0 2021-01-06 10:37:16.263 debug (10931) Objects create User PubSub Client synology.0 2021-01-06 10:37:16.262 debug (10931) Objects create System PubSub Client synology.0 2021-01-06 10:37:16.261 debug (10931) Objects client ready ... initialize now synology.0 2021-01-06 10:37:16.249 debug (10931) Redis Objects: Use Redis connection: 127.0.0.1:9001 host.iobroker 2021-01-06 10:37:15.898 info instance system.adapter.synology.0 started with pid 10931 synology.0 2021-01-06 10:37:16.976 silly (10931) States system redis pmessage system.adapter.synology.0.logLevel/system.adapter.synology.0.logLevel:{"val":"silly","ack":true,"ts":1609925836970,"q":0,"from":"system.adapter.synology.0","lc":16 synology.0 2021-01-06 10:37:16.955 debug (10931) * Get info from (firstPoll) api: DSM method: getPollingData params: {} synology.0 2021-01-06 10:37:16.955 debug (10931) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}} synology.0 2021-01-06 10:37:16.955 debug (10931) ----------------------------------------------------------------------------------------------------- synology.0 2021-01-06 10:37:16.458 info (10931) starting. Version 0.1.18 in /opt/iobroker/node_modules/iobroker.synology, node: v10.20.1 -
@Alero sagte in synology adapter gelb:
code: 400
Was mich wundert ist der Code 400 , der sonst nicht dabei ist wenn die Administrators group nicht eingehalten wird.
hier noch die EInstellungen meiner syno
und der gruppe
Sowohl User als auch pw wurden in den Adapter kopiert um Schreibfehler zu vermeiden.Alero
-
hier noch die EInstellungen meiner syno
und der gruppe
Sowohl User als auch pw wurden in den Adapter kopiert um Schreibfehler zu vermeiden.Alero
@Alero
Bei den retuschierten Screenshots kann man nicht viel erkennen .Ich habe gerade im main.js vom Adapter geschaut , die Meldungen sind neu eingepflegt .
Ich würde dann auch auf die Meldung HTTP 400 Error (Bad Request) tippen das es dann so gemeint ist
-
@Alero
Bei den retuschierten Screenshots kann man nicht viel erkennen .Ich habe gerade im main.js vom Adapter geschaut , die Meldungen sind neu eingepflegt .
Ich würde dann auch auf die Meldung HTTP 400 Error (Bad Request) tippen das es dann so gemeint ist
@Glasfaser
die letzten Bilder sollten nur dokumentieren das der User "Hardware" heist und in der Administrators Gruppe vorhanden ist.
Dan ist es ein Zugrtiffsproblem?Alero
-
@haselchen
Hi,
scheinbar doch ein falscher user oder pw. Habe es mit dem Admin account meiner synology versucht. gleiches Ergebnis.To use the adapter, the user must be in the Administrators group! code: 400 message: No such account or incorrect passwordIch muss doch den User und das PW des Synology account mit adminrechten dort eintragen, oder?
AleroGelöscht
-
hier noch die EInstellungen meiner syno
und der gruppe
Sowohl User als auch pw wurden in den Adapter kopiert um Schreibfehler zu vermeiden.Alero
816
Online32.5k
Benutzer81.7k
Themen1.3m
Beiträge