Hi

I’m attempting to integrate a Paradox MG5050 panel with Home Assistant using the Paradox Alarm Interface (PAI) 3.6.1 add-on, connected via a local IP connection to an IP150+ module. The connection to the IP150+ succeeds, but authentication with the MG5050 panel fails with the error Invalid PC Password , despite using the correct PC Password (section [911] in MG5050 programming) and Installer Code, verified via BabyWare and panel programming.

Environment

• PAI Version : 3.6.1 (Home Assistant add-on)
• Paradox Panel : MG5050, firmware 7.01.012
• IP Module : IP150+, firmware 5.06.030
• Connection Type : Local IP (not SWAN)
• Home Assistant : Core 2025.4.1, Supervisor 2025.03.4, OS 15.1
• MQTT : Mosquitto broker (core-mosquitto), configured and working

Configuration

Relevant YAML configuration:

CONNECTION_TYPE: IP
IP_CONNECTION_HOST: [redacted local IP]
IP_CONNECTION_PORT: 10000
IP_CONNECTION_PASSWORD: paradox
IP_CONNECTION_USERNAME: null
IP_CONNECTION_SITE_ID: null
PASSWORD: [redacted 4-digit PC Password]
MQTT_ENABLE: true
MQTT_HOST: core-mosquitto
MQTT_PORT: 1883
MQTT_USERNAME: mqttUser
MQTT_PASSWORD: [redacted]
MQTT_HOMEASSISTANT_AUTODISCOVERY_ENABLE: true
IP_INTERFACE_ENABLE: true
IP_INTERFACE_PASSWORD: paradox

With LOGGING_LEVEL_CONSOLE: 10, the relevant log excerpt is:

2025-04-21 14:22:00,894 - INFO - MainThread - PAI.paradox.connections.connection - Connection established 2025-04-21 14:22:00,894 - INFO - MainThread - PAI.paradox.connections.ip.commands - Authenticating with IP Module 2025-04-21 14:22:00,909 - INFO - MainThread - PAI.paradox.connections.ip.commands - Authentication Success. IP(114) Module version 20, firmware: 5.6, serial: 72022f00 2025-04-21 14:22:00,936 - INFO - MainThread - PAI.paradox.connections.ip.commands - Session successfully established with IP Module 2025-04-21 14:22:00,938 - INFO - MainThread - PAI.paradox.paradox - Connecting to Panel 2025-04-21 14:22:01,042 - INFO - MainThread - PAI.paradox.paradox - Panel Identified MG5050 version 7.1 build -1 2025-04-21 14:22:01,042 - INFO - MainThread - PAI.paradox.paradox - Initiating panel connection 2025-04-21 14:22:01,171 - INFO - MainThread - PAI.paradox.hardware.spectra_magellan.panel - Installer login 2025-04-21 14:22:01,268 - ERROR - MainThread - PAI.paradox.paradox - Got ERROR Message: Invalid PC Password 2025-04-21 14:22:01,270 - ERROR - MainThread - PAI.paradox.lib.handlers - Exception caught during message handling Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/paradox/lib/handlers.py", line 116, in handle await handler(data) File "/usr/local/lib/python3.11/site-packages/paradox/lib/handlers.py", line 65, in call result = self._handle(data) ^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/paradox/paradox.py", line 636, in handle_error_message raise AuthenticationFailed() paradox.exceptions.AuthenticationFailed

Steps Taken

1. Verified the PC Password (section [911] in MG5050 programming) and Installer Code using BabyWare and keypad programming. Both are correct and work in BabyWare for panel access.
2. Tested both PC Password and Installer Code in the PASSWORD field, as well as defaults (0000, 1234, 5555). All result in the same Invalid PC Password error.
3. Successfully authenticated with the IP150+ using IP_CONNECTION_PASSWORD: paradox.
4. Enabled DEBUG logging (LOGGING_LEVEL_CONSOLE: 10) to capture more details.
5. Reviewed PAI documentation and GitHub issues but found no specific references to IP150+ firmware 5.06.030 or MG5050 firmware 7.01.012

Suspected Issues

• The log mentions “Installer login,” suggesting PAI may be attempting to use the Installer Code instead of the PC Password, despite the PASSWORD field being set to the PC Password.
• Possible incompatibility between PAI 3.6.1 and IP150+ firmware 5.06.030, which is designed for SWAN server integration and may restrict local IP authentication.
• Potential bug in PAI’s handling of PC Password authentication for MG5050 firmware 7.01.012

Questions

• Does PAI 3.6.1 support local IP connections with IP150+ firmware 5.06.030 and MG5050 firmware 7.1?
• Should the PASSWORD field use the PC Password (section [911]) or the Installer Code for this setup?
• Are there known workarounds for the Invalid PC Password error with newer IP150+ firmware?
• Could the “Installer login” log entry indicate a specific authentication requirement or bug?

Additional Notes
Local IP connection is preferred over SWAN due to reliability. SWAN attempts failed due to unresolved hostnames (e.g., swan.paradoxmyhome.com, turn.paradoxmyhome.com).

Willing to provide further logs or test specific configurations if needed.

Thank you for any assistance or insights!

1 post - 1 participant

Read full topic

Hopefully this is a suitable place to ask this question.

I’ve just started exploring ESPresence for room presence data.
Currently have 4 nodes in 4 rooms - ESP32-C3 Superminis
Device detection works, and I can go between rooms and get a room change.

The device being detected is my Pixel 9 Pro - problem is out of all devices seen on the Fingerprints dialog this is the weakest/least accurate.
I can be 50cm-100cm from a node and it is reading 8m+

I’ve modified two of the nodes with this antenna mod. It has improved the detection of the P9P and it appears “closer” but I don’t feel this should be required.
Even so, a 50cm away node is still reading at 3-4m.

Has anyone seen similar?
Any way to increase the BLE signal from a Pixel 9 Pro?

I realise the more nodes the better, which can somewhat eliminate the issue but I’d like to know if I can improve without a hardware mod and having many nodes in each room.

1 post - 1 participant

Read full topic

I have HA Green and it has been great! The only issue I have is that the BT adapter listed below, which controls my SwitchBot blinds, has dropped out after a year. It has been fine for a while

This is what I purchased:

The name on the BT says TechKey, but in HA, it is listed as Realtek Bluetooth. Is there a fix I’m missing to stop it from dropping?

If I reseat it, it works again, but I’m tired of having to go to the IDF room to keep doing this.

1 post - 1 participant

Read full topic

Has anyone successfully used a multi-rocker / multi-gang zigbee switch with “on with timed off” feature?

In zigbee2mqtt’s documentation (like this ), the feature should be used by publishing messages like {"state" : "ON", "on_time": 300}. However, multi-rocker switches require the state key to be state_top, state_left, etc.

I have tried these methods, and none were successful:

• Publishing {"state_top" : "ON", "on_time": 300} to zigbee2mqtt/FRIENDLY_NAME/set results in an error message: “z2m: No converter available for ‘on_time’ on ‘FRIENDLY_NAME’: (300)”.
• Publishing {"state" : "ON", "on_time": 300} to zigbee2mqtt/FRIENDLY_NAME/top/set has no effect at all. The switch does not turn on.

Has anyone had any success?

1 post - 1 participant

Read full topic

I have a stand alone machine setup solely to run Frigate. Its Proxmox with a Frigate container running Docker. Its an Intel (Dell Optiplex 7050 Micro MFF, i5, 16GB RAM, 256GB SSD, 1tb data drive).
I have tried various setting but I dont get any recording, alerts or motion detections in the review of Frigate interface. I do however, bizarrely get person image detected within the Home Assistant add on.

Heres my config:

mqtt:
  enabled: true
  host: 192.168.0.23
  port: 1883
  user: MQTTUSER
  password: xxxxxx
ffmpeg:
  hwaccel_args: preset-vaapi
#Global Object Settings
objects:
  track:
    - person
#  filters:
#    person:
#      min_area: 1000
#      max_area: 500000
cameras:
  drive2:
    ffmpeg:
      inputs:
        - path: rtsp://frigate:frigate01@192.168.0.80:554/h264Preview_01_main
          input_args: preset-vaapi
          roles:
            - record
        - path: rtsp://frigate:frigate01@192.168.0.80:554/h264Preview_01_sub
          roles:
            - detect
#    detect:
#      width: 640
#      height: 480
#      fps: 5
#    objects:
#      track:
#        - person
#    live:
#      stream_name: live
#    zones: {}
#    review: {}
  Garage:
    ffmpeg:
      inputs:
        - path: rtsp://192.168.0.125:554/user=admin_password=xxx//live/0
          input_args: preset-vaapi
          roles:
            - record
        - path: rtsp://192.168.0.125:554/user=admin_password=xxx//live/1
          roles:
            - detect
#    detect:
#      width: 1280
#      height: 720
#      fps: 5
detectors:
  cpu:
    type: cpu
#detectors:
#  ov:
#    type: openvino
#    device: CPU
#    model:
#      path: /openvino-model/FP16/ssdlite_mobilenet_v2.xml
#model:
#  width: 320  # Changed from 300 to 320
#  height: 320 # Changed from 300 to 320
#  input_tensor: nhwc
#  input_pixel_format: bgr
#  labelmap_path: /openvino-model/coco_91cl_bkgr.txt
#version: 0.14
version: 0.14

I also get these two errors through google resources screen:

I am aware I have other issues with the setup but trying to overcome this initially. Any help very much appreciated

1 post - 1 participant

Read full topic

I’ve got a weather automation using Met Office data, which I’m trying to send out via MQTT to use elsewhere on my network.

The automation action is set up like this:

- data:
      topic: metweather/weather
      retain: true
      qos: "0"
      payload: >-
        {  "condition": {{states('sensor.london_gatwick_airport_weather_daily')|
        string }}, 
           "temperature": {{states('sensor.london_gatwick_airport_temperature_daily') | string }},
           "feels_like": {{states('sensor.london_gatwick_airport_feels_like_temperature_daily') | string }},
           "visibility": {{states('sensor.london_gatwick_airport_visibility_daily') | string }},
           "wind_speed": {{states('sensor.london_gatwick_airport_wind_speed_daily') | string }},
           "wind_dir": {{states('sensor.london_gatwick_airport_wind_direction_daily') | string }},
           "wind_gust": {{states('sensor.london_gatwick_airport_wind_gust_daily') | string }} 
        }
    action: mqtt.publish

It works, but at the far end I’m receiving this:

b'{"condition": rainy, \n "temperature": 16,\n "feels_like": 14,\n "visibility": Good,\n "wind_speed": 9,\n "wind_dir": WSW,\n "wind_gust": 11 \n}'

At the far end, i’m trying to decode it with (Python 3.9):

weather = json.loads(msg.payload.decode('utf-8'))

and it looks to be choking on the carriage returns.
Is there any way to publish the json in a format that the remote Python code will accept and decode properly?

I’ve tried to put everything in one line but it doesn’t seem to help, as I guess somewhere underneath HA is breaking the line down?

1 post - 1 participant

Read full topic

Hi there!

I’m not new to home assistant but I am new to the automation world of HA.
Normally I always program things in Node-Red, now I would like to start making automations in HA itself.

What I would like to do is let the robot vacuum run when it has been 4 days or longer after the last run.
Whats the best way to make this? Can this be done in one automation or does it need helpers to save the last time it has cleaned?

What I was thinking now I make a automation to save the last time it has cleaned into a helper (thing i’m running into there is how to save the date and time).
And as second trigger when it is longer then 4 days ago.

1 post - 1 participant

Read full topic

I’m running HA as a VM in Proxmox with an Aeontec Zwave dongle passed to the VM by Device ID. This works fine until it comes time to update ZWave JS UI (which gets frequent updates). >50% of the time there’s an update to this addon specifically zwave stops working in HA. All devices become unavailable. Fully shutting down the HA VM and starting it back up always fixes this issue.

What I’ve noticed is that when ZWave JS UI updates, sometimes the device number in the VM changes. Here are lsusb results running before and after updating the addon:

