iobroker-community-adapters / ioBroker.shelly

Integrate your Shelly devices into ioBroker via MQTT or CoIoT
Other
168 stars 68 forks source link

Shelly 2.5: Roller-Switch: Datapoints OPEN/CLOSE/PAUSE are not updated #770

Closed 2Moon4 closed 1 year ago

2Moon4 commented 1 year ago

I'm sure that

Shelly device

Shelly 2.5 (20221027-092056/v1.12.1-ga9117d3)

Protocol (CoAP / MQTT)

MQTT

The problem

Today I updated to version 6.3.1. After that (at least) the OPEN/CLOSE/PAUSE data points were no longer updated. Each of these actions was working by the Shelly 2.5 device. I was able to open and close the blind via button-click of the OPEN/CLOSE/PAUSE object in the Shelly object tree within the iobroker-objects-website. But - no update (true/false) was made in the corresponding object. All these objects stays on "true" - with no changings. Also the time of the last change/update has not been updated within this object. I think this is a bug because a button action on the OPEN/CLOSE/PAUSE object of the (Shelly) adapter should also update it (change-time, last-update-time, accknowledge) - if the device is working by clicking these object-buttons.

So i went back to version 6.0.0. - this version works fine (again) without changing anything!

Version of nodejs

16.16.0

Version of ioBroker js-controller

4.0.23

Version of Adapter

6.3.1

Operating system running ioBroker

Linux raspberrypi 5.10.103-v7l+ (Raspbian GNU/Linux 10 (buster))

Checklist of files to include below

Additional information & file uploads

iobroker.current.log

klein0r commented 1 year ago

Today I updated to version 6.3.1. After that (at least) the OPEN/CLOSE/PAUSE data points were no longer updated. Each of these actions was working by the Shelly 2.5 device. I was able to open and close the blind via button-click of the OPEN/CLOSE/PAUSE object in the Shelly object tree within the iobroker-objects-website.

Those states are write only. Why should they change their state?

2Moon4 commented 1 year ago

Hello,

Yes they are write only for users.... But not for the device, or? If the device changes it's state ... the objects should be updated. This does not work, too. And if I click the button, the device worked.... so it should update it's state. But nothing happens. The state stays at its old value.

One example: I click at the button OPEN. The device opens the blind. The state of value OPEN should be true..... The state of value CLOSE should be false. Is the blind finish opening, all states should go to false, except PAUSE. nothing of this state changes happens in version 6.3.1.

Greetings

Matthias Kleine @.***> schrieb am Di., 7. Feb. 2023, 06:56:

Today I updated to version 6.3.1. After that (at least) the OPEN/CLOSE/PAUSE data points were no longer updated. Each of these actions was working by the Shelly 2.5 device. I was able to open and close the blind via button-click of the OPEN/CLOSE/PAUSE object in the Shelly object tree within the iobroker-objects-website.

Those states are write only. Why should they change their state?

— Reply to this email directly, view it on GitHub https://github.com/iobroker-community-adapters/ioBroker.shelly/issues/770#issuecomment-1420239107, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYVFQJU2GSZBQIIN5HQHSX3WWHPW7ANCNFSM6AAAAAAUTIA7SA . You are receiving this because you authored the thread.Message ID: @.*** com>

loemic87 commented 1 year ago

I am also running v. 6.3.1 with 2 instances, because i am using gen1 and gen2 devices. My problems are the same.

I am not able to control my shelly2.5 shutters with iobroker. Controlling via Alexa or shelly app or shelly webinterface works.

If i should provide a logfile please tell me what loglevel (silly, debug, info...) and what information i have to provide.

system: raspberrry pi 4, raspbian bullseye js-controller: 4.0.24 node: 16.19.0

stale[bot] commented 1 year ago

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

stale[bot] commented 1 year ago

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