P44-DSB - Information for installation and support

Attention - Uncorrected machine translation

This German version of the following text is currently 100% machine translated. In case of ambiguity, please refer to the German version (which in this case is the original written by hand).

This documentation page is intended for supporters and installers, and provides useful information for planning, installation and maintenance.

The following quick links refer directly to particularly important topics, otherwise the table of contents (displayed on the left as a column if the browser page is wide enough, on the mobile at the top) gives an overview.

Systematic troubleshooting:

P44-DSB is not displayed or not reliably displayed in the dSS:

Call the web interface of the P44-DSB remotely:

Too much/too little visible in the log:.

DALI bus problems:

Enocean problems:

Get support from plan44:

Access to the P44 DSB web interface.

For installation and support, access to the P44-DSB device web interface is required. Normally and with a PC/Mac in the local network, this can be accessed via the dSS configurator in the "Hardware" tab, by right-clicking on one of the P44 lines at "Meter & Controller ".

In case of support, however, one often wants to access remotely, or the connection to the dSS does not yet exist. Then the following methods help:

Locating a P44-DSB in the local network.

If the P44-DSB is set to DHCP (which it should be, see network configuration), then the IP address in the LAN router can usually be found in a table of DHCP clients.

However, the P44-DSB always make themselves discoverable in the local network via DNS-SD. DNS-SD is also the mechanism used by the dSS to find P44-DSBs.

Tools with graphical interface:

On the command line:

macOS and partly Windows, from Windows 10, depending on the installed software.
with dns-sd -B _http._tcp retrieve the list of devices, tool must be terminated with Ctrl-C.
with dns-sd -L 'name of the device EXACTLY as in the list' _http._tcp display hostname of the device, something in the form p44dsbe243215672.local.
show the IP address with dns-sd -G v4 hostname.local..
Linux, Windows with Windows Subsystem for Linux (WSL) installed:
with avahi-browse -t -r _http._tcp show all devices and their IP addresses.

Remote Access.

Direct to P44-DSB-DEH2, P44-DSB-E2, P44-DSB-D, P44-DSB-E (but not the older model P44-DSB-DEH).

Starting with firmware 2.0.0.0, P44-DSB devices have a direct way to enable remote access in a similar way to dSS:

Indirectly via dSS (also works for the older P44-DSB-DEH).

If digitalSTROM remote access to an installation exists, the web interface of connected P44-DSB can also be reached via a so-called ssh tunnel:

Network configuration.

Network - to be considered in general

Static IP or not?

Connection between dSS and P44-DSB.

Troubleshooting P44 DSB problems.

General procedure.

