text:
Need help with a lot of errors in log: warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions

So i'm trying to get some data from my ecoflow powerkit. And after much trial and error i thought i got it working. But still no data coming in so checked the log and saw this?! I dont know why? Maybe someone can help me with this?
2024-06-24 10:39:53.757 - info: ecoflow-mqtt.1 (1031) starting. Version 0.0.33 (non-npm: foxthefox/ioBroker.ecoflow-mqtt#e04cc52932a0f10e2f638c99201217e85008563b) in /opt/iobroker/node_modules/iobroker.ecoflow-mqtt, node: v18.20.3, js-controller: 5.0.19 2024-06-24 10:39:53.786 - info: ecoflow-mqtt.1 (1031) adapter entered ready 2024-06-24 10:39:53.787 - info: ecoflow-mqtt.1 (1031) your configration: 2024-06-24 10:39:53.788 - info: ecoflow-mqtt.1 (1031) powerstream -> [] 2024-06-24 10:39:53.789 - info: ecoflow-mqtt.1 (1031) powerstation -> [] 2024-06-24 10:39:53.790 - info: ecoflow-mqtt.1 (1031) smartplug -> [] 2024-06-24 10:39:53.790 - info: ecoflow-mqtt.1 (1031) wave -> [] 2024-06-24 10:39:53.791 - info: ecoflow-mqtt.1 (1031) glacier -> [] 2024-06-24 10:39:53.791 - info: ecoflow-mqtt.1 (1031) generator -> [] 2024-06-24 10:39:53.792 - info: ecoflow-mqtt.1 (1031) panel -> [] 2024-06-24 10:39:53.793 - info: ecoflow-mqtt.1 (1031) shelly -> [] 2024-06-24 10:39:53.794 - info: ecoflow-mqtt.1 (1031) powerkit -> [{"devName":"Camper","devId":"M109ZEB********","devType":"powerkitbp5000","haEnable":false,"pstationsSlave1":false,"pstationsSlave2":false}] 2024-06-24 10:39:53.809 - info: ecoflow-mqtt.1 (1031) start device state creation ->powerkit for Id M109ZEB******** 2024-06-24 10:39:54.520 - info: ecoflow-mqtt.1 (1031) pdevices states created for M109ZEB******** / powerkit / Camper 2024-06-24 10:39:54.544 - info: ecoflow-mqtt.1 (1031) [EF] going to connect to mqtt broker 2024-06-24 10:39:54.988 - info: ecoflow-mqtt.1 (1031) EF connected 2024-06-24 10:39:55.113 - info: ecoflow-mqtt.1 (1031) state ecoflow-mqtt.1.M109ZEB********.action.latestQuotas changed: true (ack = false) 2024-06-24 10:39:55.114 - info: ecoflow-mqtt.1 (1031) (ack=false) ->cmd : channel action state latestQuotas 2024-06-24 10:39:55.484 - info: ecoflow-mqtt.1 (1031) state ecoflow-mqtt.1.M109ZEB********.info.status changed: online (ack = true) 2024-06-24 10:39:55.487 - info: ecoflow-mqtt.1 (1031) [EF] M109ZEB******** is online with cloud 2024-06-24 10:39:56.513 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.524 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.535 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.547 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.558 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.571 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.582 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.594 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.604 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.617 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.628 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.640 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.650 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.661 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.672 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.682 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.694 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.706 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.721 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.734 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.746 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.764 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.775 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.790 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.800 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.813 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.865 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.878 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.891 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.901 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.911 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.922 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.935 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.945 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.957 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.973 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:56.986 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.001 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.010 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.022 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.078 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.092 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.108 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.121 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.139 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.150 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.165 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.175 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.189 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.203 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.257 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.270 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.279 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.294 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.345 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.356 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.368 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.378 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.392 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.401 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.413 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.423 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:57.434 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:58.867 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:58.876 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:58.885 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:58.894 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:58.947 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:58.955 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:58.964 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:58.974 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:58.985 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:58.995 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.006 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.015 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.024 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.032 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.043 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.053 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.065 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.074 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.084 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.093 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.102 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.111 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.125 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.176 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.184 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.233 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.248 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.262 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.273 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.285 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.296 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.311 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.322 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.333 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.343 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.356 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.366 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.376 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.385 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.396 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.405 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.415 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.424 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.435 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.444 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.455 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.464 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.538 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.549 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.560 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.569 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.580 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.589 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.599 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.608 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.658 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.692 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.729 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.738 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.788 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.802 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.813 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.825 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.835 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.887 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.901 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.913 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.966 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.985 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:39:59.998 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.018 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.029 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.038 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.046 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.056 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.107 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.117 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.128 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.136 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.145 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.155 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.165 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.173 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.181 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.190 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.199 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.210 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.218 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.230 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.240 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.251 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.261 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.272 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.324 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.335 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.344 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.397 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.406 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.415 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.426 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.439 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.448 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.496 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.508 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.561 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.573 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.586 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.637 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.656 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.669 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.700 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.756 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.776 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.795 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.808 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.859 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.875 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.889 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.903 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.916 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.931 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.942 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.955 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:00.966 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.093 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.103 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.110 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.121 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.131 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.140 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.148 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.158 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.167 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.178 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.186 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.195 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.204 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.214 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.224 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.233 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.243 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.255 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.307 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.318 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.368 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.379 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.390 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.398 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.408 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.421 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.430 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.440 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.451 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.461 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.512 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.521 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.537 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.548 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.560 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.572 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.622 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.632 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.643 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.696 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.711 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.722 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.741 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.757 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.770 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.777 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.827 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.840 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.852 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.866 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:01.876 - warn: ecoflow-mqtt.1 (1031) State "ecoflow-mqtt.1.M109ZEB********.bpundefined.moduleSn" has no existing object, this might lead to an error in future versions 2024-06-24 10:40:05.268 - info: host.IoBroker "system.adapter.ecoflow-mqtt.1" disabled 2024-06-24 10:40:05.269 - info: host.IoBroker stopInstance system.adapter.ecoflow-mqtt.1 (force=false, process=true) 2024-06-24 10:40:05.276 - info: ecoflow-mqtt.1 (1031) Got terminate signal TERMINATE_YOURSELF 2024-06-24 10:40:05.277 - info: host.IoBroker stopInstance system.adapter.ecoflow-mqtt.1 send kill signal 2024-06-24 10:40:05.280 - info: ecoflow-mqtt.1 (1031) cleaned everything up... 2024-06-24 10:40:05.281 - info: ecoflow-mqtt.1 (1031) terminating 2024-06-24 10:40:05.283 - info: ecoflow-mqtt.1 (1031) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-06-24 10:40:05.355 - info: ecoflow-mqtt.1 (1031) ecoflow connection closed 2024-06-24 10:40:05.785 - info: ecoflow-mqtt.1 (1031) terminating 2024-06-24 10:40:05.842 - info: host.IoBroker instance system.adapter.ecoflow-mqtt.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

The power kit implementation is relatively new, so there might not everything discovered and each feedback is appreciated.
For development I had only one testing telegram. So it would be great if you could activate the debug mode and activate the set/getMsg and updateMsg. Opening the App will also produce same telegrams additionally. If you could post the log, then I can check the missing properties causing the issue

I may have found the issue with the undefined batterypack number.
You can try the new version 0.0.37 from git or npm.
If there is a message in the log that the battery +serial# has no kitnum, then I need the incomming JSON file for comparison.

Did you have a chance to test the newer version?
In the meantime version 1.0.1 is available from git and npm.

I just found out i can enable debug log so did that and in the file is the result for you. Hope this helps.
Iobroker Log Jordy.txt

The log helps very much. So I can see that I am expecting another structure of the incomming message.
Having almost no live data is a problem, but hence you have managed to put the adapter into debug mode, you can help.
It would be great if you can go to the first page of the adapter settings and tick the msgSetGet, msgUpdate and msgCmd.
That brings some more informations related to the messages.
Hopefully there will be cyclically messages and also some message when you open the App.
It would be great i you could post the log afterwards.

If you need anything else just let me know. I'll try to give you whatever you need. You just sometimes need to tell me how to, because I don't know how iobroker works

OK, thanks for the help.
For the above mentioned things you need to go to instances and click on the ecoflow-mqtt adapter "wrench" symbol.

You can try to click on the button DEBUG JSON as well, but I guess it does not return too much.
Log can be downloaded here

only for completeness, another important tick:

I hope that enables you to work with iobroker and logging

I enabled everything you send me i hope this log file will help you.
iobroker ecoflow log2 Jordy.txt

Thank you very much, that helps a lot.
You did it right.
I will check what is the difference between my expectation and reality.

OK, I think now it should work.
Please do the following:

stop the adapter (I think it is not started, because of not working properly)
delete all objects (go to Objects, right click on the powerkit serial number and choose delete whole tree and confirm)
install the preliminary version (see the circles in below screenshot) go to Adapter -> enable expert mode (head symbol) -> go to custom installation (octacat symbol) -> choose custom (world symbol) -> type in the url ending with 1.0.4
start adapter

Oke i did what you send me and i still dont think it is working. Here is the new log file
iobroker ecoflow log3 Jordy.txt

Thanks for the log.
I think the version is not installed correctly.
2024-09-10 10:24:49.462 - info: host.IoBroker iobroker npm error The git reference could not be foundnpm error command git --no-replace-objects checkout 1.0.4npm error error: pathspec '1.0.4' did not match any file(s) known to git
I will make a merge to the main repository now(5min).
So it is not needed the tree version.
please go to the same window and use GitHub as source (instead custom) and type ecoflow in the search field and select it for installation.

I think it is working, or at least doing something. There is a thing in the log that makes me think it is nog fully working:  "not processed kitscc/kitscc state: seq value 43"  See the attached log file
iobroker ecoflow log4 Jordy.txt

Definitely it is working and the adapter receives data.
I think missing to get it connected and having data is accomplished.
Beside of the usual telegrams of the already defined values, there are some more related to the energy.
This kind of telegram is not evaluated right now, thats why there are some messages like
"..not processed bbcin/bbcin state: seq.."
"..not processed ichigh/ichigh state: wattItem.."
this is not to much to worry about.
"seq" is the sequence number of the telegram and "wattItem" is an array of hourly values.
bbcout": "watt":[21,21,20,16,17,20,21,21,20,19,18,20,16,16,17,26,16,0,0,0,0,0,0,0] is summed up to 325Wh.
The problem with hourly values is the timezone, so the first value might not be the first value in your timezone.
Thats finetuning by adding such datapoint definition. I will try to do it in the next update.
I had experience with other devices that the energy values are updated in the App after each hour, whereby the data in the adapter might be continuously updated. That could create a  difference.
What might be good to know, which datapoint you are referring to.
if bbcin and bbcout should have a difference, I can not judge. Here again, it might be good to indicate the name of datapoint what is of concern. Then it is also easy to search in the log for it and look what is incomming.
In order to reduce the logging, you might want to untick/deselect the msgStateCreation.

authors: Jordyleef foxthefox


text:
Update aws-java-sdk-dynamodb to 1.12.230

Updates com.amazonaws:aws-java-sdk-dynamodb from 1.11.1034 to 1.12.230.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" } ]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #296.

source: gharchive/pull-request

repo: fp-in-bo/api

license: MIT

license_type: permissive

license_source: github-api


text:
Re-enable hakyll with fixed http-types

http-types dependency is fixed in hakyll-4.7.5.0.

Looks good locally, you were probably faster than the package syncing.

authors: bergmark jaspervdj

repo: fpco/stackage

license: mit

license_source: bigquery


text:
Possible bug when editing user's username property

(found with @marcodeltufo)
To reproduce:

Go to localhost:5173/admin/users
Edit a user who already has a given value for username
Remove the value of username and click "save".
No error is observed
The user still has the same username.

Note that the request body of the PATCH API call is
{
"id":1,
"email":"admin@fractal.xy",
"is_active":true,
"is_superuser":true,
"is_verified":false,
"slurm_user":"test01",
"cache_dir":"/tmp \\asd"
}

but it does not include username.

Is something wrong here? Or did we exclude it on purpose due to some weird request-body-validation rule in fractal-server? (cc @ychiucco)

My suggestions:

It is a bit weird that this property is removed from the payload without any warning/error message, in fractal-web.
This username change looks like something that an admin should be able to do. If they can modify a user's username, then they should also be able to remove it. This likely requires a (minor) change in fractal-server. Note: I may be contradicting past me, with this remark.. if so, I'm sorry for that ;)

