Next Source-beta 2.16
Next Source-beta 2.16
Soon a new release from Source 2.16beta available for Beta-testers.
Watch out
Verkenner
Watch out
Verkenner
Best regards, Verkenner
Re: Next Source-beta 2.16
Good News!
I'm Running 2.16 beta for like 5 months now on firmware 27-4-2010
All working good!
Is this new firmware also released?
I'm Running 2.16 beta for like 5 months now on firmware 27-4-2010
All working good!
Is this new firmware also released?
http://www.bwired.nl Online Home, Domotica, Home Automation. Weblog. http://blog.bwired.nl
Re: Next Source-beta 2.16
Good News indeed: Source 2.16beta is stable.
Soon release from Source 2.16 available for all-users
I think Pieter is a Plugwise-Power-User !
Verkenner
Soon release from Source 2.16 available for all-users
I think Pieter is a Plugwise-Power-User !
Verkenner
Best regards, Verkenner
Re: Next Source-beta 2.16
Lets wait for the releasenotes and which firmware.
My Circles only work with 2.16Beta now.
My Circles only work with 2.16Beta now.
Re: Next Source-beta 2.16
Looks like Plugwise released new firmware and beta software for beta testers.
A new public beta version has been released today: version 2.16 (20101118)
Use the update button to download it.
Also, firmware 2.34 (2010-11-01) is beta too.
A new public beta version has been released today: version 2.16 (20101118)
Use the update button to download it.
Also, firmware 2.34 (2010-11-01) is beta too.
Re: Next Source-beta 2.16
Who installed this new software and did the firmware update.
Any tryouts yet
Please Plugwise: we want to test but we need the releasenotes.
Any tryouts yet
Please Plugwise: we want to test but we need the releasenotes.
Re: Next Source-beta 2.16
Installed the update, first one took about two hours and left 4 circles of 20 without new firmware. Second round left one plug without update.
Funny enough the updaters says that everything is up to date....
Might give it another try tomorrow.
It seems that reading/finding the plugs is a bit quicker than before.
schedules seem to stay after the update too.
Funny enough the updaters says that everything is up to date....
Might give it another try tomorrow.
It seems that reading/finding the plugs is a bit quicker than before.
schedules seem to stay after the update too.
Re: Next Source-beta 2.16
Installed the update and firmware. No problems so far. Update was smooth.
Modules seem to respond faster.
Wanted to see if plugwise modules restore previous on/off status after a power failure, but seems is not the case
Modules seem to respond faster.
Wanted to see if plugwise modules restore previous on/off status after a power failure, but seems is not the case
Re: Next Source-beta 2.16
Thanks for the info
And yes this firmware makes switching faster.
Also when you plug the circle in the outlet is does not need to think, it activates almost direct
And yes this firmware makes switching faster.
Also when you plug the circle in the outlet is does not need to think, it activates almost direct
Re: Next Source-beta 2.16
Hi,
did the software and firmware upgrade this morning (2 hours for 28 plugs) and everything went smoothly and is working fine till now. HS plugwise plugin is also working without any problem.
Still interested in the release notes though. It's still not possible to connect to the plugwise webserver remotely...
/Rien
did the software and firmware upgrade this morning (2 hours for 28 plugs) and everything went smoothly and is working fine till now. HS plugwise plugin is also working without any problem.
Still interested in the release notes though. It's still not possible to connect to the plugwise webserver remotely...
/Rien
Rien
Re: Next Source-beta 2.16
Just finished the update as well. It actually went much smoother when compared with the previous firmware update. The upload of the FW to the plugs took most of the time, between 1.45 and 5.15 minutes per plug. Based on this I guess that I now have a better idea on the weak spots in my plugwise network, assuming that a slower upload of the FW implies a weaker zigbee network connection.
Last edited by yjb on Sun Nov 21, 2010 2:38 pm, edited 1 time in total.
Re: Next Source-beta 2.16
@RdP
You mentioned the Plugwise webserver is not reachable from outside. In my setup (and I'm not a network expert) I'm able to get to the webserver (the site you see when enabling the webserver in the setup and typing the ipnumber:port) from external locations by adding the port in my modem/router and link to the ip of the relevant internal server.
You mentioned the Plugwise webserver is not reachable from outside. In my setup (and I'm not a network expert) I'm able to get to the webserver (the site you see when enabling the webserver in the setup and typing the ipnumber:port) from external locations by adding the port in my modem/router and link to the ip of the relevant internal server.
Re: Next Source-beta 2.16
That's strange. I can't get it to workabl wrote:@RdP
You mentioned the Plugwise webserver is not reachable from outside. In my setup (and I'm not a network expert) I'm able to get to the webserver (the site you see when enabling the webserver in the setup and typing the ipnumber:port) from external locations by adding the port in my modem/router and link to the ip of the relevant internal server.
Rien
Re: Next Source-beta 2.16
@rdp this is really not related to the webserver if the webserver:
- isn't only active on localhost/127.0.0.1
- has no default gateway (or static routes based on the outside ip of the client that tries to connect)
- has not a firewall configured for this traffic to block
If all aren't true in your case, it's an issue within your network. If you can reach the webserver from within a client on your network, you'll have to check your router and configure NAT mapping or port forwarding and check the firewall on the box (most SOHO routers configure the firewall also when configuring NAT or port forwarding). It's ofcourse also possible that your ISP is blocking the traffic on common well-known ports (like 80/tcp).
- isn't only active on localhost/127.0.0.1
- has no default gateway (or static routes based on the outside ip of the client that tries to connect)
- has not a firewall configured for this traffic to block
If all aren't true in your case, it's an issue within your network. If you can reach the webserver from within a client on your network, you'll have to check your router and configure NAT mapping or port forwarding and check the firewall on the box (most SOHO routers configure the firewall also when configuring NAT or port forwarding). It's ofcourse also possible that your ISP is blocking the traffic on common well-known ports (like 80/tcp).
Alexander