For successful troubleshooting, the following questions should be addressed in advance in all cases, in this order:

  1. State of LED on device:.

    • not lit at all → check power supply. If the power supply is OK, the LED is never completely dark.
    • is constantly glowing yellow on the P44-DSB-DEH (first DALI model), even after waiting for a while → probably the power supply is ageing and provides just barely enough current for the LED, but no longer for normal operation of the fixture. Replace with a 12V or 15V power supply with at least 800mA current capability and positive pole inside the plug. Most commercially available WLAN routers have such power supplies.
    • glows yellow for a long time after startup: if a DALI bus with many DALI ECGs/drivers is connected → patience! DALI is slow and takes a long time (>10min possible depending on number of DALI devices) after a restart. Hectic interrupting and restarting usually makes the situation worse.
    • green with occasional yellow flashing → normal operation, everything OK, yellow flashing indicates activity (button pressed, state change of a luminaire, sensor value, etc.).
  2. Does the device appear in the dSS configurator in tab "Hardware" → "Meter & Controller "?

  3. Can the web interface of the P44-DSB be accessed?

    • On-site or via Teamviewer to a device on-site: by right-clicking on one of the P44-DSB lines in "Hardware" → "Meter & Controller ", at the very bottom of the context menu select "Open Configuration Interface ".
    • By remote: if the dSS configurator is accessed remotely via pagekite link, the menu command will not work. However, there are several options for remote access to the P44-DSB web interface.
    • If the web interface appears only partially or strangely, or displays error messages ("Ajax error..."), this is mostly due to the browser cache → reload page with Cmd-R (Mac) / Ctrl-R or F5 (PC), in case of doubt also force reload with Cmd-Shift-R (Mac) / Ctrl-F5 or Ctrl-Shift-R (PC).
  4. Which firmware version does the device have?.

    • If the firmware is very old (<version 2.0), newer dSS cannot connect → update P44-DSB.
  5. Does the problematic end device appear on the "Devices " tab in the P44-DSB web interface?

    If not:

    • For DALI: see DALI troubleshooting.
    • For EnOcean: see teach-in
    • For hue: check bridge for function (using the hue app), possibly rescan via "Devices" → hue header → "(i)" button → "Scan for devices..." → "Look for new devices only "
  6. Is the problematic device working from the P44-DSB web interface?

    • If the device was detected by the P44-DSB at startup, but is currently unreachable or, in the case of wireless sensors, has not sent a value for a very long time, the line in the list in the "Devices " tab is grayed out. The column "Status " may tell you why (most common: timeout for sensors → check reception situation).

    • For devices with fast outputs (lights, switching sockets, etc.): Press the button with the gear icon and adjust the output value manually.

      Does the device respond? If not:

    • For EnOcean heating valves: these have very slow reacting outputs, it can take up to 40min for the output to change depending on circumstances (summer mode, battery condition). Therefore manually adjusting the output value for testing does nothing. The function can be better checked by analyzing the log.

    • For pushbuttons: Use the "Identify device... " function on the "Device " tab of the P44-DSB web interface, and then press the button. The dSUID of the push button should be displayed and the corresponding line in the list will be highlighted in blue.

      If the (EnOcean) button does not respond reliably: check signal strengths.

    • For sensors and inputs: Press the button with the three-line icon. Then all inputs and sensors are displayed, with continuously (every 2 seconds) updated value and indication when this was last sent by the hardware ("Last updated ").

      If (EnOcean) sensors do not provide a value, or much too infrequently: check signal strengths.

Backup of the configuration.

A backup of the configuration of the P44-DSB should be made of each installation.

Support requests to plan44.ch

Support requests to plan44.ch work most efficiently via the support form or email, especially if the following info is already noted down at the same time:

  1. Serial number of the affected device.

    • The serial number is displayed in the P44-DSB web interface under "System" → "Serial Number " and can be selected and copied by right-clicking. MAC, GTIN and vdc host dSUID are not relevant for support by plan44.ch and do not need to be noted separately.
    • The serial number can also be found on the label of the device.
  2. Precise error description.

    • Which device (specify dSUID or exact name) is not working?
    • Which operating steps were taken: Scene called up? Button pressed? Direct setting in the web interface?
    • What should have happened?
    • What has happened (or not)?
  3. Send logfile if necessary.

    • If a problem has occurred recently, it may be helpful to download the current log and send it along with the support request. A complete log is much more useful for analysis than just a screenshot with a few lines.
    • Just a look into the log can also show errors before a support request is necessary: More info about logs see next chapter.
    • In case of DALI problems the "DALI Hardware Summary" (see below) is also very helpful.
  4. Possibly send configuration backup.

    • If a P44-DSB does not work at all anymore, and a backup of the configuration is at hand, this can be useful to analyze the problem. As long as the P44-DSB is still accessible/operable, this is not necessary.
  5. Remote access link for remote support (plan44.ch and own remote support)

    • With direct access to the affected device, error diagnoses work faster and better.
    • Access to a P44-DSB can be done either via a digitalSTROM remote access link (please send along, specify dSS password), or via direct remote maintenance (not for old model P44-DSB-DEH) ,as described here.

Logs.

In many cases, the log files can shed light on when something is not working. The point is not to understand every line, but to get an overview of what is going on and see any error messages.

