I had to redo my Leader Pioreactor and set-up the wifi (local access point) as with the one before. The existing workers do connect to the wifi and get recognized by the watchdog. Adding them to the inventory also works, but they never show up as online. If the identify button on one of the added pioreactors is pressed the according pop-up in the web-ui shows up and the according messages in the mqtt log on the leader (pio mqtt) can be observed. I am really confused on what is going on. Best, Kai
Hey Cameron, no a browser hard refresh sadly did not help. I can not start actions like stirring for example. If I press the button on the WebUI I do not see any corresponding entries in the MQTT log. For the Browser Console I will quickly check if there is anything…
Browser console also does not show any errors, what is shown is a log entry from MQTTContext.js:111 that it “connected to MQTT broker for global” and “connected to MQTT broker for pioreactor”.
Can you tell me what software versions you Pioreactors have (on the Inventory page, or sshing in and running pio version)? Specifically, what the leader version is vs the workers?
Yea you definetly want to update the workers. Fastest way is to rewrite the worker images, or if they access to the internet, use pio update app. Otherwise, you can upload the release_xxx.zip files from prerelease:false · Releases · Pioreactor/pioreactor · GitHub and run
I updated all workers to 24.10.29 but still have the same problem with the same symptoms. During the Update I could also follow along in the log on the WebUI, so there is definitely Data flowing between workers and leader, just the control from the WebUI (Identify, Stirring etc ) and the Status Overview of the workers in the WebUI (Online, Version Data, IP, …) are not working.
I powercycled the cluster (leader and workers) after the update. I tried to start stirring on worker01 but got an error exclaiming that the worker is not assigned to an experiment.
Assigning the worker through the UI works (in the UI) but does not actually assign the worker. The inventory page does not show any information regarding the worker (Online Status, IP, Software Version,… is all blank)
I thought so too at first but the logs in the WebUI and the ident pop-up (also WebUI) prove that the WebUI and the workers have access to the MQTT Topic, right? The communication from the worker side I can also see in the MQTT log on the leader. Could it be that the WebUI has somehow only read but no write access to the MQTT Thread?
When I curl the api from the worker I get the correct experiment assignment back, trying to run “pio run stirring” on the worker nevertheless leads to an error for not being assigned to an experiment.
