- This topic has 27 replies, 10 voices, and was last updated 2 years, 8 months ago by
.
-
Posts
-
Weird, I am on 1.4 and I dont seem to have that option? Is this a standard vs paid thing?
I’m facing the same issue with WMS 2.0 (Standard on-prem) and ThinOS 9.0.
Since I cannot use ini-files with ThinOS 9 anymore I don’t know how to solve this. Although I’m not really sure MQTT is the problem. The devices register and check-in correctly with WMS after each reboot. However, changes made in WMS (like query, change hostname) are ignored. Plus, the devices do not send heart-beats.
When looking into the “Central Configuration” of a ThinClient, WMS shows the following settings:
WMS server: https://wms.example.com:443
MQTT server: tcp://WMS01:1883 (greyed out, cannot be modified)
Using the new Admin Policy Tool on the client didn’t work either. That ended up with the default MQTT server (us1-pns.wysemanagementsuite.com)…
Any way around that?
With the free version you have to edit this directly in the MongoDB. I used following url as a guideline:
You can do the same with the following attributes to set the right url:
Stratusapp.server.url
Stratus.external.mqtt.url
Memcached. Servers
Mqtt.server.urlThe Mqtt ones are the ones you have to change.
Thanks a lot XanDaph!
I successfully edited the MQTT entries and the client now shows:
WMS server: https://wms.example.com:443
MQTT server: tcp://wms.example.com:1883
The eventlog also shows “Connected to MQTT broker”. However, commands like restart or change hostname still don’t work…
Update:
Restart commands do work, though they are not pushed instantly to the device. I changed the time for the devices to send a heart-beat to 5 minutes.
So, if I send a restart command via WMS, the device does nothing until it sends a heart-beat after 5 mins. It restarts right after that check-in. That does not really seem like “push-action” (more like “pull”, haha).
Also: changing the hostname still won’t work.
That clearly indicates that MQTT is still not working correctly for you.
Have you IP6 running on the WMS server? Can you disable?CG
You’re right, MQTT wasn’t working correctly. I checked the stratus.log. Since I edited the MQTT entries in the MongoDB, the wms server couldn’t resolve the external url. I added an entry to the hosts file and that was it. Stratus.log doesn’t show new errors.
Restarting devices does work now instantly, renaming still does not.
WMS shows:
Admin initiated Change Host Name - Test01 on WTxxxxxxxxx at 04/27/20 10:36:37 AM (Status: Successful )The client shows:
wms: received "Change Host Name" commandThe host name remains the same, though.
Perfect.
The renaming issue has a different reason.
Open your policy and got to „General Settings“. You will find the parameter „Terminalname“. Enter $TN there.CG
Tried that. Since I’m using ThinOS 9 I’m guessing I have to use System Settings -> Device Settings -> Terminal Name.
I entered $TN, tried to change the host name and now the host name of the device literally is “$TN”.You do not need that with ThinOS 9 and WMS 2.0, as 2.0 in opposite to 1.4 only pushes parameters that have been actively configured.
Therefore, remove $TNCG
Hm, that’s odd. That’s how it was before.
I removed $TN again and now it works! Thanks a lot!
Just in case someone with ThinOS 9.1 and WMS 3.X on-prem comes across this thread, they added two more values to the db that need to be changed for external MQTT.
stratus.external.secure.mqtt.url
stratus.external.preferred.mqtt.urlThanks to @XanDaph for pointing me on the right track!
- You must be logged in to reply to this topic.