!!! note "Logs are deleted by reboot". Unlike the dSS, the logs of the P44-DSB are only in RAM, not in flash. That means they will be deleted when the device is rebooted. Therefore, in case of problems, download the current logs and save them** before restarting.

Loglevel

Log messages have a "level" (importance/detail level):

The maximum desired log level can be set on the tab "System" -> "Logs" by clicking on the small number links 7,6,5,4:

Log Settings

By default (after reboot) log level 5 is set, i.e. the messages with level 6 and 7 (info and debug) are not output. This results in not too many messages, but they make the basic activity on the device visible.

On each log line the corresponding level is written in the square bracket after the date as a letter, in the following example the "N":

[2022-11-09 18:17:51.492 N] vdSD 72536785B63C6CD8807428477EE2909600: changes to PRESENT

Log download.

Using the links "current " and "previous " (see screenshot above), the current and previous logs can be downloaded as a whole (depending on the browser, it will be displayed as text in a new tab or end up in the download folder).

Focus on a problematic device.

Sometimes you want to monitor a specific device, but don't want to set the log level higher overall because otherwise the log will be flooded with too many messages.

DALI

General

Selection of DALI devices

The unique identification.

Therefore: For a really long-term stable DALI installation that can be expanded without problems, the following applies:

Unfortunately Serial Number botched, even with DALI2

Unfortunately, not even the DALI2 certification gives 100% certainty that the "unique serial number" (as required by the standard unequivocally) is really unique. It happens (fortunately very rarely) that two units of the same device model have the same serial number, even for DALi2 certified devices. If the two devices are connected to the same P44-DSB, it will detect this and treat the serial number as invalid; but if the two are on different P44-DSBs but in the same digitalSTROM installation, they get the same dSUID and the dSS sees only one device.

Multi-channel or DT8?

For the smoothest possible installation and maintenance - as mentioned above: Use DALI driver with unique electronic serial number!

If exclusively DALI devices with unique serial numbers are in use on a bus, there will be no problems with swapped luminaires in the dSS, and then the bus can be completely rescanned at any time without the slightest concern, and DALI drivers can be added or replaced at any time. However, if DALI drivers without correct serial numbers are in use, the following step-by-step procedure is recommended:

  1. wire DALI installation as completely as possible, do not yet connect P44-DSB to the DALI bus.

  2. function check of luminaires still without connecting DALI bus to P44: all should light up when supply is present (except for non-factory new devices, which may have been configured to a different switch-on brightness). If a luminaire remains dark: Check wiring. 3.

When the DALI bus is completely wired: check that there is no external voltage on the bus. **External voltage can lead to a defect in the P44-DSB!

