So I'm new here although I've been lurking & reading for the last couple months. I have a 150 lite that was having trouble with the Ethernet locking up every night so I updated to the beta firmware. That didn't solve the problem it ended up being an issue with DHCP on my Linksys E1000. After I changed the classic to a static IP everything has been working good for a couple weeks now.
I decided I would like to try out my midnite so I went to the ALPHA site to register & it wouldn't take my MAC address. Then when I went to the main my midnite page it let me register just fine but shows the no communication in at least two weeks which I think is because I have the new beta firmware loaded? I tried to login on the ALPHA site but it doesn't recognize my username from the main site.
Should I roll back the firmware & see if I can make it work with the main site? I am just not sure what to do next.
I assume you are using the local app to set this up? The old My Midnite should work fine with the new firmware. You need to make sure "Web Access" is enabled and dns over ride is set to 0.0.0.0 After making these changes and saving them you also need to do a reboot on the classic. it is under the Basic tab called Bully Menu "Reboot"
Actually the new Alpha firmware WIL NOT work with the old MyMidNite which is the problem you're seeing. You'll have to either roll back the Classic firmware or send me the MAC and Device ID of the unit you want to see on the Alpha mymidnite site. Just use the contact form on the current site to send me the info and I'll get you going on the Alpha site:
https://mymidnite.com/drupal/?q=contact
Thanks,
-Andrew
Wow what great service around here I didn't expect to get help so quick. Just to clarify I am running the 2-19-15 firmware and would like to use the new site if possible because for me being able to see the SOC from the WBjr is probably the most important thing when I'm not here at the site. The only weird thing I have seen with this firmware is that since I loaded it all the leds have a slow flash (150 lite) since I'm using local app to configure I just left the display disconnected for now, I will post that info in the firmware thread maybe it's a bug or maybe just a problem with my unit.
Is the my midnite communication 2-way or does the Classic just report in to the server? My internet access is through an AT&T 4g hotspot so inbound traffic is NAT'd out (no routable public IP) which is the reason I can't just use the local app remotely. The Classic is connected to the hotspot with a wifi client bridge. Does the MAC address need to be passed through correctly? I was running dd-wrt on a linksys E1000 as a client bridge but read that sometimes there is problems passing the proper MAC address so I dug out an old 802.11b Senao bridge and set it to use MAC cloning & now my hotspot shows the MAC of the Classic properly.
I will send you the MAC & device id so I can try it with the new site. Thanks
Thanks!
The MyMidNite connection dials out from the Classic only -- the server only grabs the delivered info but in no way tries to initiate communications. Your situation is exactly the reason we designed in MyMidNite!
There will be a lot of bugs with this version -- it is Alpha. Hopefuly with the bugs found and fixed we'll have a production release out soon.
Thanks for getting me set up on the new server, unfortunately I seem to be having some issues on my end (nothings ever easy, right?). I had a bit of time to mess with it on Sunday so I rolled back the firmware to try to get it working with the old site. I tested 5 different laptop/netbooks XP & 7 on the wired end of the client bridge all worked fine with Internet access within about 5-10 seconds of plugging in yet no dice on the Classic reporting in. So I did some captures with Wireshark, I'm seeing the UDP packets & TCP Modbus packets if I use local app but no TCP packets out to the server (web access is enabled, DNS overide set to 0.0.0.0, and rebooted).
When I got a little bit deeper in I noticed that there seems to be problem with ARP when the Classic sends out an ARP request nobody responds & when the router sends out an ARP request the Classic doesn't respond. Yet all the other machines seem to respond with the MAC. I disabled the MAC clone on the bridge thinking maybe having two IP's with same MAC was causing an issue but still same thing with either the old Senao bridge or the Linksys E1000 with dd-wrt in client bridge mode. I'm guessing that needs to resolve before it will start sending TCP packets to the server?
I will try to do a capture on a Linksys WRT54g with stock firmware set up normal as a router with no WAN connection and see if it acts different. I'm not really in a big hurry to get this working as the system seems to be working fine & I need to step back and take a break for a couple days.
That is great information, noservices. The ARP info is handy, though I don't understand why that would be happening myself. If the behavior is the same with two separate bridges and no other devices, then the fault must be with the Classic, however, if it is sending ARP requests and not getting a response, it's difficult to fault the unit itself. I'd love to have a look at your wireshark dumps if you get the chance. PM me or email me at mymidnite.
-Andrew
So some sort of success? Reflashed the 2-19-15 firmware and finally got it to call in by doing a factory reset on the hotspot and I could see the TCP packet . Then I was trying to set the time zone on the new server & FFF'd it all up now all I can get is an error unknown time zone page.... I will send you the Wireshark files showing the ARP issue.