search

Jey-Cee / ioBroker.upnp

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

[Bug]: Infos after js-controller 3.3.15 #88

Closed mcuiobroker closed 2 years ago

mcuiobroker commented 2 years ago

Contact Details

mcuiobroker@gmail.com

What happened?

A bug happened! Everytime there are Log entries "you should change the type"-> has to be type "number" but received type "string"

Adapter Version

1.0.19

JS-Controller Version

3.3.15

Node JS Version

12.22.6

NPM Version

6.14.15

Operating System

Debian

Relevant log output

`
<html>
<body>
<!--StartFragment-->

upnp.0 | 2021-08-31 21:40:00.781 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.ByteSendRate" has to be type "number" but received type "string"
-- | -- | -- | --
upnp.0 | 2021-08-31 21:40:00.763 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.ByteReceiveRate" has to be type "number" but received type "string"
upnp.0 | 2021-08-31 21:40:00.708 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.PacketSendRate" has to be type "number" but received type "string"
upnp.0 | 2021-08-31 21:40:00.690 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.PacketReceiveRate" has to be type "number" but received type "string"
upnp.0 | 2021-08-31 21:40:00.673 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.TotalBytesSent" has to be type "number" but received type "string"
upnp.0 | 2021-08-31 21:40:00.620 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.TotalBytesReceived" has to be type "number" but received type "string"
upnp.0 | 2021-08-31 21:40:00.603 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.AutoDisconnectTime" has to be type "number" but received type "string"
upnp.0 | 2021-08-31 21:40:00.545 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.IdleDisconnectTime" has to be type "number" but received type "string"
upnp.0 | 2021-08-31 21:40:00.400 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.UpnpControlEnabled" has to be type "boolean" but received type "string"
upnp.0 | 2021-08-31 21:40:00.329 | info | (7119) State value to set for "upnp.0.WANDevice_-_FRITZ!Box_6591_Cable.WANDevice.WANCommonInterfaceConfig.RoutedBridgedModeBoth" has to be type "number" but received type "string"

<!--EndFragment-->
</body>
</html>`

Anything else?

No response

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

stale[bot] commented 2 years ago

This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions. Dieses Problem wurde aufgrund von Inaktivität automatisch geschlossen. Bitte öffnet ein neues Issue, falls dies noch relevant ist und stellt sicher das alle relevanten Details, Logs und Reproduktionsschritte enthalten sind. Vielen Dank für Eure Unterstützung.