Only now connect DALI to P44-DSB and then start/restart. 4.

  1. Patience after restart, especially with many DALI devices and if many of them are DT8 luminaires (more data to transfer). A complete scan of a full bus will take 10min or longer. DALI has a very low data rate and takes time! Hectic restarting, resetting, etc. does nothing.

  2. Don't start immediately with assigning in dSS! Also don't start with forming DALI groups, etc. This work is for the cat when, because of address conflicts, the bus must be completely rescanned and the short addresses (partially) reassigned.

  3. If under "Devices " on the "DALI " line under Status you get an orange error message because of "Address collision " (move the mouse pointer over it to read the whole text), this means that several devices on the bus have the same short address. If not exclusively brand new DALI devices were used (but maybe already used in another (test-)installation), this can happen and is not a real problem at this point. In this case:

    • Under "Devices" → DALI header → "(i)" button → "Scan for devices..." → "Service-only scans..." → "Force full re-scan of all devices " trigger.
    • Again patience, may take a bit longer than a normal scan.
    • Under "Devices " on the "DALI " line there should now be no error displayed.
  4. Briefly test the basic function of each dimmer, preferably in the P44-DSB interface:

    • "Devices" → DALI header → "(i)" button → "DALI bus diagnostics... ".
    • For each DALI driver a green field should appear (compare number with actual installed devices).
    • Pressing yellow button "all lights off " must switch off all lights connected to the bus, just as "all lights max brightness " must switch them all on.
    • Clicking on a green field must make a light fully lit for a short time and then go to minimum brightness (not off).
    • If up to here something does not work, the error must be searched and found (mostly: bad DALI contacting, too much voltage drop, possibly wiring error, see below)! As long as the lights don't work properly on this level, no further configuration in P44 or dSS makes sense!

    • Optional: Use the "gear " button of the lights to call the brightness slider (for color lights additionally slider for color temperature + color) and test if the lights react as expected.

  5. If everything works as expected, you can assume that everything is correct on the DALI + P44-DSB level. Now the luminaires should also appear in the dSS, and can be given names and room assignments.

    • If in the dSS the fixtures do not appear or are grayed out, although they are in the list in the P44-DSB, it is more likely due to an unreliable connection to dSS or general network problems.

    • If it took a force full re-scan (see above), then there are probably excess grayed out lights visible in dSS. These can be deleted.

    • It is worth to compare the number of lights in the dSS with the number of lights in the P44-DSB, if they are not the same, something is still wrong. But first reload the list on both sides, so that the display is really up to date.

    In the P44-DSB:

    Number of devices in the P44

    In the dSS:

    Number of devices in the dSS

  6. only when everything is working properly, also via dSS, you can consider turning on the optimizer, if with larger groups of lights the reaction looks too much "running light" (one after the other).

Documentation of the installation.

It is very useful to have documentation of an installation (and besides, of course, always: a backup of the configuration).

If the commissioning was successful and the luminaires have been assigned names, it is therefore recommended to have a "DALI Hardware Summary" created for this purpose. Apart from a bit of waiting time (slow bus scan) this costs nothing and is extremely useful for later troubleshooting or for sending along with support requests.

The "DALI Hardware Summary" can be triggered via the corresponding button "Devices" → DALI header → "(i)" button → "DALI Hardware Summary... ". A separate browser page will pop up, if the bus is full it may take several minutes until the result is displayed:

DALI Bus Overview/Hardware Summary

The appearing table contains all important information about all devices on the bus:

Keep this browser page printed or saved as a PDF with the project documentation.

If an installation contains only DALI drivers with unique electronic serial number, and the newly added DALI devices also have an electronic serial number, they can simply be connected, and the P44-DSB restarted, and if there are any address conflicts (only happens with non-factory added devices), a "Force Full Re-Scan" can be triggered. There will be no confusion, all dSUIDs will remain stable, and the new fixtures will appear in addition.

However, if DALI drivers without serial number are in the installation or such are added, the following procedure is recommended:

  1. DALI hardware summary of the current situation retrieve as a basis.

  2. unplug DALI bus at P44-DSB (or de-energize everything, incl. P44-DSB).

Connect new DALI drivers/luminaires. 4.

Leave DALI bus unplugged, (re)start P44-DSB until it is ready (LED lights up green, possibly with occasional short yellow flashes). 5.

For safety: Check DALI bus for external voltage before connecting to P44-DSB. **External voltage can lead to a defect at the P44-DSB!

Only now connect the DALI bus. The P44-DSB does not make an automatic scan, the list of DALI devices therefore remains empty.

  1. "Devices" → DALI header → "(i)"-button → "DALI bus diagnostics... ", and check basic DALI function (as described above at commissioning steps).

  2. If there are orange fields here, then there are address conflicts, and it needs a "Full Rescan". If all fields are green, there is probably no address conflict, but it is not completely sure.

  3. Comparing with the "DALI-Hardware Summary" you can quickly see which DALI short addresses have been added.

  4. By clicking on the new green fields you can see if the new luminaires work and if an existing luminaire has an address conflict and reacts. If this happens, it needs a "Full Rescan".

  5. Factory new fixtures do not have a short address yet, so they do not have a green field yet. This is not a problem, they will get a free short address during the scan (see next point).

  6. if no address conflict was detected, a normal scan is now sufficient: "Devices" → DALI header → "(i)" button → "Scan for devices..." → "Normally re-scan and re-register all devices ". After that, all the previous devices and the new ones should appear in the list and, with some delay, in the dSS.

