Fórum LogicMachine Forum

Hello! Here is PRISME, an energy management app for LogicMachine. It reads the hourly spot price, the weather forecast and your own meters, and decides from them when heating, hot water and the EV charger should run: 1.) Load control on price, lowers setpoints or sheds on expensive hours, boosts on cheap ones 2.) Peak protection, sheds load before the hourly average crosses your threshold, and keeps you off the next grid tariff step 3.) EV charging, picks the cheapest hours before your deadline, backs off when the house draws hard, can prefer hours with expected sun 4.) Solar model, learns your installation's clear-sky curve and adjusts for season and cloud 5.) Reports and an event log, every decision with its reason and the change it made, all exportable to a spreadsheet Price zones for Norway, Sweden, Denmark and Finland. More price zones can be added, just ask Interface in English and Norwegian. **This is a beta.** It's been testet in one house, mine. Zaptec, Schneider EVlink Pro AC and the Victron integration have never been connected to real hardware; Easee is well tested. Please read the attached README before pointing it at anything you care about. It covers the requirements, the limitations and what leaves your house. You can see the whole app before wiring up a single address: **Help → Getting started → Show example data** fills every page with a fictional house, entirely in your browser. Please use this thread for questions, suggestions or wishes. I would especially

Hello I need 3 users to access the scada-main page, they need to edit knx objects for managing a building remotely. 1.png (Size: 2.25 KB / Downloads: 25) I don't want all of them to use the admin account for security reasons, but i haven't found how a new user can access this page. Can you help me ? Thanks

Hello, I need to use a dummy module as a placeholder in a project. I saw that Schneider makes one specifically for SpaceLogic—can I use that? Are there universal ones available? Does LogicMachine have a specific one for this purpose? Thanks.

Hi Guys, Can I use a long press to trigger a repeating send action as long as I hold down the button? (without logic, but using JavaScript) KR, Alberto

Good morning. What is a good LTE modem to use with Wiser for KNX that is trouble-free and easy to configure? Tank's

Hi Guys, I have a problem with remote VISU and the CSS. In local I see the correct CSS (I want red) but in remote is the deafult. Screenshot 2026-09-15 154321.png (Size: 214.16 KB / Downloads: 6) Screenshot 2026-09-15 154332.png (Size: 92.02 KB / Downloads: 6) Can you help me ? BR, Alberto

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, 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

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