Currently we do not accept None as UserUpdate.username, but we can make it possible by changing this line
https://github.com/fractal-analytics-platform/fractal-server/blob/673e1c95b7de9b6f0a54f97eaf080ea80abdd569/fractal_server/app/schemas/user.py#L52C1-L52C8
into
_username = validator("username", allow_reuse=True)(valstr("username", accept_none=True))

I confirm that in the frontend we are removing the null values. If I allow them I receive:
String attribute 'username' cannot be None

Waiting for backend

https://github.com/fractal-analytics-platform/fractal-server/issues/1650

Closing, as the use of username should be superseded by the future task access-control configuration (based on either task-user relationship or task-user_group relationship, and not on string matching for specific columns).
Specific backend issue(s) TBD

source: gharchive/issue

authors: tcompa ychiucco zonia3000

repo: fractal-analytics-platform/fractal-web


text:
Used new endpoints for retrieving current user and list of users

Checklist before merging

[X] I added an appropriate entry to CHANGELOG.md

Closes #335

Thanks Sonia!
I used this a bit with fractal-server 1.4.0a8, and could not spot any unexpected behavior. I'm merging this one, and let's open issues if needed.


text:
galera::status must be conditionally included

Now galera::status in just included unconditionally in galera::validation so setting status_check to false doesn't prevent installing clustercheck script and xinetd service in case validation = true. I suggest to use for validation either status user/password if they are given and status_check enabled or to use root account as failback