If address conflicts are detected, a "Full Rescan" is needed. It can happen that a newly added device without electronic serial number is mixed up with a previously installed one without serial number - then you have to correct the names and room assignments in the dSS accordingly.

  1. otherwise, the general commissioning instructions apply, see above.

  2. even after a change, documentation of the new state with a "DALI hardware summary" is recommended.

Optimizer

Because the DALI bus has a very low data rate, in rooms with many DALI luminaires, you see a "running light effect" when scenes are called, especially when colored luminaires (which need more data) are involved.

Since the beginning, the P44-DSB offers the possibility to manually form groups so that several DALI dimmers appear as one digitalSTROM luminaire in the system. The disadvantage is that the dimmers then run in parallel in any case and can no longer be controlled individually at all.

Therefore, in most cases the "Optimizer" is the better solution. This automatically forms DALI groups and DALI scenes (max. 16 each) for frequently used digitalSTROM scenes, which can then be called up perfectly synchronously. The optimizer keeps statistics about the different scene settings and the number of affected luminaires, and assigns scenes to the most frequent combinations (after at least 4 calls). Combinations that have not been used for a long time are released again over time for newer, frequently used ones.

The settings for the optimizer can be found under "Devices" → DALI header → "(i)" button:

DALI-Optimizer-Settings.

The following settings are available:

Optimization disabled Default setting: Optimizer disabled. In case of problems (luminaires react wrong on scene calls, select this setting first)

Use existing Optimization
The optimizer uses the previously learned scenes, but does not learn anything new. This can be used to freeze a proven situation and protect it from changes. But if the dS-scenes are changed, the optimizer won't work with time because the saved scenes don't exist anymore. Before that the setting "Automatically create optimizations..." must have been used for a while, otherwise this setting has no effect.
Use existing Optimization, update when scenes are changed/saved
The optimizer uses the previously learned scenes, and adjusts the settings when the scene settings are changed, but does not create new scenes or delete existing ones. The setting "Automatically create optimizations..." must have been used for a while before, otherwise this setting has no effect.
Automatically create optimizations based on usage statistics
This is the recommended normal setting. This is the recommended normal mode. The optimizer keeps statistics on the digitalSTRIOM scenes called and makes sure that a DALI scene is used for the most used ones (3 lights or more), so that the lights switch perfectly in sync.
Clear Optimizer Cache (but no mode change) - use with care
When this option is clicked, the optimizer cache is cleared, i.e. all existing optimizations are removed, and learning starts again. The optimizer mode is not changed by this.

If the log is set to at least level 6, a statistic of the scene calls appears after each optimized scene call, the line with the asterisk is the one affected by the current scene call.

[2022-11-30 20:16:50.913 N] Optimizer statistics after 88 optimizable calls for vDC 25FA7890CFB75913800265EE292CB2AB00 (office DALI):
- 'callScene' called 7 times (weighted, raw=7), last 23 seconds ago, contentId=0, numdevices=7, nativeAction='DALI_scene_1'
* 'callScene' called 3 times (weighted, raw=3), last 21 seconds ago, contentId=5, numdevices=7, nativeAction='DALI_scene_0'
- 'callScene' called 4 times (weighted, raw=4), last 79515 seconds ago, contentId=0, numdevices=5, nativeAction='DALI_scene_2'
- 'dimChannel' called 9 times (weighted, raw=10), last 79531 seconds ago, contentId=0, numdevices=5, nativeAction='DALI_group_1'
- 'callScene' called 5 times (weighted, raw=5), last 6932 seconds ago, contentId=72, numdevices=11, nativeAction='DALI_scene_3'

DALI debugging.