[core-ssh ~]$ lsusb
Bus 003 Device 001: ID 1d6b:0003
Bus 002 Device 003: ID 0658:0200
Bus 001 Device 001: ID 1d6b:0001
Bus 002 Device 001: ID 1d6b:0002
[core-ssh ~]$ lsusb
Bus 003 Device 001: ID 1d6b:0003
Bus 002 Device 004: ID 0658:0200
Bus 001 Device 001: ID 1d6b:0001
Bus 002 Device 001: ID 1d6b:0002

Notice how 0658:0200 (my zwave dongle) changed from device 003 to 004.

What can I do to prevent this so I don’t have to reboot HA so frequently?

1 post - 1 participant

Read full topic

Hi there
I’d like to setup an automation that is triggered by a virtual button and then based on time of year (for example, January to June) turns on certain lights (and their associated effects) then with the same button (ideally same automation) pressed in July through September each year sets a different number of lights with different effects.

I’ve already setup how the light strips and bulbs will react color and effect wise through the button but scratching my head on how to take range of months in a year within the automation. I believe Template may be the way to go but not sure how to get started with this. Can anyone offer assistance or a script/template ?

Thanks so much

1 post - 1 participant

Read full topic

Hi all,

I am sucessfully using a Home Assistant installation with the NGINX Home Assistant SSL proxy add on. Recently I startet to look into InfluxDb and Grafana and set up these add ons, too. Both add ons seem to work fine.
I now want to embed the Grafana panels into my Home Assistant dashboards. To do so, I’m adding a website-card which points to the embed url from Grafana. This is where the issues begin.
As I’m accessing Home Assistant via https, the Iframes, created by the website-card, also need to referr to https urls.
I therefore want to use the NGINX Home Assistant SSL proxy add on to forward an additional port to Grafana, so that this port can be used to acess the Grafana panels. However, I could not find any information on how this could be done. I saw, that the NGINX add on configuration allows customized server configurations for NGINX, but I could not find out where the files need to be placed.
Did anyone do this before and can point me to the right way?

Greetings
Offline

1 post - 1 participant

Read full topic

Hello All,

I have nine humidity sensors and would like to receive a notification on my iPhone when the batteries fall below 10%.
I’d like the notification to include the name of the sensor(s) that triggered the notification.

I’ve done a test with this configuration, but without success:

alias: Test
description: ""
triggers:
  - trigger: numeric_state
    entity_id:
      - sensor.buanderie_batterie
    below: 95
conditions: []
actions:
  - action: notify.mobile_app_iphone_patrick
    metadata: {}
    data:
      title: Low battery
      message: "{{ state_attr(trigger.entity_id, 'friendly_name') }}"
mode: single

I’m sure my mistake is basic…

Thanks and regards,
Patrick

2 posts - 2 participants

Read full topic

Hi there,
I’m new in HA and in that forum. Set-up my HA and also energy-board. But the PV-results are wrong and I have no idea, what’s going on. If I go into survey with all entities, the results of PV are ok.

7.022 W is the same number, as in openDTU.
In the energy-dashboard it shows a big peak between 6 and 7 am, inverters were started at 6:17.

And that should be the problem in detail:

What’s happening and how do I get the rigt results?

Thanks Norbert

PS: can only add one image as newbee!?

2 posts - 1 participant

Read full topic

Hi all

My HA has been running flawlessly up until I rebooted the PC I have it running on today and now it boots up but most of my key integrations won’t load.

From the web UI I can’t access the backup section or the log section.

I have rebooted a number of times to no avail.

I am running my instance via a Windows 11 PC with Virtual Box.

The last thing I did on it was update the front end to the latest - I can’t tell you what version as the system info page won’t load either.

What shall I do??

My last backup was yesterday but I can’t even figure out how I can restore…

3 posts - 3 participants

Read full topic

My Energy dashboard has been running perfectly since… Well: since it was introduced. Since two days however the dashboard displays “there is no data to show” despite that data being in the system for years now. I tried rolling back a backup, but that didn’t solve the issue. In the logs there is nothing meaningful that points to an underlying problem. The logbook and long term data is still working on entities. What could possibly be wrong here?

