PLEASE NOTE: If you had an account with the previous forum, it has been ported to the new Genetry website!
You will need to reset the password to access the new forum. Click Log In → Forgot Password → enter your username or forum email address → click Email Reset Link.
27 minutes ago, The Blind Wolf said:Doing small prints while waiting for your way to resolved it. is it a firmware update that going to need to be done or we got to change something on the gs menu?
Will just be an update. Sorta tweaking it for a fix right now...
Will just be an update. Sorta tweaking it for a fix right now...
Well, i moved my printers to run on the master, so I can update the slave that way we can have a test of sorts to make sure there isn't a conflic between the two version being together. never know, want to make sure everything out in the field works in all the wrong ways 😛
Well got my internet modem upgraded today, alos got 370A 11kw of battery online. resolveing the big battery still no go on it, though I just split my presmatic cell to 12v so I can run my other 200ah battery while I figure out what is going on with that one battery, might end up just stripping it and rebuilding it into two smaller 108ah batteries to save on the head ache of such abig darn battery, that ting is so big you could use the top to play card games on it.
Once the update for the GS is ready then I'm going to switch it back to the breaker box, but, not until I can watch what is going on. I would like to be able to watch it on my phone while in the room. instead of running back and forth to my office.
Gs12 came to life.to bad it's raining but maybe Sid can finish the fixes for the gs6's daisys.2 birds w/1stone.we know someone who will appreciate it.
NOTE: This is a relatively new technology, and may not work on all devices. My (Ubuntu 18.04) laptop running Firefox 88 (or Chromium 90) handles mDNS perfectly, but my Samsung S7 phone with Chrome 91 does not.
MDNS resolution on desktop Linux takes place at NSS (Name Switch Service), and is configurable. Browser really shouldn't matter. IIRC ".local" is just a Linux desktop convention, which hints "please attempt to resolve this hostname via mdns", Android doesn't seem to share this convention.
The inverter should still be accessible using MDNS on Android by omitting .local at the end of the address... I've also seen .lan among other things.
If you can get mDNS to work on an Android device, by all means let us know; I'll happily update the manual. Here's what I found though: https://android.stackexchange.com/questions/49188/how-to-get-mdns-working-for-chrome-on-android
If you can get mDNS to work on an Android device, by all means let us know; I'll happily update the manual. Here's what I found though: https://android.stackexchange.com/questions/49188/how-to-get-mdns-working-for-chrome-on-android
I looked into the issue as well. Are you familiar with adb? A simple test:
> adb shell flame:/ $ ping genetry-34febd9e.local ping: unknown host genetry-34febd9e.local 2|flame:/ $ ping genetry-34febd9e PING genetry-34febd9e.lan (192.168.8.131) 56(84) bytes of data. 64 bytes from Genetry-34FEBD9E.lan (192.168.8.131): icmp_seq=1 ttl=255 time=74.2 ms 64 bytes from Genetry-34FEBD9E.lan (192.168.8.131): icmp_seq=2 ttl=255 time=93.0 ms 64 bytes from Genetry-34FEBD9E.lan (192.168.8.131): icmp_seq=3 ttl=255 time=114 ms
On Android, using http://genetry-34febd9e.lan I'm able to talk to the inverter, both in firefox and chrome.
To clarify: adb shell allows one to get to a terminal on a locally connected android device, provided they have debugging enabled on the device.
Bingo, thanks a lot! Works perfectly on my phone...