Local Status Panel

[svencool]

Seems like when I launch the app it sometimes finds the classic and other times it doesn't. I've reset the router no luck any ideas? I have it set to auto detect also....

Mike

[zoneblue]

What firmware are you using? Anything recent should be pretty good.

What ive always done, and had good results with is giving the classic a static IP, turning off auto detect on the local app and adding the classics IP in to the local app.

[svencool]

I updated the firmware to 2079 a few days back. Seem to be working fine and I was able to use the new cloud based program as well. Its back to working again I have it setup as DHCP and Web Access Enabled. What are the advantages to using a static address?

[zoneblue]

For anything that is a permanent fixture on ones LAN, static IP addresses remove a step in the connection process. With a static address it will always be where you left it;) Making it easy to find. However there is one downside. You have to keep track of your addressing. You dont want to give two devices the same IP. What i do is have .1 the gateway, .2-.20 reserved for static addresses, and configure the router to serve DHCP address from .100-.200 for the laptops. That keeps a little order to things.

[svencool]

Thanks for explaining that I think I'm gonna go that way with my connection. Can I ask anyone what is FET and PCB under the temperature section on the status page? Can I change them so they read in F instead of C?

[zoneblue]

FET temp is the classic's sensor on or near the mosfets heatsink (the mosfets do most of the heavy lifting.). The PCB temp is the sensor on the control board, which is more of a overall chasis temp. The two are probably correlated much of the time.

As for Farenheight, interestingly, no it cant be set to read that.