Yes, AM and Remote Agent versions are the same. I don't see temperatures on the GPU tab, I used "Map to system monitoring" button --> "Display system monitoring data in the GPU tab", but they still don't appear in the GPU tab or status tab.
Status tab says "Interface Offline" and "Mining" and I can use start/stop/reboot/all functions. I am using "Managed Hosts" mode. As I said before this happened just after new update, when both AM and Remote Agents where updated, if only AM is updated and Remote Agent is previous version, it works fine. I guess newer version cannot pull the info from the miner, but I haven't touched mining software at all.
Can you please try to stop a single Managed Miner, then start it again. Any change?
Already tried many times, but no changes. Everything is the same for all servers, not showing hashrate/income, "Interface Offline" and "
Mining".
Maybe it is not even trying to pull info from the miner software? Is there an option to disable direct Afterburner control and switch back to using miner software for temperatures like before? I tried to use different versions of Claymore too, no changes.
I have further investigated this issue and found an obvious bug:
Claymore's software is listening to port 3333 by default and AM was using the same port for pulling miner info in the previous versions, but now it looks like AM is trying to connect to Claymore through port 4028 and as I remember it is default port of CGminer.
After setting port 4028 to Claymore, everything works as it should!
I hope this information will help you to fix it and them who are using Claymore with Awesome miner.
Good that you found this. This behavior was actually changed in Awesome Miner 3.0.
Awesome Miner has always set the port dynamically for most mining software, except the Claymore miners. If you start multiple miners on the same computers they were always assigned a unique port like 4028, 4029, 4030 and so on.
For Claymore it used to be 3333 all the time, which didn't work when you were running multiple Claymore miners on the same computer. For that reason I changed the Claymore miner port to follow the same pattern as for all other miners controlled by Awesome Miner - to start on port 4028 and than increase the number to make it unique.
If you run version 3.X of both Awesome Miner and the Remote Agent, it should work as long as the mining process also was started with a recent version that set the port to 4028+.