State issues since dSS Update 1.19.3 - state wrong

[iobroker]

State issues since dSS Update 1.19.3 - state wrong

[Apollon77]

please provide a full debug log ... or in fact you can check in taht log and see what "changes" DS delivers". is there anything in the changelog that might have caused that ( I did not checked yet)

[tmycgn]

I had suspected that it might have something to do with the GE-KM300, since many changes have been made there. Therefore, I had already tested another scenario with different hardware (GE-KL200). Otherwise, I do not recognize anything conspicuous.

The debug results in an interesting case.... Here I just pressed one light switch via the app. If I understand the debug correctly, but the states of both lights are set to "on" correct?

Setup:

If the debug returns the values of the API, would this mean that the API has a bug in the new version?

[Apollon77]

The debug log means that there is a callScene event coming in for a zone and so the adapter sets the states to what he "guesses" and is pushing a "getOutputValue" to the queue to get the real real value.

To check this in detail I need a full debug log and time to dig through allll the details. If these two devices are not in the group for which the callscene command was sent then it is wrong that both are set ... but then data in the basic structuire wpuld be wrong because the adapter gets that on startup.

SO get a full debug log of start and then do such an action ... control via iobroker and also control outside and such. Then get logfile from disk (/opt/iobroker/log/...) and attach here or send to [email protected] via email with refernce to this issue

[tmycgn]

Thanks for your support, email with log and test details has been sent.

[tmycgn]

Short update after further testing by myself: The states are always set incorrectly in a room initially, but then will be correct automatically within approx. 2 minutes. Individual devices get corrected, not all at once. Maybe it helps.

[tmycgn]

Hi @Apollon77,

Since the Digitalstrom integration currently still does not work properly, I have tested further and found out the following. Maybe this leads to a solution of the problem. I have tested with the attached adapter configuration:

Data Polling Interval: 60 - Use Scene Preset Values: false - Request Device Output values actively: false

Result:

• If I press the virtual switch in the Digitalstrom app, the state* of the light is changed correctly with a slight time delay. The physical light is switched correctly.
• If I press the physical switch, the state* of the light is not changed at all. However, the physical light is switched correctly.

*digitalstrom.0.devices.302ed89f43f0000000002c8000000c7600.302ed89f43f00000000045400052ab2600.state

Debug:

Switching the light via the Digitalstrom app:

The status is then corrected with a slight time delay (2-10 seconds) when the following is executed with a time delay:

Switching the light via the physical switch:

Is there anything else I can do to support? Is the above configuration best-practise or should or should I change it for this issue?

Thanks!

[stale]

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.

[tmycgn]

The issue still exists. :/

[stale]

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.