There's a new home for Articles. Find Articles on Our Product Support Page.
We're starting with soti connect (cloud) and planning to add Zebra printers by MQTT. The networkteam wanted the exact ports which we're using. We're thinking about 433 (https) 8883 (MQTTS) 4646/4650 (filestore) wich are inbound, outbound or both?
Having an issue with keeping the ZQ521 printers connecting to our SOTI Connect instance with MQTT The printer show either a "Connection State Uknown" or "Device not Reachable" This the log output from one of the ZQ521 printers, it initially connects but the connection the imediately closes for some reason [12-17-2024 18:16:10.640][Info][00010038][mqtt1] Server certificate verify ok[12-17-2024 18:16:10.675][Info][0000101B][mqtt1] Successfully connected[12-17-2024 19:59:25.092][Error][0000130A][mqtt] Network link lost[12-17-2024 19:59:25.096][Info][00010039][mqtt1] Connection closed[12-17-2024 19:59:25.098][Info][0000100F][mqtt1] Waiting 79 seconds before trying connection[12-17-2024 20:00:44.218][Info][00001006][mqtt1] Waiting for an IP address[12-17-2024 20:04:23.093][Info][00001006][mqtt1] Waiting for an IP address[12-17-2024 20:04:28.573][Info][00001006][mqtt1] Waiting for an IP address[12-17-2024 21:18:18.500][Info][00001006][mqtt1] Waiting for an IP address[12-17-2024 21:18:21.885][Info][00001006][mqtt1] Waiting for an IP address[12-17-2024 21:18:25.106][Info][00001006][mqtt1] Waiting for an IP address[12-17-2024 21:50:08.291][Info][00001006][mqtt1] Waiting for an IP address[12-17-2024 21:50:11.758][Info][00001006][mqtt1] Waiting for an IP address[12-17-2024 21:50:15.097][Info][00001006][mqtt1] Waiting for an IP address
Hello everyone, I have the following issue with Soti Connect. My individual rules are no longer executed during check-in, but only when I update the rule. The rule should be applied when the model is ZD401 and/or when the Media Sensor does not have "GAP" entered When I click on "Update" for the rule, it is executed on the printer. However, I would like the rule to be applied during every check-in(I have set the check-in to occur every hour)
Hi all, a customer wants to add and configure his CA in Connect for certificate-based Wi-Fi authentication. His Zebra ZQ630 printers are currently connected to a PSK network and a seamless transition between the current and the new network would be nice. We successfully configured the CA in MobiControl, including generating and deploying Wi-Fi certificates to devices and connecting to the new certificate-based network. Does anyone have experiences with configuring it in Connect? I guess the CA and template configuration is pretty much the same. What is the exact process of generating and deploying device-based certificates? Anything to keep in mind by configuring the configurations? Any problems to be aware of? I would appreciate any tips or experiences. Thank you in advance! Felix
Can i get a procedure to enroll honeywell or toshiba devices since there is no info about how to set up the adapter and enroll these devices in Soti connect. The only info i can find is about zebra printers.
Hello everyone, Since the last Soti Connect update (2024.2.0.8055) the automapping no longer works automatically.The "rule" itself works, if you open the rule under (Administration->Automatic Group Mappings) and click on save, the devices are moved immediately correctly.I created the rule based on a specific IP range A short explanation of how I built the rules: Device is staged, after enrollment the device is moved to a superordinate group (Devices all Companies). And from this group, the device should be moved to the respective company based on the IP range (automapping) Any ideas? Or known problems? Thanks Greetings Max
Hello, I think there are wrong requirements on the soti connect page in pulse:https://pulse.soti.net/support/soti-connect/help/?V=2024.1&T=/setup/systemreqs/systemreqs as the online help page required still dotnet 6 for Connect 2024.1:https://soti.net/soticonnect/v2024.1/en/setup/systemreqs/systemreqs.html Martin
Could you detail of SOTI connect feature
I'm trying to setup a connection between a HiveMQ broker and the MQTT protocol adapter in SoTI connect. The soti connect install is setup in the cloud. Which ports need to be opened on the server that's running the MQTT broker to establish a secure tls connection with the protocol adapter?
I am installing Connect 2024.1 and afterwards the HiveMQ MQTT Broker, but there you should select the server.pfx from Soti Connect, what is the password ? During installing Soti Connect 2024.1 you can just select a password for the RootCA and not for the MQTT certificates, as it was possible in older versions of Connect concerning the online help. What have I missed during installation?
tengo una version de prueba de soti x 30 dias y no se como agregar mis equipos a la plataforma
I'm trying to access the Soti Connect API on our cloud-hosted instance using the Resource Owner grant type as documented at Soti Connect Help: Request Access Token. Here are the steps I've taken: Add a new client ID and secret as documented at Global Settings: General --> Security Access Add a new local Soti Connect user specifically for API access Send a request to https://hostname/Connect/token I receive an error message that the password must be changed. error error_description----- -----------------access_denied {"errorCode":161,"parameter":"IsPasswordChangeRequired"} The problem is that we're using Soti Identity for authentication, and disabling that just to change a password seems excessive. I realize this may be an example of an XY problem, so if there's a better way to do this than to create a local user, I'm interested.
Hi there, the PM43c is not official certified, is it possible to get device type definition for this printer, this printer is technically the same as the PM43 the Pm45c is certified, but not able to onboard, the cloud connecter shows the printer, but discover says there is no new printer so how i can solve this? regards Andreas
How to see new devices (Zebra ZT 231) in SOTI ?
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points
Highly experienced members with valuable inputs. Should have more than 700 points
Beginners taking the initiative. Should have more than 500 points