This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm that you accept these cookies being set.

[OLD] LogicMachine firmware 2024.02
#1
2024.04 RC3 https://forum.logicmachine.net/showthread.php?tid=5393



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.



New LM Home application

More info here: https://forum.logicmachine.net/showthread.php?tid=5220



KNX Data Secure

Video tutorial: https://forum.logicmachine.net/showthrea...5#pid33915
#2
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.    
#3
For Reactor IO v1 use LM5 Lite + Ext (4 or 6 DIN units) firmware.
#4
(22.02.2024, 08:51)admin Wrote: For Reactor IO v1 use LM5 Lite + Ext (4 or 6 DIN units) firmware.

Thank you so much.
#5
Are we at the Point where imx28 cpu‘s are not longer supported ?
#6
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.
#7
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

Can it be a bug? Thank you
#8
The only difference is that 2024 firmware has a newer OpenVPN package. Have you tried upgrading your router to the latest version?
#9
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:
Tunnel status: unknown / no connection
2024-02-18 13:45:31 Exiting due to fatal error
2024-02-18 13:45:31 Cannot load inline certificate file
2024-02-18 13:45:31 OpenSSL: error:0A00018E:SSL routines::ca md too weak:
2024-02-18 13:45:31 library versions: OpenSSL 3.0.12 24 Oct 2023, LZO 2.10
2024-02-18 13:45:31 OpenVPN 2.6.6 arm-openwrt-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH/PKTINFO] [AEAD]
2024-02-18 13:45:31 DEPRECATED OPTION: --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-18 13:45:31 WARNING: Compression for receiving enabled. Compression has been used in the past to break

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
#10
Try this: https://superuser.com/questions/1737052/...d-too-weak
#11
HI,

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.
#12
Try pinging LM. Do you get normal replies or some replies are missing? The time should be around 1ms or 2ms if PC and LM on the same network.

Do you have any .lp scripts that are accessed by remote devices? Incorrectly written .lp script can block the web server.
#13
I am running a script to send telemetry to thingsboard with mosquito mqtt connection:

Code:
indirizzo = event.dst
--broker = "demo.thingsboard.io"
broker = "185.5.xxx.xxx"
port = 1883
token = "xxxxxxxxxxxxxxxxxxxxxxxx"
topic = "v1/devices/me/telemetry"
value = event.getvalue()
-- Se value è un booleano, converte "true" in 1 e "false" in 0
if value == "true" then
    value = 1
elseif value == "false" then
    value = 0
else
    -- Se value è un numero float, riduce i decimali a 1
    numero = tonumber(value)
    if numero ~= nil and numero % 1 ~= 0 then
        value = string.format("%.1f", numero)
    end
    -- Se value è un numero intero, non fare nulla
end
-- Ora 'value' contiene il valore modificato secondo le specifiche
old_value = storage.get(indirizzo)
value = tostring(value)
--log (value, old_value)
if value == old_value then
 
  --log("return")
 
  return
 
end
storage.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)
  if status then
    --log("mqtt connected "..event.dst.." "..payload)
    client:publish(topic, tostring(payload))
  else
    log("mqtt connect failed " .. tostring(msg))
    client:disconnect()
  end
end

client.ON_PUBLISH = function()
  client:disconnect()
end

-- client:login_set(username, password)
client:login_set(token, nil)
status, rc, msg = client:connect(broker, port)

if status then
  client:loop_forever()
else
  log('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
#14
Can you provide access via ZeroTier? Please send network ID and LM admin password via PM.
#15
(04.04.2024, 09:46)admin Wrote: Can you provide access via ZeroTier? Please send network ID and LM admin password via PM.

Il will send you the static IP:port to access and admin password via PM.

But, please, don't reboot the LM or something because it is currently working and right now we are doing some tests on HVCA systems
#16
(04.04.2024, 08:32)gdimaria Wrote: HI,

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? 

Can we do something to help you?

BR
Marcello
#17
Your case is different as your LM is overloaded where previous one not at all. Are you sure that locally this is not the same?
------------------------------
Ctrl+F5
#18
Can you provide access via ZeroTier? Please send network ID and LM IP / admin password via PM.
#19
Hi Daniel,
It seems to me a very similar situation but to be sure I had already written a PM to gdimaria to speak with him.

Now I'll do some tests locally then we'll organize to connect you to this machine.
#20
(26.03.2024, 17:37)admin Wrote: Try this: https://superuser.com/questions/1737052/...d-too-weak

Finally get old openvpn client configuration to work just by adding this line:

compat-mode 2.4.0

Hope it helps someone else


Forum Jump: