Jablotron PG output cannot be switched from TapHome

Symptom

The Jablotron integration seems to be working: the states of sensors, magnetic (Reed) contacts and PG outputs are all read correctly and update in the app. But switching a PG output from TapHome does nothing.

Typically the control in the app flips and then jumps back on its own: it changes, and a few seconds later it returns to its previous state. No error is reported and no device is marked as faulty.

Cause

The most common cause is an empty password in the JablotronCCU interface settings in TapHome.

This is easy to miss because the two directions of communication have different requirements:

• Reading needs no password. The JA-121T module sends the states of sections, PG outputs and peripherals on its own — whenever a state changes, and again every 10 seconds. TapHome only listens.
• Switching needs a password. Every command must be signed with a user code from the control panel. Without a valid code, the control panel rejects the command and the PG output keeps its previous state.

An installation without a password therefore shows live states everywhere and looks complete — until someone tries to switch a PG output.

Solution

Step 1: Enter the Jablotron Password in TapHome

1. Open Settings → Hardware → Jablotron
2. Fill in the password field in the format 1 * 2345, where 1 is the external user ID and 2345 is the user code from the Jablotron control panel
3. Save the settings

This user must already exist in the Jablotron control panel. The control panel logs every command under this user, so create a dedicated user for TapHome instead of using the personal code of one of the residents.

Step 2: Give This User Permissions to the PG Outputs

In the F-Link software, open the user account whose code you entered in Step 1 and check that it has permission to control the PG outputs you want to switch from TapHome.

If the user code has no permission for a PG output, TapHome still shows the state of that output, but the control panel rejects every command for it — the same symptom as when no password is entered at all.

Step 3: Turn Off the “Disable Alarm” Option for This User

Still in F-Link, turn OFF the option named Disable alarm for this user.

If this option is enabled for a user, the control panel interprets every communication attempt from that user as an attempt to deactivate the alarm. This is a flaw in the Jablotron communication protocol.

Step 4: Verify the Result

Switch the PG output from TapHome and watch it for about 15 seconds (one full refresh cycle plus a margin). If the new state stays, the command was accepted. If the output returns to its previous state, the control panel is still rejecting the command — continue with the section below.

What to Check If the PG Output Still Switches Back

If you got this far, the password and the permissions are probably correct and the problem is in the PG output itself. Check its settings in F-Link:

• The PG output is set as an impulse output. It switches for a moment and then returns to its off state by design. Change it to a bistable (ON/OFF) output so that it keeps its state.
• The PG output is driven by the control panel’s own logic — for example a section state, a detector, a schedule or a thermostat. That logic keeps overriding the command from TapHome. Either remove the internal activation source, or use a different PG output that has none.