Just installed a flukso & one sensor, can not see any data on the dashboard, any suggestions?

Just restarted tinkering with my 2 FLukso's I bought a long time ago (one has serial nr 10) ;-)
They both had an old firmware ofcourse - v213.
I configured one for my wifi, succeeded, upgrade the firmware via the dashboard, and now it is up & running again.
I'm trying to configure the other the same way (since they are exactly the same), but lo luck.
Sometimes I saw the Flusko trying to associate (on my TP-Link AP), but never succeeding in doing so.
Even tried with another SSID, same result. Reset of the wifi (x second push on the button), same result.
Very strange thing: when I scan for SSIDs (on the 'old' (ie old firmware) Flukso, when I do "iwlist ath0 scan") I cannot see my SSID, although it is broadcasted by my AP (e.g. I can see it on my portable & mobile).
On the NEW Flukso, the "iwlist" does seem to be present, is that correct?
Very strange: when I do "iwconfig ath0" & "ifconfig", I get the following:
---
root@flukso-3cb2ea:~# iwconfig ath0
ath0 IEEE 802.11g ESSID:"TELENETHOMESPOT"
Mode:Managed Frequency:2.412 GHz Access Point: 02:53:7C:14:3B:90
Bit Rate:54 Mb/s Tx-Power:19 dBm
RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=26/70 Signal level=-70 dBm Noise level=-96 dBm
Rx invalid nwid:688 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

root@flukso-3cb2ea:~# ifconfig
ath0 Link encap:Ethernet HWaddr A8:40:41:00:00:12
inet addr:10.121.49.4 Bcast:255.255.255.255 Mask:255.255.252.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:138 errors:0 dropped:0 overruns:0 frame:0
TX packets:1180 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:21483 (20.9 KiB) TX bytes:331490 (323.7 KiB)
wifi0 Link encap:UNSPEC HWaddr A8-40-41-00-00-12-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:57114 errors:0 dropped:0 overruns:0 frame:10817
TX packets:17705 errors:1260 dropped:16 overruns:0 carrier:0
collisions:0 txqueuelen:195
RX bytes:15774610 (15.0 MiB) TX bytes:1099625 (1.0 MiB)
Interrupt:3 Memory:b0000000-b000ffff
---
Apart from the errors on the wifi0 if, it seems that it is connected to a Telenet homespot - altough I defenitely did not configure this...
Anyway, how can I get this 2nd Flukso to connect with my wifi - what can I test/do/...?
thanks a lot !!!

I'm still running 232version.
Is there a list page of the firm wares now available to the end user and the changes/new features available for Non Tech users?
Non Tech description seem to be missing from this site.
Also where do you get them from?

Thanks Bazzle

After upgrading I have some bugs.

1) date / time deamon does not work. workaround set time manual. (date -s '2015.07.03-19:35')

2) minute tab shows readings with current time + 2 hours?? Time on flukso but other tabs display correct time. Think related to bug #1
My analyses Flukso is set to UTC, minute tab shows CET and other tabs show UTC.

3) graphs show irregular readings on hour tab see pic.
My system works with KWH pulse on switch box to get readings.
Sometimes for couple of hours I see flatlines so It looks like from point 1 to point 2 there are no readings.
https://drive.google.com/file/d/0BxXfTYSeWU4xc2tPQUpLSzU2dWM/view?usp=sh...

@icarus75 Bart:
After testing Beta 2.45 is it posible to switch back if bugs are not solved?
Are there other users with same issues? Or can it be a issue with the upgrade so firmware should be pushed again to my box?

@Remark 15072015
Upgrade to final firmware 2.45 without any issues....

My Flukso uploads to pvoutput.org and both seem consistent with each other. I monitor the total generation each day (as reported by pvoutput.org) and compare with output as reported by inverter (Conext RL 5000). Any ideas why Flukso (i.e. pvoutput.org) reported daily generation is consistently 20% of the inverter reading. The inverter reading is what I would expect.

Many thanks!