Closed smartboart closed 9 months ago
Seems like the communication was completely out-of-sync - the details of the "Unknown tag" messages do not make any sense to me, the tagCodes/typeCodes are random and len is larger than usually expected. The only "pattern" I can see is that there are always six equal events in a sequence.
I think restarting all components could help. Otherwise, if this is reproducible, I would need documentation about the changes by E3/DC (which is not availyble, I'm afraid).
Das sind meine Fehler seit heute morgen. Es gab im PV Modul eine neue Version, so wie ich das gesehen habe
e3dc-rscp.0 | 2024-01-31 22:05:17.192 | warn | TAG_INFO_REQ_GET_FS_USAGE has no assigned polling interval - assuming 'M' - please check io-package.json |
---|---|---|---|
e3dc-rscp.0 | 2024-01-31 22:05:17.192 | warn | TAG_INFO_REQ_GET_FACILITY has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.192 | warn | TAG_INFO_REQ_GUI_TARGET has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.192 | warn | TAG_INFO_REQ_SW_RELEASE has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.192 | warn | TAG_INFO_REQ_TIME_ZONE has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.192 | warn | TAG_INFO_REQ_UTC_TIME has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.192 | warn | TAG_INFO_REQ_TIME has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.192 | warn | TAG_INFO_REQ_DHCP_STATUS has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.192 | warn | TAG_INFO_REQ_DNS has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.192 | warn | TAG_INFO_REQ_GATEWAY has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.192 | warn | TAG_INFO_REQ_MAC_ADDRESS has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.192 | warn | TAG_INFO_REQ_SUBNET_MASK has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.191 | warn | TAG_INFO_REQ_IP_ADDRESS has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.191 | warn | TAG_INFO_REQ_A35_SERIAL_NUMBER has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.191 | warn | TAG_INFO_REQ_MODULES_SW_VERSIONS has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.191 | warn | TAG_INFO_REQ_PRODUCTION_DATE has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.191 | warn | TAG_INFO_REQ_SERIAL_NUMBER has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.190 | warn | TAG_EP_REQ_EP_RESERVE has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.189 | warn | TAG_EMS_REQ_EMERGENCY_POWER_TEST_STATUS has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.189 | warn | TAG_EMS_REQ_WB_ENFORCE_POWER_ASSIGNMENT has no assigned polling interval - assuming 'M' - please check io-package.json |
e3dc-rscp.0 | 2024-01-31 22:05:17.189 | warn | TAG_EMS_REQ_WB_DISCHARGE_BAT_UNTIL has no assigned polling interval - assuming 'M' - please check io-package.json |
@Jockelflo, dein Log sieht nach einem ganz anderen Thema aus, siehe Issues #156 , #191
Seems like the communication was completely out-of-sync - the details of the "Unknown tag" messages do not make any sense to me, the tagCodes/typeCodes are random and len is larger than usually expected. The only "pattern" I can see is that there are always six equal events in a sequence.
I think restarting all components could help. Otherwise, if this is reproducible, I would need documentation about the changes by E3/DC (which is not availyble, I'm afraid).
Hi, thanks for feedback... I have restarted my comple iobroker system.. This solved the issue...crazy.. because i had no other issues wit the broker... But it helped... If nobody else has this issue and you see no need to work at this , the issue can be closed... Thanks ...
@smartboart, many thanks for your input. I will keep this in mind and if such trouble is reported again, then I have to think about some logic like "if the adapter throws more than x unknown-tag warnings per minute, then reset communication".