LogicMachine Forum Forum

Hello, Three observations about the installation method in kb.logicmachine.net/integration/sip-server/, in case they are useful. 1. A FAILED DOWNLOAD LEAVES A PARTIAL INSTALL, SILENTLY The script runs ten os.execute('opkg --force-depends install http://...') calls and checks none of their return values. The guard at the top is if not io.exists('/etc/init.d/kamailio') and /etc/init.d/kamailio is created by the fourth package (kamailio3) - before the six module packages are installed. So if a download fails after kamailio3 succeeds, the result is a running Kamailio with some modules missing, and re-running the script does nothing, because the guard is now satisfied. Nothing reports an error. During my own installation one of the downloads did not complete (dl.openrb.com was not responding at that moment - it is reachable again now), which is how I noticed this. This does not seem to be a one-off. While checking which module packages exist, I made twelve sequential requests to the same host: eleven returned a status (200 or 404) and one returned no response at all. That one was kamailio3-mod-maxfwd, which does exist - it returned 200 when I retried the identical request a minute later. I cannot rule out something on my own network, but a single dropped request in a run of twelve is enough to break an unchecked ten-step install. Checking the exit status of each opkg call, or testing for one of the module files instead of the init script, would make a retry actually repair the ins

Hello, I am using the Kamailio SIP registrar described in kb.logicmachine.net/integration/sip-server/ on an LM5M3. The device tree reports "i.MX6UL LM5M3", ARMv7 Processor rev 5 (v7l), with genohm-scada 20251204. I installed it with the official resident-script method for the i.MX6 target: - kamailio3 3.3.7-1_imx6, plus the maxfwd, usrloc, registrar, rr, sl and tm modules - your default kamailio.cfg, unmodified First, it works well and I want to be clear about that. With no configuration changes I get multiple contacts registered against a single AoR, parallel forking to all of them, first-answer-wins with CANCEL to the losing branches, and RTP flowing directly between the endpoints - including between different subnets - since no media relay module is loaded. This is exactly the behaviour I need from a registrar for door-entry intercoms. I have run into three limits that all appear to need a rebuild rather than a configuration change, so my main question is simply: is a rebuilt package for the i.MX6 target something that can be provided? If not, the individual items below are moot. 1. BRANCH LIMIT OF 12 I registered 15 contacts against one AoR. All 15 registered successfully, but an incoming call forked to only 12 of them. I repeated the test and got 12 again, with a different subset of 12 each time. The log shows: ERROR: [dset.c:306]: append_branch(): max nr of branches exceeded ERROR: registrar [lookup.c:298]: lookup(): failed to append a branch Since this is MAX_BRANCHES

Setup: LM firmware 2025, Visu, apps/js/localbus.js (v=20251031), Android kiosk panels (WebView) plus desktop Chrome for comparison. PROBLEM On some corporate networks a middlebox (IPS / application control / proxy / NAC policy) resets established TCP sessions a few seconds after they open. Visu's live-data WebSocket is hit by this; the classic HTTP-polling visualization is not. With the current client logic the visible effect and the server load are much larger than necessary: - on every WebSocket close, localbus.js waits 1 s, - then re-downloads the FULL object registry via POST /apps/localbus.lp (about 285 KB in our project, 2832 objects), - and only then reopens the WebSocket. So each reset costs the user ~3 s of "reconnecting" spinner with frozen values, and costs the LM a full registry regeneration. Field symptom that started this: WebSocket killed 1-1.5 s after open, floor plan stays rendered, spinner flashes every ~3 s, values freeze. A laptop on the same LAN (not subject to the policy) worked fine. WHAT WE MEASURED Lab: a transparent TCP relay between client and LM that kills every session after N seconds. 1) Current client, Android panel, kill after 5 s WS lifetime 5.0 s, visible gap 2.9-3.0 s per cycle, ~37 % of the time disconnected, server work per cycle: registry POST 285 KB + WS handshake. 2) Current client, Android panel, kill after 2 s The registry POST never completes, page stays blank with a permanent spinner. 3) Patched client (see below), desktop Chrome, k