General procedure

  1. if luminaires react differently than expected when scenes are called and the DALI optimizer is switched on, as the very first measure, switch off the optimizer. With the optimizer switched on, troubleshooting is very tedious. If afterwards the lights react correctly again, the optimizer should be reset, but can usually be used again afterwards.

  2. if connected lights do not appear at all in the list of P44-DSB:

    • Test if the luminaire responds to DALI commands at all: "Devices" → DALI header → "(i)" button → "DALI bus diagnostics... " call up.
    • Pressing the yellow button "all lights off " must switch off all luminaires connected to the bus, just as "all lights max brightness " must switch them all on. A light that does not react here is defective or not correctly connected to the bus. In this case: check / measure DALI bus wiring.
    • Are more than 64 DALI devices connected? Attention, simple multi-channel dimmers without DT8 may occupy one address for each channel. More than 64 addresses on the same bus are not possible!
    • If the lights react at "all lights max/off": Rescan bus with "Devices" → DALI header → "(i)" button → "DALI bus diagnostics..." → "Scan for devices..." → "Look for new devices only... ". This will search again on the bus for devices not found so far. Patience, this can take 10min and more with many devices on the bus.
    • If the fixtures are now still not in the list: check / measure DALI bus wiring.
    • Also take a look at log, possibly error messages are visible. 2.
  3. if connected luminaires appear in list of P44-DSB, but are grayed out, this means that the luminaire was correctly addressable at the last restart of the P44-DSB or at the last bus scan, but not anymore.

    • This points most likely to a loose contact
    • e.g. with DALI bus via busbars, which are not explicitly suitable for bus extra-low voltage, there may be high contact resistances at the contacts - latching/unlatching and moving them a bit may help.
  4. if the connected lights appear in the list of P44-DSB, and are not grayed out: Press gear button and use sliders to check luminaire operation. If the fixture responds correctly here, but not via scene calls or from the dSS, then it is not a DALI problem, but rather a connection problem between P44-DSB and dSS.

DALI bus wiring.

Possible bus problems are:

  1. if the wiring has too high contact resistances (bad contacts) and as a result the voltage drop between P44 and (one, or more) DALI devices on the bus becomes too large. At least 12V must be present between the DALI connections of each device otherwise proper functioning is not guaranteed. 2.

  2. if one or more DALI devices are defective or "cracked" and put too much load on the DALI bus. A single DALI device may not draw more than 2mA current from the bus, the whole bus in total not more than 128mA (or number of devices * 2mA), see "Measure DALI bus" If these values are exceeded, especially the bus scan (reading data from the DALI devices) will not work properly. But it may be that the control via "Devices" → DALI header → "(i)" button → "DALI bus diagnostics..." → "all lights max/min/off... " still works, so this is not a guarantee for a proper bus!

  3. if the bus has a short circuit somewhere. Normally the P44-DSB detects this and displays it as an error message, but if this happens combined with poor contacting and correspondingly high voltage drop, not necessarily.

  4. if the bus once had external voltage when the P44-DSB was connected. This can lead to a defect in the P44-DSB (internal chip fuse, usually repairable but the device must be sent in).

DALI bus measure

DALI-Bus-Measurements

!!! warning "Measurement when bus is active is not meaningful". If a bus scan is running, or scenes are called continuously, then measuring bus voltage and current is not reliable. Wait until scans are completed. The LED on the P44-DSB should be green, not flickering wildly yellow/red.

!!! note "The DALI bus voltage is DC". Use DC setting on the meter accordingly. AC measurement may also show something if the bus is not completely at rest, but nothing meaningful.

