4.3.8 LTS - False "Cloud Component Not Installed" Error / RMM Issue

[KYTECHNGAMING]

Hello,

I recently downgraded/updated one of my networks to the KeeneticOS 4.3.8 LTS release.

After the transition, I started receiving an error stating that RMM (Remote Monitoring and Management) / Cloud Component is not installed.

However, this component is definitely installed on my controller, and my Keenetic mobile app is working perfectly fine without any issues.

show version

{
	"release": "4.03.C.8.0-0",
	"sandbox": "lts-4.3",
	"title": "4.3.8",
	"arch": "mips",
	"ndm": {
		"exact": "0-2f853e0",
		"cdate": "8 Jun 2026"
	},
	"bsp": {
		"exact": "0-65b295dc99",
		"cdate": "8 Jun 2026"
	},
	"ndw": {
		"features": "wifi_button,wifi5ghz,usb_3,usb_3_first,dsl,adsl,led_control,vht2ghz,bf2ghz,mimo5ghz,atf2ghz,atf5ghz,dual_image,wifi_ft,wpa3,link_agg,hwnat,cable_diag",
		"components": "acl,base,chilli,cloudcontrol,corewireless,dhcpd,dns-filter,dns-https,exfat,ext,fat,hfsplus,ip6,lang-en,lang-tr,mdns,miniupnpd,mws,nathelper-esp,nathelper-ftp,nathelper-h323,nathelper-pptp,nathelper-rtsp,nathelper-sip,ndns,ntce,ntfs,opkg,opkg-kmod-fs,opkg-kmod-netfilter,opkg-kmod-netfilter-addons,opkg-kmod-tc,pingcheck,ppe,pppoe,ssh,storage,trafficcontrol,tsmb,usb,usblte,usbmodem,usbnet,usbnet-extra,usbqmi,wireguard"
	},
	"ndw4": {
		"version": "4.3.C.8.0"
	},
	"manufacturer": "Keenetic Ltd.",
	"vendor": "Keenetic",
	"series": "KN",
	"model": "Peak DSL (KN-2510)",
	"hw_version": "10258000",
	"hw_type": "router",
	"hw_id": "KN-2510",
	"device": "Peak DSL",
	"region": "TR",
	"description": "- Master 05 - Peak DSL (KN-2510)",
	"prompt": "(config)"
}

According to the RMM changelogs, the minimum requirement is KeeneticOS 4.1.0, so this shouldn't be happening on 4.3.8 LTS.

Quote

 

2026.01.22

System requirements change

Keenetic RMM now requires the controller to run OS version 4.1.0 or higher. Raising the minimum version helps ensure security, stability, and high performance.

 

I wanted to report this bug to the community and the development team. @Daria @Julia Rybakova

Best regards,

Edited 18 hours ago by KYTECHNGAMING

[eralde]

Hello @KYTECHNGAMING

Thank you for reporting the issue!

To resolve it you need to add or remove any component to your device's firmware.
Once the device gets a new 4.3.8 LTS firmware its connection to the RMM will be restored 🙏

[KYTECHNGAMING]

Update:

I also noticed the following error line repeatedly appearing in my system logs:

Core::Scgi::Tools: ignored floating point value "channel".

I suspect this log is directly related to the cloud component mismatch. It seems like a parsing/data-type error within the SCGI (Simple Common Gateway Interface) protocol.

The system appears to be expecting a floating-point (numerical) value for a Wi-Fi or telemetry channel, but instead, it encounters the string value "channel". As a result, the backend ignores it.

This type-mismatch bug between the KeeneticOS 4.3.8 LTS core API and the Cloud/RMM components might be the root cause of the false "missing component" error in the dashboard.

Hopefully, this log snippet helps the developers pin it down quickly!

[KYTECHNGAMING]

28 minutes ago, eralde said:

Hello @KYTECHNGAMING

Thank you for reporting the issue!

To resolve it you need to add or remove any component to your device's firmware.
Once the device gets a new 4.3.8 LTS firmware its connection to the RMM will be restored 🙏

Hello @eralde
 

Thank you for the quick support and the explanation! 

I followed your advice and removed an unused component. As you stated, this triggered a clean firmware profile rebuild. Right after the update, the SCGI parsing errors disappeared from my logs, and the controller successfully restored its connection to the RMM dashboard. It is now completely Online.

For anyone else encountering this false "Cloud component missing" error on 4.3.8 LTS: Simply add or remove any component in your system settings to force a firmware sync. It resolves the configuration mismatch instantly.

Additionally, I noticed a minor frontend/UI bug on the main dashboard under the System Update section. The update channel string seems to have a broken variable interpolation. It literally displays as:

"Update Channel: LTS {{version}}" 

It looks like the template variable is not being parsed correctly and shows the raw bracket notation on the Web UI. Just wanted to pass this on to the frontend team for a quick fix in the next build!

Thanks again for the great support 🙏