SENSBLUE ATLAS/MQTT Actors - Revision history

WikiManagement at 16:54, 7 September 2026

2026-09-07T16:54:28Z

@@ Line 5,490: / Line 5,490: @@
 ===== Configure CANopen Nodes =====
 Req-Topic: <code>canopenRM8007/config/in</code>
 Stores CANopen defaults and logical node configuration inside the actor.<syntaxhighlight lang="json" line="1">
@@ Line 5,660: / Line 5,658: @@
 * As an alternative to the <code>nodes</code> object, any other key of <code>taskParams</code> whose value is an object containing <code>node_id</code> is also stored as a logical node. These two requests are equivalent:
 <syntaxhighlight lang="json">
 { "task": { "alias": "CONFIG_CANOPEN", "taskParams": { "nodes": { "motor_1": { "node_id": 5 } } } } }
-{ "task": { "alias": "CONFIG_CANOPEN", "taskParams": { "motor_1": { "node_id": 5 } } } }
+  "task": {
 </syntaxhighlight>

WikiManagement at 15:27, 3 September 2026

2026-09-03T15:27:46Z

← Older revision		Revision as of 15:27, 3 September 2026
Line 9:		Line 9:
	user: <not needed>		user: <not needed>

	login <not needed>		login: <not needed>

	=== <big>1. Relay Outputs Actor</big> ===		=== <big>1. Relay Outputs Actor</big> ===

WikiManagement at 15:27, 3 September 2026

2026-09-03T15:27:21Z

← Older revision		Revision as of 15:27, 3 September 2026
Line 7:		Line 7:
	Eth1: '''93.48.86.253'''		Eth1: '''93.48.86.253'''

	user: < not needed>		user: <not needed>

	login <not needed>		login <not needed>

WikiManagement at 15:26, 3 September 2026

2026-09-03T15:26:26Z

← Older revision		Revision as of 15:26, 3 September 2026
Line 3,183:		Line 3,183:
	\|Ordered list of screens		\|Ordered list of screens
	\|-		\|-
	\|~~Start Index~~		\|startIndex
	\|Initial active screen (optional, default = 0)		\|Initial active screen (optional, default = 0)
	\|}		\|}

WikiManagement at 15:14, 3 September 2026

2026-09-03T15:14:57Z

← Older revision		Revision as of 15:14, 3 September 2026
Line 3,115:		Line 3,115:

	==== 5.3 User interaction through MQTT ====		==== 5.3 User interaction through MQTT ====
	Enabling interaction with the carousel using the topic tft/runtime/in . Actions available will be public to the user.		Enabling interaction with the carousel using the topic tft/runtime/in.

			Actions available will be public to the user.

	'''Runtime commands'''		'''Runtime commands'''

WikiManagement at 15:09, 3 September 2026

2026-09-03T15:09:45Z

← Older revision		Revision as of 15:09, 3 September 2026
Line 3,077:		Line 3,077:
	'''Network Information Screen'''		'''Network Information Screen'''

	* ~~Display~~ an interface with information about the networks of the device		* Displays an interface with information about the networks of the device
	* Updated on load		* Updated on load
	* No user interaction required		* No user interaction required

WikiManagement at 15:05, 3 September 2026

2026-09-03T15:05:22Z

← Older revision		Revision as of 15:05, 3 September 2026
Line 9,198:		Line 9,198:
	On an unexpected exception, every handler returns <code>{ "success": false, "error": "<exception text>" }</code> instead of its usual fields.		On an unexpected exception, every handler returns <code>{ "success": false, "error": "<exception text>" }</code> instead of its usual fields.

	==== 15.6 Interpreting the Results ====		==== 15.5 Interpreting the Results ====

	===== a) <code>success: false</code> on SMS_RECEIVED =====		===== a) <code>success: false</code> on SMS_RECEIVED =====
