LM 2024.02 release candidate firmware is ready for testing.
Changes from 2024.01 beta
- Fixed compatibility issue with old Logic Machine mobile app
- Scripting editor - add event script group address / tag to editor title
- CANx-DALI - fix DT8 discovery on certain DALI2 ballasts
- Visualization - fix rare bug when object data type is changed
Known issues
- Homekit application must be updated to the latest version via LM app store after the firmware upgrade.
- BACnet client (scripting) direct connection mode does not work.
22.02.2024, 08:47 (This post was last modified: 22.02.2024, 08:48 by vuphong0307.)
Giải quyết tất cả,
Giúp mình trường hợp này nhé:
Tôi có LM5Rio (phiên bản Logicmachine5 Reactor IO) bị thẻ nhớ lỗi. Tôi đang cài đặt lại thẻ nhớ mới. Nhưng gặp vấn đề về firmware trên web thì phiên bản này không còn nữa. Ai có bản cũ thì cho mình xin với.
2024 release for old CPU (imx28) will be published when a stable version is ready. Can't say whether any more updates are planned because the device is in the EOL status.
We've just found a problem testing this firmware version. Our machines are connected using OpenVPN client, flawlessly. After firmware upgrade we get this status in openvpn client: Tunnel status: unknown / no connection
In status log maybe problem can be related to this lines:
TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network
TLS Error: TLS handshake failed
Our server is an openvpn router from mikrotik, dinamic IP. We just updated two machines, and same problem arises in everyone. I've tried to change configuration file, server configuration and checked server logs, but I can't find anything usefull.
Our client configuration is always the same:
client
dev tun
proto udp
remote "our server"
port 1175
nobind
persist-key
persist-tun
tls-client
remote-cert-tls server
verb 4
mute 10
cipher AES-256-CBC
auth SHA1
auth-user-pass
auth-nocache
I had similar OpenVPN problem after updating to 2024 FW
VPN server is Asus 4G router. I have quite many LM-s connected with Asus but all are using 2023 FW. After updating FW to 2024.01 and 2024.02 got this error:
Code:
12345678
Tunnelstatus: unknown / noconnection2024-02-1813:45:31Exitingduetofatalerror2024-02-1813:45:31Cannotloadinlinecertificatefile2024-02-1813:45:31OpenSSL: error:0A00018E:SSLroutines::camdtooweak:
2024-02-1813:45:31libraryversions: OpenSSL3.0.1224Oct2023, LZO2.102024-02-1813:45:31OpenVPN2.6.6arm-openwrt-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH/PKTINFO] [AEAD]
2024-02-1813:45:31DEPRECATEDOPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.2024-02-1813:45:31WARNING: Compressionforreceivingenabled.Compressionhasbeenusedinthepasttobreak
Asus is on latest FW.
Moved to Zerotier with these few latest FW LM-s but would be good to know how to fix this problem...
VPN configuration is same for all devices
indirizzo = event.dst--broker = "demo.thingsboard.io"broker = "185.5.xxx.xxx"port = 1883token = "xxxxxxxxxxxxxxxxxxxxxxxx"topic = "v1/devices/me/telemetry"value = event.getvalue()
-- Se value è un booleano, converte "true" in 1 e "false" in 0ifvalue == "true"thenvalue = 1elseifvalue == "false"thenvalue = 0else-- Se value è un numero float, riduce i decimali a 1numero = tonumber(value)
ifnumero ~= nilandnumero % 1 ~= 0thenvalue = string.format("%.1f", numero)
end-- Se value è un numero intero, non fare nullaend-- Ora 'value' contiene il valore modificato secondo le specificheold_value = storage.get(indirizzo)
value = tostring(value)
--log (value, old_value)ifvalue == old_valuethen--log("return")returnendstorage.set(indirizzo, value)
dispositivo = grp.alias(indirizzo).." ("..indirizzo..")"payload = '{"'..dispositivo..' - valore":' .. value .. '}'--payload = "{temperatura:"..value.."}"--log (payload)mqtt = require("mosquitto")
client = mqtt.new()
client.ON_CONNECT = function(status, rc, msg)
ifstatusthen--log("mqtt connected "..event.dst.." "..payload)client:publish(topic, tostring(payload))
elselog("mqtt connect failed " .. tostring(msg))
client:disconnect()
endendclient.ON_PUBLISH = function()
client:disconnect()
end-- client:login_set(username, password)client:login_set(token, nil)
status, rc, msg = client:connect(broker, port)
ifstatusthenclient:loop_forever()
elselog('connect failed: ' .. tostring(msg))
end
I taken it from LM docs, as suggested...
right now I can ping only in Zerotier and the reply is like that:
Esecuzione di Ping 10.147.20.232 con 32 byte di dati:
Risposta da 10.147.20.232: byte=32 durata=36ms TTL=64
Risposta da 10.147.20.232: byte=32 durata=36ms TTL=64
Risposta da 10.147.20.232: byte=32 durata=32ms TTL=64
Risposta da 10.147.20.232: byte=32 durata=32ms TTL=64
Statistiche Ping per 10.147.20.232:
Pacchetti: Trasmessi = 4, Ricevuti = 4,
Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 32ms, Massimo = 36ms, Medio = 34ms
since I updated to the latest release, I have noticed a strong slowdown in the opening of browser pages (in particular Firefox, google less):
if, for example, I want to edit a script, sometimes it takes a whole minute before I see the editor page.
What could be the reason for this?
Peppe
P.S. the cpu load is always low.
Exactly the same behavior for me,
Firefox has become unusable while with Chrome you can still do something.
I noticed this behavior, I don't know if it helps:
Using Chrome with LM5 connected via ZeroTier and 4G router, if you open the Modbus tab for the first time and then open the Object Mapping view (I have around 250 objects for each RTU device) with the fw 20230607 you don't see any delay while with the new 20240219 the LM freezes for 20/30 sec, the CPU/IO value goes into the red area and if you have another tab open in the browser with the System Load, that freezes too.
Have you already discovered something about this strange behavior?
