Remove danielperna84 from links pt2

for custom_homematic

README.md

@@ -2,7 +2,7 @@
 
 Homematic(IP) [Integration for Home Assistant](https://www.home-assistant.io/getting-started/concepts-terminology/#integrations)
 
-[Installation](https://github.com/danielperna84/custom_homematic/wiki/Installation)
+[Installation](https://github.com/sukramj/custom_homematic/wiki/Installation)
 [Alternative Installation by J. Maus](https://github.com/jens-maus/RaspberryMatic/wiki/HomeAssistant-Integration)
 
 [Wiki with additional information](https://github.com/sukramj/hahomematic/wiki)
@@ -68,7 +68,7 @@ Advanced setups might consider this:
 
 This integration starts a local XmLRPC server within HA, which automatically selects a free port or uses the optionally defined callback port.
 This means that the CCU must be able to start a new connection to the system running HA and to the port. So check the firewall of the system running HA (host/VM) to allow communication from the CCU. This Traffic (state updates) is always unencrypted.
-If running HA on docker it is recommended to use `network_mode: host`, or specify [callback host/port](https://github.com/danielperna84/custom_homematic#callback_host-and-callback_port).
+If running HA on docker it is recommended to use `network_mode: host`, or specify [callback host/port](https://github.com/sukramj/custom_homematic#callback_host-and-callback_port).
 
 ### Authentication
 
@@ -289,7 +289,7 @@ These two options are required for _special_ network environments. If for exampl
 
 System variables are fetched every 30 seconds from backend (CCU/Homegear) and belong to a device of type CCU. You could also click on action on the integration's overview in HA.
 
-System variables are initially created as **[deactivated](https://github.com/danielperna84/custom_homematic#deactivated-entities)** entity.
+System variables are initially created as **[deactivated](https://github.com/sukramj/custom_homematic#deactivated-entities)** entity.
 
 The types of system variables in the CCU are:
 
@@ -335,7 +335,7 @@ Clears the cache for a central unit from Home Assistant. Requires a restart.
 ### `homematicip_local.create_central_links`
 
 Creates a central link from a device to the backend. This is required for rf-devices to enable button-press events.
-[See](https://github.com/danielperna84/custom_homematic?tab=readme-ov-file#events-for-homematicip-devices)
+[See](https://github.com/sukramj/custom_homematic?tab=readme-ov-file#events-for-homematicip-devices)
 
 ### `homematicip_local.copy_schedule`
 
@@ -523,7 +523,7 @@ Attention: This action gets the value for the entity via a 'getValue' from the b
 
 ### `homeassistant.update_device_firmware_data`
 
-Update the firmware data for all devices. For more information see [updating the firmware](https://github.com/danielperna84/custom_homematic#updating-the-firmware)
+Update the firmware data for all devices. For more information see [updating the firmware](https://github.com/sukramj/custom_homematic#updating-the-firmware)
 
 ## Events
 
@@ -541,14 +541,14 @@ The `PRESS*` parameters are evaluated for this event type in the backend.
 ### `homematic.device_availability`
 
 This event type is used when a device is no longer available or is available again,
-and can be used with the blueprint [Support for persistent notifications for unavailable devices](https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local_persistent_notification.yaml).
+and can be used with the blueprint [Support for persistent notifications for unavailable devices](https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local_persistent_notification.yaml).
 
 The `UNREACH` parameter is evaluated for this event type in the backend.
 
 ### `homematic.device_error`
 
 This event type is used when a device is in an error state.
-A sample usage is shown in the blueprint [Show device errors](https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local_show_device_error.yaml).
+A sample usage is shown in the blueprint [Show device errors](https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local_show_device_error.yaml).
 
 The `ERROR*` parameters are evaluated for this event type in the backend.
 
@@ -648,7 +648,7 @@ If a device's channels are assigned to multiple rooms or nothing is set, the are
 
 Not all parameters of a HomeMatic or HomematicIP device are created as entity. These parameters are filtered out to provide a better user experience for the majority of the users. If you need more parameters as entities have a look at [this](https://github.com/sukramj/hahomematic/blob/devel/docs/unignore.md) description. Starting with version 1.65.0 this can be configured in the reconfiguration flow under advanced options. You use this at your own risk!!!
 
-BUT remember: Some parameters are already created as entities, but are **[deactivated](https://github.com/danielperna84/custom_homematic#deactivated-entities)**.
+BUT remember: Some parameters are already created as entities, but are **[deactivated](https://github.com/sukramj/custom_homematic#deactivated-entities)**.
 
 ### Devices with buttons
 
@@ -665,7 +665,7 @@ See this [explanation](https://github.com/sukramj/hahomematic/blob/devel/docs/rs
 The `LEVEL` parameter of the HmIP-eTRV can be written, i.e. this parameter is created as a **number** entity and the valve can be moved to any position.
 However, this **manual position** is reversed shortly thereafter by the device's internal control logic, causing the valve to return to its original position almost immediately. Since the internal control logic of the device can neither be bypassed nor deactivated, manual control of the valve opening degree is not useful. The `LEVEL` parameter is therefore created as a sensor, and thus also supports long-term statistics.
 
-If you need the `LEVEL` parameter as number entity, then this can be done by using the [unignore](https://github.com/danielperna84/custom_homematic#unignore-device-parameters) feature by adding LEVEL to the file.
+If you need the `LEVEL` parameter as number entity, then this can be done by using the [unignore](https://github.com/sukramj/custom_homematic#unignore-device-parameters) feature by adding LEVEL to the file.
 
 ### Pressing buttons via automation
 
@@ -686,9 +686,9 @@ data:
 To receive button-press events for Homematic(IP) devices like WRC2 / WRC6 (wall switch) or SPDR (passage sensor) or the KRC4 (key ring remote control) or HM-PBI-4-FM (radio button interface) you have to several options:
 
 #### Option A:
-Use the action [create_central_links](https://github.com/danielperna84/custom_homematic?tab=readme-ov-file#homeassistantcreate_central_links).
+Use the action [create_central_links](https://github.com/sukramj/custom_homematic?tab=readme-ov-file#homeassistantcreate_central_links).
 A one time execution is required to activate the events.
-To deactivate the events the action [remove_central_links](https://github.com/danielperna84/custom_homematic?tab=readme-ov-file#homeassistantremove_central_links) can be used.
+To deactivate the events the action [remove_central_links](https://github.com/sukramj/custom_homematic?tab=readme-ov-file#homeassistantremove_central_links) can be used.
 
 #### Option B:
 With RaspberryMatic no program is needed for buttons. Events can directly activated/deactivated within ->Settings->Devices. Click the "+" of e.g. a remote control then click directly the "button-channel". Press "activate". There is no direct feedback but a action message should appear.
@@ -950,19 +950,19 @@ BidCos-RF devices have an optional parameter for put_paramset which defines the
 
 The following blueprints can be used to simplify the usage of HomeMatic and HomematicIP device:
 
-- [Support for 2-button Remotes](https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-2-button.yaml): Support for two button remote like HmIP-WRC2.
-- [Support for 4-button Key Ring Remote Control](https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-key_ring_remote_control.yaml): Support for four button remote like HmIP-KRCA.
-- [Support for 6-button Remotes](https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-6-button.yaml): Support for six button remote like HmIP-WRC6.
-- [Support for 8-button Remotes](https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-8-button.yaml): Support for eight button remote like HmIP-RC8.
-- [Support for persistent notifications for unavailable devices](https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local_persistent_notification.yaml): Enable persistent notifications about unavailable devices.
-- [Reactivate device by type](https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local_reactivate_device_by_type.yaml). Reactivate unavailable devices by device type.
-- [Reactivate every device](https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local_reactivate_device_full.yaml). Reactivate all unavailable devices. NOT recommended. Usage of `by device type` or `single device` should be preferred.
-- [Reactivate single device](https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local_reactivate_single_device.yaml) Reactivate a single unavailable device.
-- [Show device errors](https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local_show_device_error.yaml) Show all error eventy emitted by a device. This is an unfiltered blueprint. More filters should be added to the trigger.
+- [Support for 2-button Remotes](https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-2-button.yaml): Support for two button remote like HmIP-WRC2.
+- [Support for 4-button Key Ring Remote Control](https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-key_ring_remote_control.yaml): Support for four button remote like HmIP-KRCA.
+- [Support for 6-button Remotes](https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-6-button.yaml): Support for six button remote like HmIP-WRC6.
+- [Support for 8-button Remotes](https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-8-button.yaml): Support for eight button remote like HmIP-RC8.
+- [Support for persistent notifications for unavailable devices](https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local_persistent_notification.yaml): Enable persistent notifications about unavailable devices.
+- [Reactivate device by type](https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local_reactivate_device_by_type.yaml). Reactivate unavailable devices by device type.
+- [Reactivate every device](https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local_reactivate_device_full.yaml). Reactivate all unavailable devices. NOT recommended. Usage of `by device type` or `single device` should be preferred.
+- [Reactivate single device](https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local_reactivate_single_device.yaml) Reactivate a single unavailable device.
+- [Show device errors](https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local_show_device_error.yaml) Show all error eventy emitted by a device. This is an unfiltered blueprint. More filters should be added to the trigger.
 
 Feel free to contribute:
 
-- [Community blueprints](https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/community)
+- [Community blueprints](https://github.com/sukramj/custom_homematic/blob/devel/blueprints/community)
 
 These blueprints on my own system and share them with you, but I don't want to investigate in blueprints for devices, that I don't own!
 Feel free to copy, improve or enhance these blueprints and adopt them to other devices, and if you like create a PR with a new blueprint.

blueprints/automation/homematicip_local-actions-for-2-button.yaml

@@ -8,7 +8,7 @@ blueprint:
     Tested with HmIP-BSM, HmIP-BDT, HmIP-BSL, HmIP-WRC2. Should work with other device too.
     v2022-10-28
   domain: automation
-  source_url: https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-2-button.yaml
+  source_url: https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-2-button.yaml
   input:
     remote:
       name: 2-Button Device

blueprints/automation/homematicip_local-actions-for-6-button.yaml

@@ -8,7 +8,7 @@ blueprint:
     Tested with HmIP-WRC6. Should work with other device too.
     v2022-10-28
   domain: automation
-  source_url: https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-6-button.yaml
+  source_url: https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-6-button.yaml
   input:
     remote:
       name: 6-Button Device

blueprints/automation/homematicip_local-actions-for-8-button.yaml

@@ -8,7 +8,7 @@ blueprint:
     Tested with HmIP-RC8. Should work with other device too.
     v2022-10-28
   domain: automation
-  source_url: https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-8-button.yaml
+  source_url: https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-8-button.yaml
   input:
     remote:
       name: 8-Button Device

blueprints/automation/homematicip_local-actions-for-key_ring_remote_control.yaml

@@ -8,7 +8,7 @@ blueprint:
     Tested with HmIP-KRCA. Should work with other device too.
     v2022-10-28
   domain: automation
-  source_url: https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-key_ring_remote_control.yaml
+  source_url: https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local-actions-for-key_ring_remote_control.yaml
   input:
     remote:
       name: 4-Button Device (e.g. HmIP-KRCA)

blueprints/automation/homematicip_local_persistent_notification.yaml

@@ -3,7 +3,7 @@ blueprint:
   description: Display persistent notification if device is not available.
     v2022-12-11
   domain: automation
-  source_url: https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local_persistent_notification.yaml
+  source_url: https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local_persistent_notification.yaml
 
 mode: restart
 max_exceeded: silent

blueprints/automation/homematicip_local_reactivate_device_by_type.yaml

@@ -3,7 +3,7 @@ blueprint:
   description: Reactivate a device marked as not available by type.
     v2022-12-05
   domain: automation
-  source_url: https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local_reactivate_device_by_type.yaml
+  source_url: https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local_reactivate_device_by_type.yaml
   input:
     device_type:
       name: Device Type

blueprints/automation/homematicip_local_reactivate_device_full.yaml

@@ -3,7 +3,7 @@ blueprint:
   description: Reactivate every device marked as not available.
     v2022-12-05
   domain: automation
-  source_url: https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local_reactivate_device_full.yaml
+  source_url: https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local_reactivate_device_full.yaml
 
 mode: restart
 max_exceeded: silent

blueprints/automation/homematicip_local_reactivate_single_device.yaml

@@ -3,7 +3,7 @@ blueprint:
   description: Reactivate a single device marked as not available.
     v2022-12-05
   domain: automation
-  source_url: https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local_reactivate_single_device.yaml
+  source_url: https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local_reactivate_single_device.yaml
   input:
     device_id:
       name: Homematic device

blueprints/automation/homematicip_local_show_device_error.yaml

@@ -4,7 +4,7 @@ blueprint:
     Display errors emitted by devices. This is an unfiltered blueprint. More filters should be added to the trigger.
     v2022-12-21
   domain: automation
-  source_url: https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/automation/homematicip_local_show_device_error.yaml
+  source_url: https://github.com/sukramj/custom_homematic/blob/devel/blueprints/automation/homematicip_local_show_device_error.yaml
 
 mode: restart
 max_exceeded: silent

blueprints/community/homematicip_local-actions-for-12-button.yaml

@@ -8,7 +8,7 @@ blueprint:
     by @djusHa
     v2022-12-05
   domain: automation
-  source_url: https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/community/homematicip_local-actions-for-12-button.yaml
+  source_url: https://github.com/sukramj/custom_homematic/blob/devel/blueprints/community/homematicip_local-actions-for-12-button.yaml
   input:
     remote:
       name: 12-Button Device

blueprints/community/homematicip_local-actions-for-4-button-fm.yaml

@@ -8,7 +8,7 @@ blueprint:
     by @andyboeh
     v2022-12-05
   domain: automation
-  source_url: https://github.com/danielperna84/custom_homematic/blob/devel/blueprints/community/homematicip_local-actions-for-4-button-fm.yaml
+  source_url: https://github.com/sukramj/custom_homematic/blob/devel/blueprints/community/homematicip_local-actions-for-4-button-fm.yaml
   input:
     remote:
       name: 4-Button Device (e.g. HM-PBI-4-FM)

changelog.md

@@ -1440,7 +1440,7 @@ Rounding support for Concentration of HmIP-SCTH230 will be re-added with HA 2023
   Old behaviour was to display a DEFAULT value.
   As soon as events have been received from the CCU the state will switch to the correct state.
   This should be relevant, if HA has been restarted shortly after the CCU has been restart.
-  See [Readme](https://github.com/danielperna84/custom_homematic#noteworthy-about-entity-states) for further information.
+  See [Readme](https://github.com/sukramj/custom_homematic#noteworthy-about-entity-states) for further information.
 - Add attribute state_uncertain
   There is now an extra attribute at each entity, that shows is the state of the entity might be uncertain due to a CCU restart.
   This should be relevant, if the CCU has been restarted and HA is still running.
@@ -1524,7 +1524,7 @@ Rounding support for Concentration of HmIP-SCTH230 will be re-added with HA 2023
 
 - Bump hahomematic to 1.8.0
   - Enable additional sysvar entity types
-- Create sysvars with new types. [See](https://github.com/danielperna84/custom_homematic#system-variables)
+- Create sysvars with new types. [See](https://github.com/sukramj/custom_homematic#system-variables)
 
 # Version 1.7.3 (2022-06-01)
 

custom_components/homematicip_local/const.py

@@ -23,8 +23,8 @@
 DEFAULT_MQTT_ENABLED: Final = False
 DEFAULT_MQTT_PREFIX: Final = ""
 
-LEARN_MORE_URL_XMLRPC_SERVER_RECEIVES_NO_EVENTS: Final = "https://github.com/danielperna84/custom_homematic?tab=readme-ov-file#what-is-the-meaning-of-xmlrpc-server-received-no-events--xmlrpc-server-empf%C3%A4ngt-keine-ereignisse"
-LEARN_MORE_URL_PONG_MISMATCH: Final = "https://github.com/danielperna84/custom_homematic#what-is-the-meaning-of-pending-pong-mismatch-on-interface--austehende-pong-ereignisse-auf-interface"
+LEARN_MORE_URL_XMLRPC_SERVER_RECEIVES_NO_EVENTS: Final = "https://github.com/sukramj/custom_homematic?tab=readme-ov-file#what-is-the-meaning-of-xmlrpc-server-received-no-events--xmlrpc-server-empf%C3%A4ngt-keine-ereignisse"
+LEARN_MORE_URL_PONG_MISMATCH: Final = "https://github.com/sukramj/custom_homematic#what-is-the-meaning-of-pending-pong-mismatch-on-interface--austehende-pong-ereignisse-auf-interface"
 
 CONF_ADVANCED_CONFIG: Final = "advanced_config"
 CONF_CALLBACK_HOST: Final = "callback_host"

custom_components/homematicip_local/manifest.json

@@ -4,7 +4,7 @@
   "after_dependencies": ["mqtt"],
   "codeowners": ["@SukramJ"],
   "config_flow": true,
-  "documentation": "https://github.com/danielperna84/custom_homematic",
+  "documentation": "https://github.com/sukramj/custom_homematic",
   "homekit": {},
   "integration_type": "hub",
   "iot_class": "local_push",