Line 9,249:		Line 9,249:
	<code>set_ssh</code> runs <code>systemctl start\|stop</code> on both <code>ssh.socket</code> and <code>ssh.service</code>, confirmed on-device via <code>systemctl list-units \| grep -i ssh</code>. On this image, <code>ssh.service</code> is <code>TriggeredBy: ssh.socket</code> and both are enabled independently — stopping only <code>ssh.service</code> leaves <code>ssh.socket</code> listening on :22, and it socket-activates a fresh <code>sshd</code> on the next connection attempt, so SSH would stay reachable despite <code>SSH:Off</code> reporting success. Some distros name the service unit <code>sshd</code> instead; reconfirm both unit names if targeting a different image.		<code>set_ssh</code> runs <code>systemctl start\|stop</code> on both <code>ssh.socket</code> and <code>ssh.service</code>, confirmed on-device via <code>systemctl list-units \| grep -i ssh</code>. On this image, <code>ssh.service</code> is <code>TriggeredBy: ssh.socket</code> and both are enabled independently — stopping only <code>ssh.service</code> leaves <code>ssh.socket</code> listening on :22, and it socket-activates a fresh <code>sshd</code> on the next connection attempt, so SSH would stay reachable despite <code>SSH:Off</code> reporting success. Some distros name the service unit <code>sshd</code> instead; reconfirm both unit names if targeting a different image.

	==== 15.7 Boot Behaviour ====		==== 15.6 Boot Behaviour ====
	On every boot, the actor:		On every boot, the actor:

Line 9,257:		Line 9,257:
	There is no periodic check — all processing after boot is triggered by modem D-Bus signals.		There is no periodic check — all processing after boot is triggered by modem D-Bus signals.

	==== 15.8 Known Limitations ====		==== 15.7 Known Limitations ====
	Behaviour that is easy to rely on by mistake, listed so integrations do not.		Behaviour that is easy to rely on by mistake, listed so integrations do not.
	{\| class="wikitable"		{\| class="wikitable"
Line 9,309:		Line 9,309:
	\|}		\|}

	==== 15.9 Notes ====		==== 15.8 Notes ====
	* The SMS Actor keeps no persistent state across restarts (no EEPROM, file, or database). In-memory bookkeeping only tracks SMS already seen/being processed, to avoid double-handling from overlapping D-Bus signals.		* The SMS Actor keeps no persistent state across restarts (no EEPROM, file, or database). In-memory bookkeeping only tracks SMS already seen/being processed, to avoid double-handling from overlapping D-Bus signals.
	* Message deletion after processing is enabled by default; this can be disabled via configuration if a full SMS audit trail is needed on the modem/SIM itself (subject to SIM storage limits).		* Message deletion after processing is enabled by default; this can be disabled via configuration if a full SMS audit trail is needed on the modem/SIM itself (subject to SIM storage limits).
	* There is currently no sender allow-list or authentication on inbound SMS commands — any device holding the SIM number can trigger any of the commands above by sending the matching text.		* There is currently no sender allow-list or authentication on inbound SMS commands — any device holding the SIM number can trigger any of the commands above by sending the matching text.
	* <code>set_digital_output</code>/<code>set_relay</code> are the only commands that depend on another actor process (<code>busi2c-3</code>/<code>busi2c-1</code>) being up and reachable over MQTT; all other commands run entirely within the SMS actor's own process.		* <code>set_digital_output</code>/<code>set_relay</code> are the only commands that depend on another actor process (<code>busi2c-3</code>/<code>busi2c-1</code>) being up and reachable over MQTT; all other commands run entirely within the SMS actor's own process.

WikiManagement at 15:04, 3 September 2026

2026-09-03T15:04:01Z

← Older revision		Revision as of 15:04, 3 September 2026
Line 4,139:		Line 4,139:
	After STOP, the buzzer is forced to OFF.		After STOP, the buzzer is forced to OFF.

	=== 12. Power Monitor ~~actor~~ ===		=== 12. Power Monitor Actor ===

	==== 12.1 Overview ====		==== 12.1 Overview ====

WikiManagement at 15:02, 3 September 2026

2026-09-03T15:02:17Z

← Older revision		Revision as of 15:02, 3 September 2026
Line 8,612:		Line 8,612:
	\|}		\|}

	=== 15 SMS Actor ===		=== 15. SMS Actor ===

	==== 15.1 Overview ====		==== 15.1 Overview ====

WikiManagement at 14:58, 3 September 2026

2026-09-03T14:58:19Z

← Older revision		Revision as of 14:58, 3 September 2026
Line 249:		Line 249:
	[[File:RTCActor Overview.svg\|center\|frameless\|903x903px]]		[[File:RTCActor Overview.svg\|center\|frameless\|903x903px]]

	=== <big>3 System Health Actor</big> ===		=== <big>3. System Health Actor</big> ===

	==== 3.1 App Interfacing ====		==== 3.1 App Interfacing ====