@efoft Sorry for not being clear on this. We should keep all three class parameters as OPTIONALs, this includes $user and $password. Could you update your submission again? Thanks :)

definately, no problem! :)
@fraenki, Would you mind if I set them all to undef instead of $galera::status_* since they are optional? because if let's say we set status_check to false, galera::status won't be included and effectively this 3 params becomes undef anyway...

@efoft Merged, thanks!

authors: efoft fraenki

repo: fraenki/puppet-galera


text:
Can't change the page

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Framework7 Version: 2.0.7

Framework7-Vue Version: 2.0.7

Platform and Target: CORDOVA, IOS, ANDROID.

What you did
I am trying to change the displaying page after the successful login, but I can't change the actual page.
login.vue: https://gist.github.com/tomaszek92/d1fd8985491ba073c2f097db763137a5
routes.js: https://gist.github.com/tomaszek92/4759a4ea6fe6c8e06d68413cb587cb01
Expected Behavior
Change the displaying page.
Actual Behavior
Can't change the displaying page, throws an error:

Also, I tried with navigate method, but it does nothing (no error, no change the page).

It should be this.$f7Router.navigate('/home/');

And your login.vue must contain only f7-page element as a root element. No f7-view should be there


text:
Pushstate / Routing problem in v2

Hello @nolimits4web
I'm creating an app using framework7 v2. Previously i've worked with v1 and its good. v2 seems to be a major change from v1.
so i'm facing some problem in routing.. could u please help me..
this is the app.js from the kitchen sink template...
`var theme = 'auto';
if (document.location.search.indexOf('theme=') >= 0) {
theme = document.location.search.split('theme=')[1].split('&')[0];
}
// Init App
var app = new Framework7({
id: 'com.example.example',
root: '#app',
theme: theme,
routes: [
{
name: 'messages',
path: '/messages/',
templateUrl : './pages/messages.html',
on:{
pageInit: function (event, page) {
// alert('open');
console.log('page open');
},
pageBeforeRemove: function (event, page) {
// alert('removed');
console.log('page close');
},
},
view: {
xhrCache: false,
pushState: true,
uniqueHistory: true,
pushStateRoot: '/#/'
// pushSep
},
},
// Default route, match to all pages (e.g. 404 page)
{
path: '(.*)',
url: './pages/404.html',
},
],
vi: {
placementId: 'pltd4o7ibb9rc653x14',
},
touch: {
// Disable fast clicks
fastClicks: false,
}
});
`
in some page i've used this template..

Suparna Biswas

Where are you from?1 min ago

when i'm clicking on this link, the message page opens but the pushstate with the separator is not is not showing in the url causing the app to close when the back button is pressed.
I want the url to show like this..
abc.com/#/messages.html
so that by pressing the back button i can come to the home page..
Please help me.. Any help will be appreciated..