If DALI bus problems are suspected, the following should be measured:

  1. first, easiest to measure quickly: the voltage at the P44-DSB, at the green terminal. If it is lower than about 14.5V, disconnect the DALI bus and measure again at the P44-DSB to make sure that the power supply to the P44-DSB is working.

    • if without connected bus no voltage can be measured, then the P44-DSB is defective (probably internal fuse blown by external voltage, can usually be repaired)
    • if the voltage without bus is ok and only with connected bus no or very little voltage can be measured, then the bus has a short circuit somewhere.
    • if the voltage drops below 14V with the bus connected, but is at about 14.5V without the bus, one or more devices on the bus is drawing too much current -> measure bus current.
  2. if voltage at P44-DSB is too low: measure total bus current, one DALI wire must be disconnected at P44-DSB: The total current must not be more than 128mA, or not higher than number of devices times 2mA. So for a small bus with 4 DALI devices already 20mA are too much (42mA = 8mA max.) If the current is higher, most likely one of the DALI devices is defective and draws too much current. The faulty device must be found and removed*, it also interferes with the communication of all other devices.

  3. if the total current is too high: a single DALI device must never draw more than 2mA current from the bus. Modern DALI devices usually draw much less, more in the range of 0.2mA. Depending on the wiring, the current can be checked at individual devices, or parts of the bus can be measured to find out which device is drawing too much current. 3.

  4. if the voltage at the P44-DSB is correct and the total current is not too high: measure the DALI voltage at unrecognized or not properly working dimmers/drivers, and at the farthest connections. This should be at least 12V everywhere, better higher. If the voltage is lower, there are probably bad contact points/terminals in between on the bus causing voltage drops; these need to be found and fixed.

Enocean

General

Device compatibility, profiles

Teach-in and teach-out.

For learning and unlearning, the P44-DSB is put into learn mode, i.e. it listens until a learn telegram is received, and then remembers the Enocean address, or deletes it if it was already stored previously.

EnOcean devices can also be removed from the system via the web interface: "Devices" → Device line → "(i)" button → "Remove device... ", instead of unlearning them.

!!! warning "Unlearning is not the same as deleting". When deleting via the web interface, the device is removed from the system and all associated configuration is deleted (name, digitalSTROM group/color etc.). When unlearning, the device is also removed, but the configuration is retained, i.e. when the same device is taught in again later, it is configured as it was before. When deleting via the web interface, only the relevant element is deleted for devices with several elements (e.g. pushbuttons), the others are retained. When unlearning, all elements of the unlearned device disappear.

Pushbuttons and simple sensors (F6-xx-xx and D5-xx-xx)

These devices do not know a separate learn mode, but send the same telegram each time they are actuated.

If, during the teach-in process of a pushbutton in the vicinity, another pushbutton is accidentally actuated, then this could be taught-in by mistake.

To prevent this from happening, these devices are only taught-in when a sufficiently strong radio signal is received from them, i.e. when the device is approximately within 30cm or closer to the P44-DSB.

If for some reason the device can not be brought that close, you can do the teach-in on the web interface without the "proximity check" (w/o proximity check, button with red writing on the right), with the risk that another device will be taught in by mistake.

On/off learn button

Remove superfluous button halves

Almost all buttons contain the same module (PTM215), which has contacts for two pushbuttons (or 4 single pushbuttons). Only the pushbutton caps make the difference whether two rockers or only one is actually available for the user:in. After teach-in, EnOcean pushbuttons always appear as 2 separate rockers - but with a single pushbutton, the second rocker remains without function, and can be removed via the web interface.

Other devices (A5-xx-xx and D2-xx-xx)

These devices send a separate learn action (triggered by a special button, magnetic contact, etc.) that is different from normal operation. Mains-powered devices sometimes send the learn action once after the supply voltage is applied. Details of this must be found in the manufacturer's documentation.

Therefore, the radio signal strength is not evaluated for these devices, i.e. they can and should always be taught-in and taught-out normally (button without red writing)!

Encryption

Newer EnOcean devices support encrypted connections. Even if the Encean hardware ID of a device is known, these cannot simply be tapped or simulated by an attacker with a jammer. Otherwise, they function in the same way as unencrypted connections.

Ranges, signal strength, measuring

External antennas on P44-DSB-DEH2 and P44-DSB-E2.