I have a T25 doorstation (software MX-V4.4.2/73) with a BellRFID module (hardware: 2.3, software v1.1.0.0), with two BellButtons.
Until recently this worked without a problem, however since a couple of days one of the BellButtons generates random key presses. See system messages below for an example:
16:48:06 IPMSG HttpRequestKim[29907] Notify sent to 192.168.0.42:80. 237 bytes in 0.376s.
16:48:20 IPMSG HttpRequestKim[29991] Notify sent to 192.168.0.42:80. 237 bytes in 0.371s.
16:48:26 IPMSG HttpRequestKim[30024] Notify sent to 192.168.0.42:80. 237 bytes in 0.373s.
16:48:34 IPMSG HttpRequestKim[30073] Notify sent to 192.168.0.42:80. 237 bytes in 0.380s.
17:17:24 IPMSG HttpRequestKim[8380] Notify sent to 192.168.0.42:80. 237 bytes in 1.908s.
17:17:54 IPMSG HttpRequestKim[8554] Notify sent to 192.168.0.42:80. 237 bytes in 0.380s.
17:18:00 IPMSG HttpRequestKim[8585] Notify sent to 192.168.0.42:80. 237 bytes in 0.401s.
17:20:50 IPMSG HttpRequestKim[9561] Notify sent to 192.168.0.42:80. 237 bytes in 0.374s.
17:20:59 IPMSG HttpRequestKim[9612] Notify sent to 192.168.0.42:80. 237 bytes in 0.406s.
17:21:24 IPMSG HttpRequestKim[9742] Notify sent to 192.168.0.42:80. 237 bytes in 0.371s.
17:22:52 IPMSG HttpRequestKim[10280] Notify sent to 192.168.0.42:80. 237 bytes in 0.378s.
17:32:13 IPMSG HttpRequestKim[13529] Notify sent to 192.168.0.42:80. 237 bytes in 0.385s.
17:32:34 IPMSG HttpRequestKim[13661] Notify sent to 192.168.0.42:80. 237 bytes in 0.371s.
17:32:41 IPMSG HttpRequestKim[13702] Notify sent to 192.168.0.42:80. 237 bytes in 0.879s.
17:32:51 IPMSG HttpRequestKim[13766] Notify sent to 192.168.0.42:80. 237 bytes in 0.439s.
This happens at random times during the day and night.
These messages are sent to my domotics system which plays a ringtone. Needless to say this a not very pleasant. I have now disabled this but of course now I don’t know when someone rings the bell…
Thank you for your long-standing trust in MOBOTIX products!
As a first step, it’s important to determine whether the issue is mechanical or related to configuration. I recommend removing the BellRFID module from the frame to check if the random ringing persists. If the issue disappears, it may be caused by mechanical pressure on the frame itself.
Additionally, your system is currently running a very outdated firmware and MxBus version — dating back to 2017! Once the root cause has been identified, I strongly recommend updating your system to the latest versions:
Firmware Version: 4.7.3.11-r6
Bus Module Version: 1.1.0.6
This will ensure improved stability, performance, and compatibility with current MOBOTIX features.
first of all the Answer about the question how to update MxBus Modules
First, update the camera firmware.
After the reboot, you need to manually update each MxBus module. This is not a separate download. The update is embedded in the camera firmware but must be triggered manually via the camera’s Admin dialog.
A detailed how-to guide is available here:
About your new “Connection Issue”
Possible Cause: Cable, Connection, or Power Issue
Please follow these steps to diagnose the problem:
Check the MxBus 2-wire connection
Inspect the cabling between the Door Station and the BellRFID module. Ensure the cable is intact, the connectors are properly seated, and there is no corrosion.
Inspect the RJ45 connector to the camera
Verify that the Ethernet connector is clean, corrosion-free, and securely plugged into the camera.
Check the camera’s power supply
How is the camera powered—via PoE or a MOBOTIX power adapter?
Has the PoE class changed recently?
Have you added any new PoE-powered devices to the switch that might affect power availability?
Review the system log
Look for older error messages indicating a “lost connection” or similar issues.
Power cycle the camera
What happens if you disconnect the camera from power and reconnect it? Does the issue persist after reboot?
I will see to the update of the camera once the current issue is resolved.
I checked the MxBus wiring. Cables are OK (measured with continuity tester). Reseated the connector and applied contact cleaner.
Reseated RJ45 connector and applied contact cleaner.
Camera is powered by PoE. No changes were made to the switch providing the power. No new devices added.
The first time the ‘lost connection’ message appeared was on 26/10.
The camera was already power cycled a number of times. (Is there a way to shutdown the camera before disconnecting the power? On the admin page there is only the possibility to reboot.
System time is OK.
After removing the module and doing the above, the ‘lost connection’ message does not appear anymore. However, the intermittent random key presses still remain.
This is a module with 2 Bell buttons and the intermittent key presses only occur on one of them, never on the other…
perfect that the “lost Connection” of the BellRFID is solved!
Let us come back to my initial idea:
How is the behaviour with a “loos” BellRFID (out f the Frame in the wall). To understood if it is a mechanical issue (pressure on the Modul which block the Button)?
May you can share a image of your installation!
Second Mechanical check is to remove the Buttons of the BellRfiD itself to see if the random Calls stopp´s.
Please check the black small buttons afterwards , if the “klick” behaviour on all identical or if one of them not “klick”
When I had removed the bellbuttons yesterday I already had a look at these arrows, however the arrows were hard to distinguish. I have now inserted them the other way around just for testing. Apparently it does not make any difference. It is strange that this has worked for so many years without a problem. It is also not clear to me how the direction makes any difference, the buttons look quite symmetrical.
On a related note: what is the maximum thickness of the paper that is inserted in the bellbutton. Now it is a heavy duty paper.
I will do a test tomorrow with the bellbutton removed (if it doesn’t rain…). The problem is also that sometimes several hours go by without the bell ringing and then suddenly it rings twenty times in a row…
The thickness of the paper should not be an issue with ‘normal’ paper. However, if it is folded several times and the rubber insert of the key protrudes beyond the key housing, please remove the paper.
The important test is to remove the key itself and see if the problem disappears.
Also, when i push the middle buttons of the upper key, the door bell (through my media server with an http request) rings and also the doorstation bell. However, when I push the middle buttons of the lower key, the doorbell does not ring even though that is the one that generates the random door bell rings…The doorstation bell does not ring, I only hear a beep and the blue LED in the right hand corner lights up.
After you removed the button inlays and the random ringing still occurs, while the BellRFID works properly on the second button, I assume you’ve already checked that the side buttons produce a normal “click” sound. Based on that, I would exclude the following issues:
A mechanical issue caused by a stuck inlay button
An MxBus connection issue, since the other button functions correctly and only signals when pressed
We see very few defective BellRFID units in our repair department. While a hardware fault is possible, I find it unlikely in this case.
To me, this behavior seems more like a misconfiguration. You mentioned that “nothing has changed in the configuration,” but based on your latest findings, it sounds like something might be off in the camera setup.
Why do you believe the random calls are triggered by the BellRFID buttons? Did you verify this in the camera recordings and see the specific event marked in red at the bottom of the image?
Refer to the attached document , which explains the symbols shown in a MOBOTIX camera’s live view. These symbols indicate the camera’s status and the status of connected functions, such as:
AS symbol for Activity Sensor Event
I/O symbols for inputs/outputs like door or barrier control
Please check what is shown in your setup—especially during the false ringing events.
If this is okay, I would recommend performing a firmware update and updating the MxModules. If the issue still occurs afterward, please contact your MOBOTIX partner to get in touch with MOBOTIX Support and provide the camera DUMP file for further analysis.
The reason why I believed that the issue had something to do with the BellRFID module is because each time the random calls occurs (this night there were more than 200!) an entry in the system messages is shown that says:
IPMSG HttpRequestKim[6455] Notify sent to 192.168.0.42:80. 237 bytes in 0.373s.
This message is generated from an IP Notify Profile (HttpRequesKim) that is called from an Action Group triggered by event ‘Signal: BellRFID 2’ which is the lower button.
I have a similar IP Profile for another Action Group triggered by Signal: BellRFID 1 for the upper button.
Strangely enough these messages disappear from the system messages. The +/- 200 messages from this night have disappeared and now there is a line: “292 deleted messages”.
At this moment the lower button is not functional, pressing it does not ring the doorbell and no httprequest is made. I will have a look at the settings
This is what is currently shown on the camera image:
Am I correct that there are no more spare parts available for the T25/26? I had a quick look at some suppliers and they all indicated that the BellRFID module was not available anymore.
IPMSG HttpRequestKim[6455] Notify sent to 192.168.0.42:80. 237 bytes in 0.373s
Only display the action itself, not the trigger event.
It is important, however, that we can still identify what has triggered this action.
I understand that this information is configured in the Action Group, but in the camera view, the camera symbol does not show BellRFID 1 highlighted in red.
When the BellRFID 1 module falsely triggers the IP Notify up to 200 times overnight, this should be visible during playback for proper analysis. Can ypu share a image of the Playback which shows the false moment?
If I understand correctly, the situation has now changed:
BellRFID 2 (lower button) is producing false alarms — it was previously working correctly.
BellRFID 1 (upper button) no longer functions at all.
Let’s return to the initial troubleshooting steps for clarity:
Mechanical issue – Checked
MxBus connection issues – Checked
Firmware update (Camera & BellRFID) – Not done yet
Configuration check – In progress
Before diving deeper into the configuration, I recommend updating your system from the 2017 version to the 2024 release.
Please create a backup of both your camera configuration and the BellRFID module before performing the update.
I’m afraid the situation has deteriorated again: the messages “Lost connection to MxBus modules BellRFID” have started to reappear…
I have now again opened the T25 and inspected the Mx bus wiring again: I cannot see anything wrong with those two wires. I have cleaned the connector on the camera module again.
Previously I had also already interchanged the upper and lower buttons. That did not make a difference either.
So at the moment BellRFID 1 is again working normally.
BellRFID 2 does not function when pressed. Since I did not want to receive another 200 mails overnight, I had left the system with the lost MX Bus connection…
I restarted the system again this morning with the intermittent connection. Unfortunately it can take several hours before anything happens…
I do not have a Playback image as I had disabled the script that takes a screenshot when the bell rings.
In the given circumstances where the MxBus connection gets lost, I don’t feel very comfortable to update the system at the moment.
On another note: as a backup workaround I am now trying to get the CameraBellButton to work.
I use the same setup as I do for the BellRFID buttons, but without success. Is there a document somewhere that explains the setup for the CameraBellButton?
This is a new behavior or at least the cleaning of the connectors was not solve the issue: losing the MxBus connection is problematic. For stable and reliable communication, a functioning MxBus connection is essential.
Your last option is to update the system. Hopefully, this is a software-related issue caused by your outdated firmware and Bus Module version. If the problem persists after the update—and assuming the PoE power supply is stable—it is likely a hardware issue with either the BellRFID module or the camera.
In your case, the system is currently unstable and not functioning properly. You have nothing to lose by updating. Please make sure to back up the camera configuration and the BellRFID module before proceeding!
This assumes that no other MxBus modules (e.g., DoorMaster, RS232 IO Box) are connected to the system.
Workaround: Using the Doorbell Button on the Camera
As a temporary workaround, you can use the doorbell button on the camera as you suggested. You’ll find a detailed description of all available options here: [insert link or reference].
This weekend I did some additional testing and found out that the ghost ringing by the HttprequestKim is not triggered by the Action_group where this is defined. I added another action to that group but the second action is never executed. So the HttprequestKim must be triggered by something else.
Also when I stop the MXBus connection to the BellRFID module, the ghost rings dissapear.
The doorbell on the camera used to work, but now it doesn’t anymore. Pressing it does not ring the doorstation doorbell neither. When the ghost HttprequestKim happens, the doorstation bell rings as well.
Something else I noticed is that when the system is rebooted, there are 6 items in the device properties for the BellRFID module:
Termination
Backlighting
Button configuration
RFID Encryption method
RFID Reader
Stand-alone authentication workflow.
But when I stop and restart the MXBus connection there are only three:
The update of the camera software was fast - one minute or so.
However, when I updated the BellRFID firmware, the first attempt failed without any warning.
The second attempt was successful but took about 20 minutes!
In the Event Overview I have marked the BellRFID 2 as Inactive.
The ghost rings are still there. At the time of writing this, the blue LED in the upper righthand corner on the BellRFID module is constantly flashing and a beep is sounding…
I am now going through the configuration to see if anything has changed because the doorstation has worked for many years without issues.
Another question: is the RFID module with the keypad the same as the one that comes with the bellbuttons?. In the event that I would have to replace the hardware, I have a source that has the keypad module available. The availability of these modules is very limited…
Thank you for proceeding with the update – this is an important step to rule out additional factors during the analysis.
It is completely normal that:
The camera firmware update takes only 1–2 minutes.
The MxBus module update can take several minutes and sometimes requires a second attempt. This is nothing to worry about.
The upper blue LED flashing continuously suggests that the RFID module is not correctly initialized.
A section from the Quick Install guide describes the expected status after a successful auto-configuration:
Once the auto-configuration is completed, the white camera illumination is on and the BellRFID shows:
The green status LED flashing continuously.
The blue LED flashes briefly and then turns off.
My recommendation for a final check:
Reset the MxBus modules to factory defaults
Reset the camera to factory defaults
Run the auto-configuration of the Doorstation and follow the steps in the manual
Assumption: You have created a backup of the camera and BellRFID after the firmware update!
After a successful auto-configuration:
There should be no spontaneous loss of the MxBus connection.
Both bell buttons should work.
The system should run stably.
Once confirmed, you can start setting up your IP Notify actions again – but do it step by step.
If this is not the case there is a hardware issue with the BellRFID, please let me know the results
About your second Question:
Another question: is the RFID module with the keypad the same as the one that comes with the bellbuttons?. In the event that I would have to replace the hardware, I have a source that has the keypad module available. The availability of these modules is very limited…
This will not work. The Keypad Module and BellRFID Module share the same electronic board, but they use different software flags. A Keypad will always be recognized by the system as a keypad.
However, pressing the physical key on the cameramodule does nothing.
Is there something else that needs to be set?
With regards to the reset to factory defaults:
The system integrator that installed the T25 did not provide the keyboard inset, required for the setup, nor the RFID cards.
Also, I have no idea what the SuperPIN is. Is this reset to the factory default as well? In the video the person enters 123456789. Is this the factory default?
I have contacted the system integrator but have not received any news yet. In the mean time they have switched to a different brand of doorstations many years ago, so I doubt they will be of any help…
At this moment I have disabled the RFID module (not physically, but in the Admin setup pages, otherwise I can’t open the door anymore with the fingerprint reader that is part of the system…
