Blynk fix for partitions 2-8, Push notifications for power/battery/alarm#198
Merged
taligentx merged 5 commits intotaligentx:developfrom Feb 4, 2021
kricon:develop
Merged
Blynk fix for partitions 2-8, Push notifications for power/battery/alarm#198taligentx merged 5 commits intotaligentx:developfrom kricon:develop
taligentx merged 5 commits intotaligentx:developfrom
kricon:develop
Conversation
Blynk examples now call pauseZones on partitions other than 1 #190 Memory/Programming leds now also work on partition 2, doesn't work for partitions 3-8 for reason taligentx stated in #182 Viewing event buffer now also works fine on partitions 2-8. Added push notification for battery/power trouble/restore and partition in alarm (partition you've selected in blynk project). Note that you must add widget:notification in your blynk project and enable notifications. Remember that it sends notification only when selected partition goes in alarm and not the others. Works when phone is locked and when Blynk app isn't open.
…ifferent partition enter * key #198
…larm If power/battery trouble/restore occur, it will be pushed as notification and "Trouble status on" notification wont be pushed. Obviously, if power/battery trouble is active and new trouble occurs such as zone sensor low battery, "Trouble status on" won't be pushed as trouble status was already on.
Owner
|
Thank you! It's great to have the better multiple partition support and notifications. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Blynk examples now call pauseZones on partitions other than 1 #190. Viewing event buffer now also works fine on partitions 2-8.
Memory/Programming leds now also work on partition 2, doesn't work for partitions 3-8 for reason taligentx stated in #182
Added push notification for battery/power trouble/restore and partition in alarm (partition you've selected in blynk project) EDIT: committed sending push notification when alarm occurs on all partitions (with partition number on which alarm occured), not just the one selected in Blynk app.
Note that you must add widget:notification in your blynk project and enable notifications. Works fine when phone is locked and Blynk app isn't open.
It's possible to make tabs in Blynk project and for example have one tab only for controlling one partition, second tab for second partition, third tab just for controlling PGM's and viewing event buffer, and fourth for Blynk serial terminal where it can log latest events for example arming/disarming/alarm/zone low batteries and such. But that requires a lot of code addition, as printPanelStatus now only supports viewing past events from DSC buffer and displaying them on virtual LCD. Also, zone low battery push notification would be nice addition aswell, I'll see if I can implement it.
EDIT: Just noticed a bug while testing: if you press ( * ) from real keypad which is set on partition different than one on Blynk virtual keypad, it calls pauseZones but never call resetZones (until status for that partition changes). Bug doesn't happen if you're doing programming, as all other keypads gets disabled and afterwards zones open/partition ready status message call resetZones. Probable solution is to call pauseZones only if ( * ) is pressed from same partition as the one on which is virtual keypad set. FIXED in commit