Merge Dev in to Master #123
Merged
Conversation
This file contains 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
Owner
davesmeghead
commented
Jul 27, 2024
davesmeghead
commented
- Uses latest HA settings, recommendations and nothing is deprecated
- Add a new Emulation Mode for minimal interaction with the Panel, a Sensor is created instead of an Alarm Panel Entity
- Limited support for PowerMaster 360 and 360R models
- PowerMaster panels now able to trigger Siren, Panic, Emergency and Fire using HA Service
- Robust use of the Integration in HA, Startup, Reload, Disable and Enable
- Redone Integration Configuration Settings, including putting strings in EN.json for future translation
- Different sensor delay settings for Motion/Camera, Magnet/Wired and Other Sensors
- Breaking changes to Services
- Breaking changes to Events
- Improved processing of PowerMaster Data, especially to support Zones 32 to 64 for PowerMaster 30 and 33
- Started to look at how to get the Image from a Camera PIR for PowerMaster panels
This is the first development release. I have made significant changes to the code since last years release, some parts have been re-written completely. These changes have been made to: - Make it more robust - Get ready for additional features coming over the next few months, particularly for PowerMaster panels This current dev release includes: - Changes to the Home Assistant Service calls - Changes to the Home Assistant Events and the Event Data Specifically for PowerMaster Panels, the changes in this dev release include: - The "Command" Service call includes Trigger, Mute, Emergency, Panic and Fire. These should trigger your alarm so test it at a time of the day that doesn't annoy your neighbours. - It handles F4 Image messages from Camera Sensors (and doesn't crash the integration). This data is not processed yet but I'm working on it. - I have added 2 Emulation Modes, "Minimal Interaction" and "Passive Monitor". Please do not use these, they are there to support capabilities I have not yet included. - In the settings there is a selection to include EEPROM data in the Panel Attributes. This is a minor thing but it makes it a use choice. As said above, this is a development release. Remember that I have rewritten chunks of the code ready for future releases and as such changes have been made to the Event and Service Data. In other words your existing automations may no longer work. The Integration update should be reversible, you should be able to delete the content of the visonic directory and put back the original version.
0.9.2 Bug fixes, EPROM Decode update and JPG Camera images
Changes to accommodate a USB connection to a 360 Panel (and maybe a 360R Panel) It gets to Standard Plus OK but then fails to Enroll so I've added a PanelConfig setting to prevent it from Enrolling. Extended the PanelConfig to ease the configuration checking. This includes making the keep alive interval set in PanelConfig per panel type. Changed all EPROM to EEPROM for consistency. I'm not sure whether it is EPROM or EEPROM inside the panel but at least its consistent use now. Further change to decoding the EEPROM Various bug fixes and comments Add the available property to Entities that didn't have it.
Including moving the code to the new HA way of creating and removing integrations and entities. Added use of HA HassEntryKey for configuration data
Removal of Override Code as its now set on the Entity Removal of B0 Dev Configuration
Cast panel_num to string in async_step_device to resolve TypeError during string concatenation
File "/config/custom_components/visonic/config_flow.py", line 233, in async_step_device
await self.async_set_unique_id(VISONIC_UNIQUE_NAME + " Panel " + panel_num)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
TypeError: can only concatenate str (not "int") to st
Fix TypeError in async_step_device method
Introduce 'Magnet Close Delay' configuration option for magnet sensors Works the same way as Motion Off Delay but for magnet sensors Sensors other than Magnet still use the old timer value
Three delays now exist in total: - One for Motion/Camera sensors - One for Magnet/Wired sensors - One for Emergency sensors (Gas,Smoke,Flood,Temperature, etc.) Delay of 0s is assumed for UNKNOWN and IGNORED Since home assistant config flow variables changed from motion_off to motion_off_delay and 2 new options where added, users need to reconfigure integration or edit .storage
Delays where not updating when using configure button on HA UI
Added Magnet Closed Delay configuration option
0.9.5.0 Significant changes to configuration settings and Message Decode This is the first Dev release that is matched to the updated Wiki Dev Release
Added sensor 0x93 - Next MCW
Process B0 51 and B0 39 correctly Remove the set baud as its not working properly
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.