readTags returns 500 #20
Comments
|
I tried it with my WP and got a proper response. If a tag is not support the tag result is Is this error persisting or only occuring once in a while? Please login to your WP website and after that visit this link: |
|
This call works fine. it's ends with #A16 S_OK |
|
it seems to be a missing/invalid login |
|
Please wait a few minutes after closing the website. There can only be a
certain amount of active connections. However, the adapter should be able
to handle this case and skips requesting for a while. Are there any adapter
logs?
Am Fr., 5. Apr. 2024 um 12:33 Uhr schrieb gemuesepudding <
***@***.***>:
… it seems to be a missing/invalid login
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRTWSYC6SL6URINOT5IJZTY3Z4YLAVCNFSM6AAAAABFYYSZFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZZGQ2TCMRZGY>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
|
all i have is |
|
ok, it was only warn level. |
|
But are you getting updated values sometimes? I noticed that the api is not
very stable and I also sometimes get those messages, especially because the
wifi signal is not that good in the basement. As long as you are only
seeing this message sporadically but getting updated values most of the
time I think this message can be ignored.
Am Mi., 10. Apr. 2024 um 11:46 Uhr schrieb gemuesepudding <
***@***.***>:
… ok, it was only warn level.
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRTWS73W5VEBARGGBFN643Y4UDAXAVCNFSM6AAAAABFYYSZFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBXGA2TENRRGE>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
|
It's updateds after restart. But not after that |
restarted at 12:33 with some errors
and
timestamp keeps the same
|
|
Okay, interesting... Since you are successfully logged in, the WP should be reachable and the credentials are also correct. Let me think about what could go wrong. |
|
looks like a timeout of the login to me |
|
No, if there is a login timeout, there is a different error and this is handled by renewing the login.
|
|
all i get is waterkotte-easycon.0 waterkotte-easycon.0 waterkotte-easycon.0 waterkotte-easycon.0 waterkotte-easycon.0 waterkotte-easycon.0 waterkotte-easycon.0 waterkotte-easycon.0 waterkotte-easycon.0 waterkotte-easycon.0 waterkotte-easycon.0 |
|
I put the loglevel to silly |
|
But there is no login message and so on. Please restart the adapter and
post the log.
Am Fr., 12. Apr. 2024 um 16:19 Uhr schrieb gemuesepudding <
***@***.***>:
… I put the loglevel to silly
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRTWS3NBICX2YFKXOVV3PDY47UQJAVCNFSM6AAAAABFYYSZFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJRHA2TINJQGY>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
|
only the first one. waterkotte-easycon.0 waterkotte-easycon.0 waterkotte-easycon.0 waterkotte-easycon.0 waterkotte-easycon.0 waterkotte-easycon.0 waterkotte-easycon.0 |
|
Okay, that helps a lot. I will look into it.
Am Fr., 12. Apr. 2024 um 16:39 Uhr schrieb gemuesepudding <
***@***.***>:
… only the first one.
waterkotte-easycon.0
2024-04-12 16:34:59.726 warn Request to '
http://192.168.120.9/cgi/readTags?n=75&t1=I263&t2=A32&t3=I30&t4=A31&t5=A61&t6=A90&t7=A93&t8=A94&t9=A91&t10=A92&t11=A96&t12=A98&t13=A100&t14=A101&t15=A102&t16=A103&t17=A99&t18=A30&t19=I137&t20=D24&t21=A25&t22=A26&t23=A28&t24=A27&t25=A29&t26=A1&t27=A2&t28=A3&t29=A4&t30=A5&t31=A6&t32=A7&t33=A8&t34=A10&t35=A699&t36=A700&t37=A701&t38=A702&t39=A12&t40=I2017&t41=I2018&t42=I2019&t43=I2020&t44=I2021&t45=I2022&t46=I2025&t47=I2024&t48=I2023&t49=I2032&t50=I2033&t51=I2034&t52=I2039&t53=A13&t54=A14&t55=A15&t56=A17&t57=A18&t58=A19&t59=A20&t60=A21&t61=A16&t62=A1022&t63=A1023&t64=D581&t65=D701&t66=I5&t67=I6&t68=I7&t69=I8&t70=I9&t71=D1010&t72=D815&t73=D816&t74=D817&t75=D818'
failed: Request failed with status code 500
waterkotte-easycon.0
2024-04-12 16:29:58.636 info Successfully logged in
waterkotte-easycon.0
2024-04-12 16:29:57.738 warn Unable to get parameter 'A1023'. Received
'E_INACTIVETAG' instead.
waterkotte-easycon.0
2024-04-12 16:29:57.737 warn Unable to get parameter 'A1022'. Received
'E_INACTIVETAG' instead.
waterkotte-easycon.0
2024-04-12 16:29:54.976 debug Active service:
{"de":"Heizbetrieb","en":"Heating","fr":"Chauffage"}
waterkotte-easycon.0
2024-04-12 16:29:54.941 debug Successfully (re-)logged in
waterkotte-easycon.0
2024-04-12 16:29:54.799 info starting. Version 0.0.2 (non-npm:
theknut/ioBroker.waterkotte-easycon#cf4498c03fc38696925618504d968242412dc693)
in /opt/iobroker/node_modules/iobroker.waterkotte-easycon, node: v18.17.1,
js-controller: 5.0.19
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRTWS3UQ2MCESWPWMDXLATY47WZXAVCNFSM6AAAAABFYYSZFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJRHA4DSMRQG4>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
|
some updates? After i restarted the adaptor today, is got Unable to get parameter 'A1023'. Received 'E_INACTIVETAG' instead. But both are queried |
I installed v0.0.2 and configured the adapter to use my Waterkotte EcoTouch DS5014.5 . But readTags fails
/cgi/readTags?n=75&t1=I263&t2=A32&t3=I30&t4=A31&t5=A61&t6=A90&t7=A93&t8=A94&t9=A91&t10=A92&t11=A96&t12=A98&t13=A100&t14=A101&t15=A102&t16=A103&t17=A99&t18=A30&t19=I137&t20=D24&t21=A25&t22=A26&t23=A28&t24=A27&t25=A29&t26=A1&t27=A2&t28=A3&t29=A4&t30=A5&t31=A6&t32=A7&t33=A8&t34=A10&t35=A699&t36=A700&t37=A701&t38=A702&t39=A12&t40=I2017&t41=I2018&t42=I2019&t43=I2020&t44=I2021&t45=I2022&t46=I2025&t47=I2024&t48=I2023&t49=I2032&t50=I2033&t51=I2034&t52=I2039&t53=A13&t54=A14&t55=A15&t56=A17&t57=A18&t58=A19&t59=A20&t60=A21&t61=A16&t62=A1022&t63=A1023&t64=D581&t65=D701&t66=I5&t67=I6&t68=I7&t69=I8&t70=I9&t71=D1010&t72=D815&t73=D816&t74=D817&t75=D818' failed: Request failed with status code 500
If i remember correct, this happens if an TAG isn't supported
The text was updated successfully, but these errors were encountered: