Jey-Cee / ioBroker.upnp

Serves for communication and interaction with all upnp-capable devices.
MIT License
10 stars 8 forks source link

[Bug]: After Update JS-Controller to 3.3.22: LogFile "has to be Type "XXX" but received type "YYY". #99

Closed Hini2001 closed 2 years ago

Hini2001 commented 2 years ago

Contact Details

xxx

What happened?

Good morning and happy new year. Since the update to JS-Controller 3.3.22 I have a problem with the UPNP adapter among others:

The Logfile is FULL and spammed with the messages that the received type of the DataPoint (DP) ist not the one it has to be. Like, f.e.: `

upnp.0 | 2022-01-02 10:55:10.852 | info | State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.ByteSendRate" has to be type "number" but received type "string" -- | -- | -- | -- upnp.0 | 2022-01-02 10:55:10.790 | info | State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.ByteReceiveRate" has to be type "number" but received type "string" upnp.0 | 2022-01-02 10:55:10.739 | info | State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.PacketSendRate" has to be type "number" but received type "string" upnp.0 | 2022-01-02 10:55:10.684 | info | State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.PacketReceiveRate" has to be type "number" but received type "string" upnp.0 | 2022-01-02 10:55:10.620 | info | State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.TotalBytesSent" has to be type "number" but received type "string" upnp.0 | 2022-01-02 10:55:10.560 | info | State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.TotalBytesReceived" has to be type "number" but received type "string" upnp.0 | 2022-01-02 10:55:10.509 | info | State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.AutoDisconnectTime" has to be type "number" but received type "string" upnp.0 | 2022-01-02 10:55:10.451 | info | State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.IdleDisconnectTime" has to be type "number" but received type "string" upnp.0 | 2022-01-02 10:55:10.359 | info | State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.UpnpControlEnabled" has to be type "boolean" but received type "string" upnp.0 | 2022-01-02 10:55:10.307 | info | State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.RoutedBridgedModeBoth" has to be type "number" but received type "string"

`

Stopping the instance. Deleting the DPs and restarting, as well as re-creating the DPs did not fix the problem. The DP types actually match what is required. So I don't know what to do anymore. I've read here another Issue with a similar problem (#88 ), but this issue was AUTOMATICALLY closed, because of no further activies.

Hope you can help me (and maybe others).

Greetings

Adapter Version

1.0.19

JS-Controller Version

3.3.22

Node JS Version

12.22.1

NPM Version

6.14.12

Operating System

Debian

Relevant log output

upnp.0
2022-01-02 10:55:10.852 info    State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.ByteSendRate" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.790 info    State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.ByteReceiveRate" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.739 info    State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.PacketSendRate" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.684 info    State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.PacketReceiveRate" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.620 info    State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.TotalBytesSent" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.560 info    State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.TotalBytesReceived" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.509 info    State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.AutoDisconnectTime" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.451 info    State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.IdleDisconnectTime" has to be type "number" but received type "string"

upnp.0
2022-01-02 10:55:10.359 info    State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.UpnpControlEnabled" has to be type "boolean" but received type "string"

upnp.0
2022-01-02 10:55:10.307 info    State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6490_Cable_(kdg).WANDevice.WANCommonInterfaceConfig.RoutedBridgedModeBoth" has to be type "number" but received type "string"

Anything else?

No response

Hini2001 commented 2 years ago

Good Evening, too bad none replied, but one for others facing this problem, an update to version 1.0.20 solved the problem and everything is running normally and as it should again. Happy New Year to all SmartHome - Junkies out there! :-)

This Bug Report could be closed then.