Do you want to ask a question? Are you looking for support? The Framework7 forum and Stack Overflow are the best places for getting support

Please, don't use GitHub issues for questions


text:
RNH ( - Seguridade Social ) for RV

if the person is adept of the RNH (20%) , and in the first year is Recibo Verde, theres no need for Seguridade social

That will be great if we can set a Residente Não Habitual (RNH) option, which limits the IRS to 20% and another option to set if it is his/her first year, so social security tax could be ignored

Sorry for the delay, but i haven't been working on this for a while. I'll upgrade the tool to use Vue3 and will add will add both of those options.

I've fixed the possibility to set  first year of activity, so that SS is 0. However, I can't seem to find reliable information on RNH - should the IRS be 20% on top of the taxable income or on top of the total gross income?

solved!

authors: franciscobmacedo jpmoura rubenmarcus

repo: franciscobmacedo/remotefreelancept


text:
🛑 PEDCO is down

In fb36d79, PEDCO (https://pedco.uncoma.edu.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PEDCO is back up in a1cdb93 after 7 minutes.


text:
Compatible Library Versions

The following document only outlines version compatibility for franka_ros.
I have updated my FER to 4.2.2 and wished to check what the recommended libfranka and associated submodule versions were for interfacing with the robot using franka_ros2.
Error Message
moveit_1  | [ros2_control_node-4] [FATAL] [1674486353.275366943] [FrankaHardwareInterface]: libfranka: Incompatible library version (server version: 5, library version: 4). Please check https://frankaemika.github.io for Panda system updates or use a different version of libfranka.

Environment
ROS Version: Foxy
libfranka:  0.9.0 - 0.10.0 (tested against multiple releases)
Note: I am recursively cloning libfranka so have also cloned associated libfranka-common repository.
Thanks in advance for any clarity you can provide. My workspace is built as a Docker image so I am happy to share further technical details where required.
@andrejpan does this fall under no ROS2 support as mentioned here?
FYI @Kzernobog.

libfranka 0.9.x will work for your robot. So installing 0.9.0 will work. I guess you still have a libfranka 0.8 somewhere on your system which shadows your 0.9 installation.
My random guess is that if you run:
sudo apt remove ros-foxy-libfranka
your problem will be solved. Feel free to reopen if this does not fix your issue.
In general all current libfranka versions should work with franka_ros2

Hi @marcbone,
I retested today with 0.9.0 again and I am still facing the above error. I also am building libfranka from source, I also ran sudo apt remove ros-foxy-libfranka as suggested above.
Here is a Dockerfile to recreate the issue:
ARG ROS_DISTRO=foxy
FROM ros:${ROS_DISTRO}-ros-base
MAINTAINER Peter David Fagan "peterdavidfagan@gmail.com"

# set default DDS to Cyclone
ENV RMW_IMPLEMENTATION rmw_cyclonedds_cpp

# install libfranka
RUN apt update && \
    apt install -y libpoco-dev libeigen3-dev && \
    git clone --branch 0.9.0 https://github.com/frankaemika/libfranka.git --recursive && \
    cd libfranka && \
    mkdir build && cd build && \
    cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=OFF  .. && \
    cmake --build . -j$(nproc) && \
    cpack -G DEB && \
    sudo dpkg -i libfranka-*.deb

# set up workspace
ENV ROS_UNDERLAY /root/panda_ws/install
WORKDIR $ROS_UNDERLAY/..
COPY . .

# import dependent libraries
RUN vcs import --skip-existing src < src/moveit2_tutorials/moveit2_tutorials.repos

# install ros dependencies
RUN . /opt/ros/${ROS_DISTRO}/setup.sh && \
    apt-get -q update && \
    apt-get install -y ros-${ROS_DISTRO}-rmw-cyclonedds-cpp && \
    apt-get install -y \
    ros-foxy-control-msgs \
    ros-foxy-xacro \
    ros-foxy-angles \
    ros-foxy-ros2-control \
    ros-foxy-realtime-tools \
    ros-foxy-control-toolbox \
    ros-foxy-moveit \
    ros-foxy-ros2-controllers \
    ros-foxy-joint-state-publisher \
    ros-foxy-joint-state-publisher-gui \
    ros-foxy-ament-cmake-clang-format && \
    rosdep update && \
    DEBIAN_FRONTEND=noninteractive \
    rosdep install --from-paths src --ignore-src -r -y --rosdistro ${ROS_DISTRO} --as-root=apt:false && \
    colcon build --mixin debug && \
    # Clear apt-cache to reduce image size
    rm -rf /var/lib/apt/lists/* && \
    # Update /ros_entrypoint.sh to source our new workspace
    sed -i "s#/opt/ros/\$ROS_DISTRO/setup.bash#$ROS_UNDERLAY/setup.sh#g" /ros_entrypoint.sh

I can assure you that you still have 0.8.0 somewhere on your system. Otherwise the error would not show that you have library version 4. You can verify this by putting
message("libfranka version: ${Franka_VERSION}")

into your CMakeLists.txt.

Thanks for getting back to me on this @marcbone. Ok I'll run the container again and look for a shared library file for 0.8.0.
From the above Dockerfile it seems surprising that this version of libfranka is getting installed on the system.

The following builds and runs as expected. As @marcbone outlined I was still installing 0.8.0 via rosdep.
ARG ROS_DISTRO=foxy
FROM ros:${ROS_DISTRO}-ros-base
MAINTAINER Peter David Fagan "peterdavidfagan@gmail.com"

# set default DDS to Cyclone
ENV RMW_IMPLEMENTATION rmw_cyclonedds_cpp

# install libfranka
RUN apt update && apt upgrade -y && \
    apt install -y  build-essential cmake git libpoco-dev libeigen3-dev && \
    git clone --recursive https://github.com/frankaemika/libfranka.git --branch 0.9.0 && \
    cd libfranka && \
    mkdir build && cd build && \
    cmake -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=OFF  .. && \
    cmake --build . -j$(nproc) && \
    cpack -G DEB && \
    sudo dpkg -i libfranka-*.deb

# set up workspace
ENV ROS_UNDERLAY /root/panda_ws/install
WORKDIR $ROS_UNDERLAY/..
COPY . .

# import dependent libraries
RUN vcs import --skip-existing src < src/moveit2_tutorials/moveit2_tutorials.repos

# install ros dependencies
RUN . /opt/ros/${ROS_DISTRO}/setup.sh && \
    apt-get -q update && \
    apt-get install -y ros-${ROS_DISTRO}-rmw-cyclonedds-cpp && \
    apt-get install -y \
    ros-foxy-control-msgs \
    ros-foxy-xacro \
    ros-foxy-angles \
    ros-foxy-ros2-control \
    ros-foxy-realtime-tools \
    ros-foxy-control-toolbox \
    ros-foxy-moveit \
    ros-foxy-ros2-controllers \
    ros-foxy-joint-state-publisher \
    ros-foxy-joint-state-publisher-gui \
    ros-foxy-ament-cmake-clang-format && \
    rosdep update && \
    DEBIAN_FRONTEND=noninteractive \
    rosdep install --from-paths src --ignore-src -r -y --skip-keys "libfranka" --rosdistro ${ROS_DISTRO} && \
    colcon build --mixin debug && \
    # Clear apt-cache to reduce image size
    rm -rf /var/lib/apt/lists/* && \
    # Update /ros_entrypoint.sh to source our new workspace
    sed -i "s#/opt/ros/\$ROS_DISTRO/setup.bash#$ROS_UNDERLAY/setup.sh#g" /ros_entrypoint.sh

authors: marcbone peterdavidfagan


text:
.htaccess file for internal redirect

In the root directory (where README.md and LICENSE is located) we should also put a .htaccess that does the Apache2 mod_rewrite stuff to redirect /oid/2.999 to plugins/..../rdap.php .
If possible, also include a file for nginx.

Suggestion: We should provide something like a .htaccess "generator" or plugin, which generates the .htaccess/nginx file dynamically, as this could vary from instance to instance.
The /oid/ Slug could be any slug wich is not a physical directory, or (like mentioned above) ist should be /(oid|weid|java)/ for example, regarding the installed Object Types.
???

This sounds interesting. Indeed, the problem is that the .htaccess would need to be renewed if new object type plugins are installed.
Another possible idea :
We could have a .htaccess which handles all HTTP requests and sends them to a resolve PHP script. This script decides what to do (and can be influenced by the page plugins).
But accessing static resources like PNG files or CSS files would be very hard with this approach, because we would "re-invent the wheel" (implement Content-Type, E-Tag, etc.)?!

Another possible idea : We could have a .htaccess which handles all HTTP requests and sends them to a resolve PHP script.
This script decides what to do (and can be influenced by the page plugins).
That sounds like a typical task for a "Router" Class/Library. There are existing classes out there, I suggest to choose one of the well known solutions. A Plugin could register its own "routes".

But accessing static resources like PNG files or CSS files would be very hard with this approach, because we would "re-invent > the wheel" (implement Content-Type, E-Tag, etc.)?!
In Apache you can skip existing files/dirs for mod_rewrite:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

Ngnix is made/optimized to serve the static files and pass dynamic script requests to Apache, thats how common configs works on my servers.

I totally forgot about -f and -d .
Ok, then I will do the following:

OIDplus will redirect those 404 to a handler script (the handler script must be able to know the file that was tried to access)
The handler script will handle this 404 . It will ask the plugins if they know what to do. If no plugin knows what to do, then a custom 404 page is shown.

Can you please provide me with the nginx config file that does the same as Apache's RewriteCond?
I will search for the MS IIS web.config possibility.

Hello Daniel,
I am not used to nginx, I must use google.
This is what I found for router file: https://stackoverflow.com/questions/26093270/nginx-how-to-let-rewrite-rules-ignore-files-or-folders
For !-f and !-d I found try_files, but never used it in production for my self: https://stackoverflow.com/questions/12206560/converting-apache-rewrite-rules-to-an-nginx-config-file
(The only server I am using without apache in production is my CDN Server. There is an Option in Plesk "Apache&Ngnix rules where you can set options like to serve static files by apache or ngnix, maybe I can find the generated config files, I will look...)

TODO @danielmarschall :

Implement "HTTP 404" handler in the OIDplus system and let plugins interchange with it
(for now just Apache2)
Make use of API in the RDAP plugin

In the next release of OIDplus, we will have a "handle404" API function.
This is what I would like to add to OIDplusPagePublicRdap:
	public function handle404($request) {
		$namespaces = array();
		foreach (OIDplus::getEnabledObjectTypes() as $ot) {
			$namespaces[] = $ot::ns();
		}

		foreach ($namespaces as $ns) {
			// Note: This only works if OIDplus is located at the domain root (because $request is relative to the domain)
			if (!preg_match('@^/'.preg_quote($ns,'@').'/(.+)$@', $request, $m)) return false;
			$oid = $m[1];
			$query = "$ns:$oid";
			$x = new OIDplusRDAP();
			list($out_content, $out_type) = $x->rdapQuery($query);
			if ($out_type) header('Content-Type:'.$out_type);
			echo $out_content;
			die(); // return true;
		}
	}

Is this OK?

Hi Daniel,
this is nice, but I would prefer to register a "regular" router rather than a 404 handler, as the 404 indicates not found.
You can register the routes by core and/or allow plugins to register their own routes.
There are many php routers available, e.g. the symfony router or google, this is one of my favorites: https://altorouter.com/
With a router you can provide "pretty urls", the 404 handler is more a "work around"?

Sorry, I don’t want to introduce more dependencies and frameworks into the product. Plus, I do not have any knowledge about this topic, so introducing such a framework into the product will most likely be counterproductive.

Also, I DO want to have RDAP only work on 404 requests. Otherwise, you can break your system, e.g. by installing a object type plugin with the namespace “img” or “plugins” or “setup”. Then, RDAP would be opened instead of the folders, and your system is damaged.

Implemented 404 handler for Microsoft IIS (SVN Rev 947)
Implemented 404 handler for NGINX (SVN Rev 948, tested with docker for Windows, container trafex/php-nginx)

authors: danielmarschall wehowski

repo: frdl/oidplus-frdlweb-rdap


text:
🛑 Senior School Website is down

In 6815a39, Senior School Website (https://www.cranleigh.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Senior School Website is back up in 55522c0.

repo: fredbradley/upptime


text:
🛑 Senior School Website is down

In 6de8ed9, Senior School Website (https://www.cranleigh.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Senior School Website is back up in 20ac58a.


text:
Merge refs/heads/1.8/main into alpha

Merge refs/heads/1.8/main into alpha

This PR has not been merged into alpha. Please fix the issues and re-open the PR.

repo: fredyk/westack-go


text:
Query latency as a metric

It would be very nice when it is possible to expose the latency of a certain (custom) query as a exposed metric.

Sounds like a really good idea. I'll implement it when I have the time, it will require a bit of (much needed) refactoring.

authors: free wavermartijn


text:
feat: add Modal Snapshot test

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Solving #309
Created a Snapshot testing for the modal component.
Co-authored-by: Ayomide Onifade onifadeayomide328@gmail.com
Co-authored-by: Quawiyyah Abdulhameed abdulhameedqo@gmail.com
Co-authored-by: Hamzat Oluwabori oluwaborihamzat@gmail.com

a new test was added, which is creating issues for all new PRs
https://github.com/freeCodeCamp/classroom/pull/396
by @lloydchang
https://github.com/freeCodeCamp/classroom/pull/397
by @theGaryLarson
https://github.com/freeCodeCamp/classroom/pull/398
by @Komal914
https://github.com/freeCodeCamp/classroom/pull/399
by @Chrisdbeloved1, @Ayomide6441, @Quawiyyah, @Code-Victor
all show the same failing test, dashtable_v2, from https://github.com/freeCodeCamp/classroom/pull/366#issuecomment-1652616915

Please contact @GuillermoFloresV if you have further questions about this. Thanks!

From https://codedayorg.slack.com/archives/C05ENB1VAKT/p1691946767049949

@Chrisdbeloved1, @Code-Victor, @Quawiyyah, @Ayomide6441
I believe you will need to fix the failing test by updating the Jest snapshot files to match — Otherwise, your pull request cannot be merged by the pull request reviewers.
https://github.com/freeCodeCamp/classroom/pull/399
Classroom ci / Build and test (16.14.2) (pull_request) Failing after 49s
https://github.com/freeCodeCamp/classroom/actions/runs/5842433790/job/15843553089?pr=399
ⓧ Run tests 4s

The error occured because UI was updated recently to support toast notifications. we are about to update the snapshot too.

authors: Chrisdbeloved1 Code-Victor lloydchang

repo: freeCodeCamp/classroom


text:
problem UI/UX Design

Challenge Build a Personal Portfolio Webpage has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.

@mkjn184 thanks for the issue. Can you elaborate on what you mean by "problem UI/UX design"? Do you mean the example portfolio page? Or do you mean the freeCodeCamp page itself? The example is simply an example to build your portfolio. Please give us more information on what your issue is.

repo: freeCodeCamp/freeCodeCamp


text:
learn to code javascript at freeCodeCamp logo      Community     Map     Donate      [ 345 ]   Basic Data Structures: Iterate Through All an Array's Items Using For Loops Test 2 displayed to user is incorrect

Challenge iterate-through-all-an-arrays-items-using-for-loops has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.

function filteredArray(arr, elem) {
    let newArr = [];
    let otherArr = [];
    // change code below this line
    for (let i = 0; i < arr.length; i++) {
        if (arr[i] === elem || arr[i].indexOf(elem) !== -1) {
            otherArr.push(arr[i]);

        } else {
            newArr.push(arr[i]);
        }
    }
    // change code above this line
    return newArr;
}

console.log(filteredArray([
    ["trumpets", 2],
    ["flutes", 4],
    ["saxophones"], 2
], 2));

Test two currently is stated as
filteredArray([ ["trumpets", 2], ["flutes", 4], ["saxophones"], 2], 2) should return [ ["flutes", 4] ]
The correct test should return
filteredArray([ ["trumpets", 2], ["flutes", 4], ["saxophones"], 2], 2) should return[ [ 'flutes', 4 ], [ 'saxophones' ] ]

Looks like the last item's bracket is in the wrong place -- should be ["saxophones", 2] ] to continue the pattern, which would make the expected result correct -- I'll do a PR


text:
Find Numbers with Regular Expressions

Challenge http://freecodecamp.com/challenges/waypoint-find-numbers-with-regular-expressions has an issue.
Two issues here:

Unnecessary use of the ignore case flag
Lack of clarity regarding the use of the + operator

As for the ignore case flag, numbers don't have case, so it's superfluous.
As with the previous waypoint (addressed in other issues), the + operator is misunderstood. However, it's probably correctly used here (more below), but it isn't clear to campers why, and the testString doesn't contain any numbers that require the + operator.
In the previous waypoint teaches campers that the + operator searches for multiple occurrences of the pattern. This is incorrect, and when they reach this waypoint, they will assume that the + is necessary to find both 3 and 4 in testString. But, as in the previous waypoint, the global modifier takes care of this.
In point of fact, the plus operator is necessary to select multi-digit numbers as a single number.
For example, if we change the string to the following
"There are 9 cats but 10 dogs."
The expressions /\d/g would select three numbers (9, 1, 0), while /\d+/g would correctly select two (9, 10).
This is because \d says "select digit characters" and the + operator says "any number of them," i.e., if a series of digit characters follow one another without any intervening characters of another type (letters, punctuation, spaces), then they count as one match to the pattern.
If this isn't what's intended, then the + operator should be removed entirely and the instructions clarified to say that campers should write an expression that selects each individual digit character.

Thanks @denmch for posting this!
Point 1 has been fixed already.
Point 2 is completely valid and the + operator needs to be explained (your words seem to do the trick)

Why its result is coming 2 ?

authors: Rahul22587 benschenker denmch


text:
Broken Test: Basic JavaScript Nesting For Loops

Describe your problem and how to reproduce it:
The Basic Javascript Nesting For Loops can pass all their criteria while doing it incorrectly.
https://learn.freecodecamp.org/javascript-algorithms-and-data-structures/basic-javascript/nesting-for-loops
You can solve the problem with the following fundamentally incorrect code:
function multiplyAll(arr) {
  var product = 1;

  for (var i = 0; undefined !== arr[i] && i < arr.length; i++) {
      for (var k = 0; undefined !== arr[i][k] && k <= arr[k].length; k++){
       product *= arr[i][k];
      }
  }
  // Only change code above this line
  return product;
}

I believe this is an easy mistake to make.
To fix, simply increase the amount of array items in the third test from:
multiplyAll([[5,1],[0.2, 4, 0.5],[3, 9]])
To:
multiplyAll([[5,1],[0.2, 4, 0.5, 5],[3, 9]])
Then only the correct nested loop will succeed the test.

This does not look like an easy mistake to make. I don't think anyone is going to be adding multiple conditions in a for loop test like this. There is often going to be a way to pass the tests with bad code, I don't think we can catch all of them.
Here's another function that will pass all the tests...
function multiplyAll(arr) {
  return arr[1][0] === 2 ? 6 : arr[1][0] === 3 ? 5040 : 54;
}

This does not look like an easy mistake to make. I don't think anyone is going to be adding multiple conditions in a for loop test like this. There is often going to be a way to pass the tests with bad code, I don't think we can catch all of them.
Here's another function that will pass all the tests...
function multiplyAll(arr) {
  return arr[1][0] === 2 ? 6 : arr[1][0] === 3 ? 5040 : 54;
}

Hmm... I see what you mean about bad code, but that's quite a specific way "around" the test, clearly manipulating the test values, and this test comes before the Ternary operator is taught.
Not understanding what should go in the second conditional, arr[k].length or arr.length or arr[i].length seems like an intuitive error that can happen, and we can proof against this error on the student's part by by increasing the size of the test array. Because the arrays are length 2, the student can incorrectly use arr[k].length, and switching to <= for the nested arr[k].length on the final test may give the student the impression they "succeeded," but instills an incorrect fundamental regarding array element counting.
I am reviewing the fundamentals and this was my experience until I did extra testing. I hope it can be improved by adding an additional element to the test array for any student who may experience the same.

Accidentally using k <= arr[k].length or something like it in the second loop is a mistake people would make, but that won't pass the tests. It only passes the tests because you added undefined !== arr[i][k] in the condition as well - which is something nobody is going to add.
Increasing the test array won't change the result for someone that uses k <= arr[k].length - it won't pass either way and it won't shed any light on why their code doesn't work.
I dunno - maybe I'm misunderstanding what you are getting at.

This does not look like an easy mistake to make. I don't think anyone is going to be adding multiple conditions in a for loop test like this. There is often going to be a way to pass the tests with bad code, I don't think we can catch all of them.
Here's another function that will pass all the tests...
function multiplyAll(arr) {
  return arr[1][0] === 2 ? 6 : arr[1][0] === 3 ? 5040 : 54;
}

Hmm... I see what you mean about bad code, but that's quite a specific way "around" the test, clearly manipulating the test values, and this test comes before the Ternary operator is taught.
Not understanding what should go in the second conditional, arr[k].length or arr.length or arr[i].length seems like an intuitive error that can happen, and we can proof against this error on the student's part by increasing the size of the test array. Because the arrays are length 2, the student can incorrectly use arr[k].length, and switching to <= for the nested arr[k].length on the final test may give the student the impression they "succeeded," but instills an incorrect fundamental regarding array element counting.
I am reviewing the basics before moving onto ES6, and this was my experience until I did extra testing. I hope it can be improved by adding an additional element to the test array for any student who may experience the same.

What's about adding hidden test case?

I don't think there's an issue here. Does anyone else want to share their opinion on this?

This code behaves as it should, it's just weird.  I wouldn't recommend writing code like that, but checking to see if an array element is undefined or checking to see if you've gone past the end of an array amount to the same thing.  Assuming, of course, that your arrays don't have undefined as elements, which is a perfectly reasonable assumption here.

authors: ElPomodorro JohnBaumlin moT01 ojeytonwilliams


text:
Answer for "React: Create a Controlled Input" outputs desired outcome but without "state." in input

Describe your problem and how to reproduce it:
An answer for "React: Create a Controlled Input" outputs desired outcome but does not pass the test
The answer:
class ControlledInput extends React.Component {
  constructor(props) {
    super(props);
    this.state = {
      input: ''
    };
    this.handleChange = this.handleChange.bind(this);
  }

  handleChange(event) {
    this.setState({
      input: event.target.value
    })
  }

  render() {
    return (

        < input value={this.input} onChange={this.handleChange} />

Controlled Input:

{this.state.input}

    );
  }
};

Error message:
// running tests
Typing in the input element should update the state and the value of the input, and the p element should render this state as you type.
// tests completed

Add a Link to the page with the problem:
https://www.freecodecamp.org/learn/front-end-libraries/react/create-a-controlled-input
Tell us about your browser and operating system:

Browser Name: Firefox
Browser Version: 75.0 (64-bit)
Operating System: macOS Mojave Version 10.14.6 (18G4032)

If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):

Hello there.
For future issues like this, please open a topic on the forum. The reason for this is to iron out issues that are user-based, and not an issue with the source code.
In your example, you are not passing the test, because you are not:

update...the value of the input

Have a look at this line:
< input value={this.input} onChange={this.handleChange} />

There is a mistake.
Thank you, for helping us keep the tests valid. I am closing this issue.

Thank you, @Sky020.


text:
Preview Saga is called twice when loading the editor

While using the editor in any of the step challenge, you will have different layout mobile and desktop, we are using different components for these layouts.
Pros:

the editor isn't supported for mobile, so we can have somewhat of a support for it.
the styling and layout will become easier.

Cons:

loading the same Redux actions twice. (adding console log, to preview sage here will show twice)
losing the state when camper change the layout manually, it act similar to refreshing the page (lose focus, maybe reimport components, and such)

I think it's better overall if that section is deleted.

I am not sure what you mean by deleting the mobile layout. It does seem pretty useful to me.
Do you mean that both the mobile layout and the web layout are loaded depending on the screen size while the user is already present on the site?

the preview saga is called twice whenever the preview is mounted.

Are you sure this is not just because you are in development mode? Does this happen for a production build?

I don't know how to test it in production, redux dev tools doesn't show anything on
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-basic-css-by-building-a-cafe-menu/step-4

@Sboonny one option is to build the client locally. That should enable redux dev tools. Just to be on the safe side, I'd add the console log you suggested, too.

It has the console log run three time in built environment.
Thanks to Oliver help, I was able to run it by these commands
pnpm run build
cd client
pnpm dlx serve -p 8000 public

I am not sure what you mean by deleting the mobile layout. It does seem pretty useful to me.
Do you mean that both the mobile layout and the web layout are loaded depending on the screen size while the user is already present on the site?

just seen will look into.sje.l

authors: Sboonny Sembauke ShaunSHamilton ojeytonwilliams smithbinky


text:
Acrescentando informação sobre justify-content

explicando mais detalhado

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@rafaellfaria Please make the changes suggested by @CleoAguiar above.
Thank you.

authors: RandellDawson rafaellfaria


text:
Added space

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality standards we encourage. This applies mainly to beginners.

PRs that are automated e.g. scripted opening PRs to remove white space / optimize images.
PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
PRs that are regarded by a project maintainer as a hindrance vs. helping.
Something that's clearly an attempt to simply +1 your PR count for October.

Learn more at https://hacktoberfest.digitalocean.com/details

@ArielLeslie There PR did seem valid to me since it is improving the user readability (even by a fraction through).

I didn't mark it as invalid, but do consider it to be pretty low quality.

@ArielLeslie I agree about the quality.


text:
Added Why MAMP

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Added Why MAMP is used


text:
fix(ui): update a link for new campers

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #47206

Update "start at the beginning" link so it can navigate new campers to the first challenge of new Responsive Web Design Certification in the audited language environments.
The code have been tested in all language environment via setting CLIENT_LOCALE and CURRICULUM_LOCAL in .env and previewed locally.
Affected page:
https://www.freecodecamp.org/learn/

@moT01 I agree. So I comitted the modified query and code which have again been tested and previewed in all language environment locally.  Thank you.

Thanks @moT01. It's owe to your appropriate advice.


text:
Update campsitesfinal.json

Pre-Submission Checklist

[X] Your pull request targets the master branch of freeCodeCamp/study-group-directory.
[X] You have only one commit (if not, squash them into one commit).

Type of Change

[ ] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[X] Update or Correct an existing group entry
[ ] Add a new group entry

Checklist:

[ ] Tested changes locally.
[ ] Automated build tests (Travis and Netlify) pass
[ ] Addressed currently open issue (replace XXXXX with an issue number in next line)

Closes #XXXXX
Description

Local group of Brescia, Italy.
Was removed because doesn't exist anymore.

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝

authors: dshortway thecodingaviator

repo: freeCodeCamp/study-group-directory


text:
Add shortcut to edit private.el

Creates a shortcut to edit user settings using recommended private.el file

I wonder, should we just make C-x c open the private config instead? Since the init.el is supposed to be unchangeable anyway, maybe we shouldn't have an easy way to access it at all?
Or, maybe this way: C-x c to open private.el, C-x C to open init.el. Private is primary, init is secondary and requires a weirder (intentionally) keystroke.
What do you think?

Had a similar thought last night, considered C-x C for private config. I think your idea is better.
New commit updates per your suggestion.

Awesome, thanks!

authors: bwl freetonik

repo: freetonik/castlemacs