1 post - 1 participant

Read full topic

Hiya,

I’m trying to get my home battery to charge when the price is lowest in 24h and to discharge when price is highest in 24h.

I therefore need to compare the value from sensor “sensor.huis_electricity_price” to the attribute of the same sensor “Max price”.

How would I do this in the GUI? I tried, as a first step, a template sensor which unfortunately does not output a value. I then wanted to compare the huis_electricity_price sensor value to the value of this newly created sensor to create a true or false sensor so I can trigger an automation.

{{ state_attr(‘huis_electricity_price’, ‘Max_price’) | float }}

2 posts - 2 participants

Read full topic

I have 2 weather integrations in my system. KNMI and met.no. Now I only want the actual weather icon on a custom:mushroom-template-card but I can’t get this to work. Does anyone know how I can do this?

3 posts - 2 participants

Read full topic

I moved 10 smart plugs (IKEA inspelning, innr SP240 and Tuya) from ZHA to MQTT. They often fail to report updated values when I plug in a device. Then when I go to the HA Zugbee2MQTT menu page, visit the plug settings and tap the blue twin arrow update button, the values change immediately to the correct values. I tried multiple units, of different brands, all behave similarly.

Example: I plugged in my e-bike battery in an IKEA inspelning smart plug. The values I read were 227V, 1.42A and 11.8W. Impossible, as 227*1.42=322W and it’s a 150W charger.
After tapping the update buttons I got 227V, 0.71A and 150W, which is a whole lot better.

When I try the same with a ZHA connected IKEA inspelning plug, I get the correct values immediately and consistently.

Are we having some bug here?

All plugs have the latest firmware: 2.4.45 IKEA, 1.9.29 innr, tuya none
I’m running all the latest updates:
OS 15.2, core 2025.4.3, Mosquitto 6.5.0, Z2M 2.2.1-1

Any help, opinions and/or user experience very welcome.

Edit: FTR I am running ZHA and Z2M on the same HA instance simultaneously, on different channels. I have other Z2M devices (Tuya temp/humidity sensors) running great.

2 posts - 2 participants

Read full topic

Hi,

Try to eliminate border on entity card, but it remains after trying couple things. Any ideas?

type: weather-forecast
entity: weather.home
forecast_type: daily
show_current: true
show_forecast: true
card_mod:
  style: |
    ha-card {
      background: transparent !important;  # Transparent background
      border: none !important;             # No border
      box-shadow: none !important;         # No shadow
      padding: 10px !important;            # Optional padding
    }

1 post - 1 participant

Read full topic

This is undoubtably in the wrong category; but, being new here, I didn’t know where else to put it. Sorry.

I have a tile connected to an input button entity. When the icon is clicked, an automation fires to use a fingerbot to push the power button on an Epson printer. An Entities card showing the status of the printer as “unknown” will eventually update to show the printer as “idle” or maybe “printing”.

I would like to change the color of the Input button Tile based on the status of the printer entity.

Anyone have any thoughts?

Thanks in advance

1 post - 1 participant

Read full topic

Hi guys im using advanced camera card in live grid mode to display hikvision RTSP streams and I would like to cycle through the primary displayed large image every few seconds. Is there a way to do this with advanced camera card or should i be trying an alternative method?

Heres my code:

type: custom:advanced-camera-card
cameras:
  - camera_entity: camera.entry_gate
  - camera_entity: camera.exit_driveway
  - camera_entity: camera.exit_gate
  - camera_entity: camera.yard_left
  - camera_entity: camera.yard_right_3
    image: {}
media_gallery:
  controls:
    thumbnails:
      show_favorite_control: false
      show_timeline_control: false
      show_download_control: false
media_viewer:
  auto_play:
    - visible
  draggable: false
  zoomable: false
  lazy_load: false
  display:
    mode: grid
live:
  draggable: false
  zoomable: false
  lazy_load: true
  display:
    mode: grid
  transition_effect: slide
view:
  triggers:
    filter_selected_camera: false
    show_trigger_status: false
    actions:
      trigger: default

1 post - 1 participant

Read full topic