Setup: LM firmware 2025, Visu, apps/js/localbus.js (v=20251031), Android kiosk panels (WebView) plus desktop Chrome for comparison. PROBLEM On some corporate networks a middlebox (IPS / application control / proxy / NAC policy) resets established TCP sessions a few seconds after they open. Visu's live-data WebSocket is hit by this; the classic HTTP-polling visualization is not. With the current client logic the visible effect and the server load are much larger than necessary: - on every WebSocket close, localbus.js waits 1 s, - then re-downloads the FULL object registry via POST /apps/localbus.lp (about 285 KB in our project, 2832 objects), - and only then reopens the WebSocket. So each reset costs the user ~3 s of "reconnecting" spinner with frozen values, and costs the LM a full registry regeneration. Field symptom that started this: WebSocket killed 1-1.5 s after open, floor plan stays rendered, spinner flashes every ~3 s, values freeze. A laptop on the same LAN (not subject to the policy) worked fine. WHAT WE MEASURED Lab: a transparent TCP relay between client and LM that kills every session after N seconds. 1) Current client, Android panel, kill after 5 s WS lifetime 5.0 s, visible gap 2.9-3.0 s per cycle, ~37 % of the time disconnected, server work per cycle: registry POST 285 KB + WS handshake. 2) Current client, Android panel, kill after 2 s The registry POST never completes, page stays blank with a permanent spinner. 3) Patched client (see below), desktop Chrome, k

Hi, We have two issues with the LM Home app. Short video attached (9 s). 1. Settings screen does not stay open — auto-redirects to Cloud/local page On an LM Home installation where settings have already been entered (cloud info entered, or an LM added, or only partially configured), we cannot change anything afterwards. This is not about first setup — it is about modifying an existing setup. Steps to reproduce (see video): Long-press the LM Home icon → tap Settings . The settings menu appears (Add LM automatically / Add LM manually / Remove LM / Clear credentials / Clear configuration). Within about one second, the app shows "Connecting to LM cloud" and jumps to the LogicMachine Cloud login page on its own — before we can tap anything. Expected behaviour: once the Settings screen is open, the app should not auto-redirect to Cloud or to the local page in any way until the user leaves the Settings screen themselves. 2. Feature request: "Local only" option in Settings Please add a checkbox in Settings: "Local only" . When it is selected: The app should not ask about Cloud at all. If the local LM is reachable → open the page bound to the user account. If the local LM is not reachable → show a message on the page such as "You are currently not on the local network" . Local only is a MUST thing for commercial projects. Thanks LM Home bug.zip (Size: 1.13 MB / Downloads: 5)

Hi, We have two issues with the LM Home app. Short video attached (9 s). 1. Settings screen does not stay open — auto-redirects to Cloud/local page On an LM Home installation where settings have already been entered (cloud info entered, or an LM added, or only partially configured), we cannot change anything afterwards. This is not about first setup — it is about modifying an existing setup. Steps to reproduce (see video): Long-press the LM Home icon → tap Settings . The settings menu appears (Add LM automatically / Add LM manually / Remove LM / Clear credentials / Clear configuration). Within about one second, the app shows "Connecting to LM cloud" and jumps to the LogicMachine Cloud login page on its own — before we can tap anything. Expected behaviour: once the Settings screen is open, the app should not auto-redirect to Cloud or to the local page in any way until the user leaves the Settings screen themselves. 2. Feature request: "Local only" option in Settings Please add a checkbox in Settings: "Local only" . When it is selected: The app should not ask about Cloud at all. If the local LM is reachable → open the page bound to the user account. If the local LM is not reachable → show a message on the page such as "You are currently not on the local network" . Local only is a MUST thing for commercial projects. Thanks LM Home bug.zip (Size: 1.13 MB / Downloads: 5)

Hi We have 3 LM which control the light in a park. The 3 LM's may not get online, so they can't communicate in any way. For sunset and sunrise switching it feels like it's drifting, making the switch-on and -off insimultanious. We have set the long- and latitude on each LM for out exact location. How do we make sure it switches on at the same time in the best way? I did realize some of the LMs had drifted in it's time, so I also adapted the time from my Windows to all 3 LMs, but the problem persists.. Thanks in advance.

Hi We have 3 LM which control the light in a park. The 3 LM's may not get online, so they can't communicate in any way. For sunset and sunrise switching it feels like it's drifting, making the switch-on and -off insimultanious. We have set the long- and latitude on each LM for out exact location. How do we make sure it switches on at the same time in the best way? I did realize some of the LMs had drifted in it's time, so I also adapted the time from my Windows to all 3 LMs, but the problem persists.. Thanks in advance.

I have a SpaceLYnk with an error that indicates a hardware issue. See attached screenshot. gateway path unavailable.png (Size: 882.01 KB / Downloads: 15) Is the solution to replace the SpaceLYnk?

I have a SpaceLYnk with an error that indicates a hardware issue. See attached screenshot. gateway path unavailable.png (Size: 882.01 KB / Downloads: 15) Is the solution to replace the SpaceLYnk?

Hello, has anyone integrated this component?

Hello, has anyone integrated this component?