Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time schedule initiated actions seem to be buggy #165

Open
Edgar-Z opened this issue May 25, 2021 · 0 comments
Open

Time schedule initiated actions seem to be buggy #165

Edgar-Z opened this issue May 25, 2021 · 0 comments

Comments

@Edgar-Z
Copy link

Edgar-Z commented May 25, 2021

Issue: Some via time schedule issued commands have no result. Just like no time schedule would exist. Devices are Fibaro Roller shutter 3 and Filio Pan08. Activation from mobile interface or PC via command always work, just time scheduled don’t.

Background: Have checked the log for two devices with the issue (some are working ok) and found the on Command is sent for Devices with an issue ( 38 and 39) as well as for the ok-working device 29 for the command class 38 (Switch Multilevel). However, the value for the non – working devices in the command class 38 is set to 13, which is the current level and not 99 as the requested “up” command. For the device 29 the value is set to 99 assumed to be correct as that device works properly. Have the impression, that switch Multilevel is sending wrong data in case the switch is at time of action not 0 or 99.
Log from 7:58 until 8:05 is available. Target action time for switch Multilevel on was 8:00. Both devices are controlled by one action with two devices.

Environment:
Raspberry Pi B+ with Raspbian 10 (Buster), Kernel 4.19.118+
Razberry 2
Zway Version 3.1.1
Devices with and without issue are Fibaro roller shutter 3 and FilioPan08.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant