1) My unit’s display shows TUE even though the date & time are accurate and when I log into the device remotely it shows the proper day as FRI.
I’ve never seen this happening. Since the LCD and the webpage both pulls time value from the controller’s internal variable, I can’t thinking of any reason that would cause what you described. Is it still the case or it’s now in sync?
2) I can’t manually adjust my PORT # from the default 80 to what I currently have forwarded on my router for this device.
The PORT# is never adjustable on the controller (i.e. using buttons) — you need to change it through the web interface (on the options page). This is due to a rather technical reason that the port number is stored in 2 bytes and all options that are editable on the controller are single bytes.
3) The MAC is a different address than it was before the firmware update. This has lead to me needing to make correction within my router’s Static DHCP settings so that it assigns the same IP and thus proper port forwarding to be visible outside of my network.
Indeed the MAC has been changed (it’s a rather accidental change when I worked on the firmware code).
4) When the screen sleeps or goes into the dim mode none of the 3 side buttons (b1, b2 or b3) will wake it. Only a physical power down and back on with the toggle switch will wake it. To be fair, this happened only the one time after I updated the firmware and I haven’t yet had the ability to try to recreate.
It should wake up on button press. Perhaps the controller was busy doing something when you click on the buttons. If this is a reproducible issue, I can check.
5) My web access page looks completely different in that none of the buttons have colors or emblems the way they previously did with v2.0.0 so I’m not sure if this is a new change with v2.0.4 or not but I noticed as soon as I logged in that it looked much more plain.
The button images have been removed but will be added back in future firmwares. The reason they are removed is that the web interface of firmware 2.0.4 (mainly javascripts and images) can be served entirely locally from a microSD card. The factory default is to retrieve javascripts and images from the rayshobby.net server, but if needed these files can be moved to a microSD card and served on the controller itself. When this happens, it’s better to minimize web traffic by reducing the number of files. It’s pretty easy to set the remote javascripts to serve extra images and the microSD card version to not. I just haven’t got around time to make two different versions.
6) In my router’s client list it now shows the device at this IP address as OpenSprinkler-00 as opposed to what it was previously called: OpenSprinkler.
This is correct. The device ID is not appended at the end of the name because if you have multiple opensprinklers connected on the same network, you will be able to tell them apart this way.