No access via WAN

Hi Xulong,

Thank you for the extensive reply. This explains what is happening.
You are correct that it is scenario per your para a). I think this must be the most frequent scenario, certainly as far as my experience is concerned.

Unfortunately the remote management tab in Wiser is confusing, as it has a different application in the general routers, and I took it as the same.

Regarding the firmware situation, I accept what you are saying and am glad about it. However, there seems to be an issue then, in that Piced seems to expect 1.30 where it polls, and wants to update the firmware even when it is all in order as per your advise.


Regarding kjayakumar's post, also here thank you for the information as to the use of port 8889.

 

What a read.. So all is resolved?

Cheers..

 

All good

Hi Roosta,

I'd say yes, all is fine. A few things don't come out quite right in the manual, and that may cause confusion. However, once that is resolved, and a decent router is used upstream (if applicable), then Wiser ticks over just fine.

For me, it will now be interesting to see how long I can run it without a reboot, which is the only other thing one might need to take care of. However, that is about the easiest thing to resolve, if need be. After all, we are dealing with automation...

I'd like to thank everyone for their contributions, particularly Brad, who gave me the necessary information to get a connection from outside in the first place.

 

Hi Thomas,

Glad to see it is all working and I was happy to help. It might have looked like I disappeared there, but actually not, I have been PMing people in the background trying to get to the bottom of the configuration best suited for routers without dis-similar port forwarding capabilities. IMHO mapping port 80 directly through externally in this specific case (ie dis-similar port mapping nobbled routers) is not the best option if it also works another way.

It also might be best to just specify replacement of the external router with a higher spec unit if that is an easily available option for the Telco involved, but sometimes it isn't. Luckily most modern routers from Telcos do support dis-similar port mapping.

More testing is being done and I will be back here with details when I get to the bottom of it. Hopefully you are now confident to sell truck loads of Wisers safe in the knowledge that it will work successfully for your clients and install easily every time.

As for the rebooting, on my personal Wiser I have 100+ widgets spread across lighting, A/C, multi-room audio, power management, enviro-monitors (using General Input Unit) with System IOs and a fair amount of logic. The only time my Wiser is down is when I am adding more widgets. I can count on <1 finger the number of times it has needed rebooting this year.

That being said I had previously seen people report on the forum the need to reboot more often and they were chasing that through with CIS with newer firmware levels etc. Obviously they are possibly doing something in their configuration (ie using a feature, widget or different app etc) that I am not so need to continue to chase down those issues until the culprit is determined.

All the best,

Brad