[RC1] LogicMachine firmware 2025.08

[admin]

LM 2025.08 release candidate 1 firmware is ready for testing.

Changes from 2025.07 beta:
- Fixed KNX connection settings not working
- Updated Visu and LM cloud apps

New Visu features:
- Trend log widget
- Camera snapshot widget with local image proxy

Most notable changes from 2024.04:
- Old visualization is disabled for new installations (does not apply if upgrading from an older version or restoring a backup)
- New Visu beta app added
- Added support for new Visu cloud version
- Mosaic app removed

Old visualization and Mosaic can still be used with this firmware. No new features will be added to old visualization and Mosaic. Only critical bug fixes will be provided.

---

You can find your hardware model in the "Upgrade firmware" window:



LM5 Power devices with i.MX6 CPU
LM5 Lite (3 DIN units): image file | signature
LM5 Lite + Ext (4 or 6 DIN units): image file | signature
LM5 Reactor GM KNX: image file | signature
LM5 Reactor GM CANx: image file | signature
LM5 Reactor Dimmer KNX: image file | signature
LM5 Reactor Dimmer CANx: image file | signature
LM5 Reactor IO V2/V3: image file | signature
LM5 Reactor IO V2/V3 + LTE: image file | signature
LM5 M4 (4 DIN units): image file | signature
LM Wall (Ambient V2): image file | signature


Extra packages (i.MX6 CPU)

libmysqlclient has been replaced by libmariadb. No script changes are needed for MySQL/MariaDB connectivity.

[Gabriel88]

Hello everyone. I have just updated my LM5 with the new firmware (LM5 Lite (i.MX6)-20250813). When trying to program the KNX system with ETS5, it detects the Logic Machine interface, lets me select it, but it doesn't communicate with the system. When I try to download or read any KNX device, it fails — there's no communication. I hope I haven’t done anything wrong, but apart from setting the communication mode to "TP-UART" on the LM5, assigning a physical address, and selecting the interface in ETS5, I don't think there's anything else to do... Thanks in advance, everyone.

[Daniel]

Tested on the same ETS 5 version as well as on ETS6 and both works fine. Don't use Zerotier multicast if you don't actually use it. Did you press this RED button on top right corner?

[Gabriel88]

Tested on the same ETS 5 version as well as on ETS6 and both works fine. Don't use Zerotier multicast if you don't actually use it. Did you press this RED button on top right corner?

Yes, I saved the changes. At this point, I must be doing something wrong, but I can't figure out what. If it has already been tested and it works, then I need to understand what my problem is...

[Daniel]

Maybe some firewall, is this corporate network with managed switch?
Did you test it just before the upgrade?

[Gabriel88]

Maybe some firewall, is this corporate network with managed switch?
Did you test it just before the upgrade?

No, it's a private residence. Unfortunately, I didn’t test it before the update. I only just noticed that there’s an error; what does this KNX/TP error refer to?  I was so focused that I didn’t notice until now. What does it mean? In the end, the whole KNX system is working correctly

[Daniel]

Is KNX cable connected?

[Gabriel88]

Is KNX cable connected?

Yes, it was the first thing I checked.

[Daniel]

Bus voltage?

[Gabriel88]

Bus voltage?

29V.  The LM5 is powered through a non-PoE power supply

---

Bus voltage?

29V.  The LM5 is powered through a non-PoE power supply

While testing, I noticed that when I connect the KNX bus, the error disappears for a couple of seconds. After about ten seconds, it shows up again.

[Daniel]

Can you provide remote access? If yes send me PM.
Double check the cable next to LM.
Did you check the voltage on LM side of TP connector?

[Gabriel88]

Can you provide remote access? If yes send me PM.
Double check the cable next to LM.
Did you check the voltage on LM side of TP connector?

Of course I can, but  wait a second. I think I found the problem. It seems that the KNX connector is damaged and is not making contact with the LM5 terminal.
I’m looking for another terminal block in the van and will do some tests.

---

Can you provide remote access? If yes send me PM.
Double check the cable next to LM.
Did you check the voltage on LM side of TP connector?

Of course I can, but  wait a second. I think I found the problem. It seems that the KNX connector is damaged and is not making contact with the LM5 terminal.
I’m looking for another terminal block in the van and will do some tests.

Update: it really seems that the KNX terminal block on the LM5 was faulty. After replacing it, everything appears to be working, and I can also use the LM5 as an interface for ETS.  Conclusion: machine update is all good, the problem was on my side due to the faulty terminal block. I don’t know how to thank you enough for your advice and patience... Drinks are on me!

[savaskorkmaz]

Hi,
There is a seting called Remote diagnostics which is different then Remote Services in Services. What is this ?

[Daniel]

Remote diagnostic was there from the beginning of LogicMachine
As the name says it is for remote diagnostics, it has use only for EMBS.

[managementboy]

I can't access the System Config since I flashed the beta... get a 404 error

[Daniel]

Cache? Did you try accessing via manual url typing? http://192.168.0.10/flashsys

[PolymorphedCust]

Can you provide remote access? If yes send me PM.
Double check the cable next to LM.
Did you check the voltage on LM side of TP connector?

I have this problem as well! I JUST updated my firmware to  the newest, and while testing multicast via ZeroTier, the "ERROR" occured.

When setting KNX Connection: Multicast back to LOCAL, the KNX/TP is OK. 

I really wanna test this multicast via ZeroTier. Do you know about this problem and maybe a solution?

[Daniel]

The issue above was related to faulty KNX connector. Multicast over Zerotier may not be very reliable as multicast is sent blindly with hope that it was delivered. Much better and robust solution is MQTT, this app makes it super easy.
https://forum.logicmachine.net/showthread.php?tid=5878

[PolymorphedCust]

I will have a look at this way of communicating between our LMs... It doesn't quite fix the ERROR problem though....
I can FORCE the ERROR, simply by setting multicast to ZT.
Then I can make it alright again by switching it back to Multicast: LOCAL.

The KNX is FUNCTIONAL while LM says it has an ERROR... That said; my LM scripts works aswell...

[Daniel]

I just tried it and it works for me, LM might need bit longer time to boot, when it asks you to switch to IP, select NO and wait.