- Fixes a bug on iConnect that can cause a hang of data logger resulting in socket error messages on sensors page.
- Adds experimental support for new RFXCOM transceiver prototype.
- Fixes a bug on iConnect that results in swap space not setup and activated.
Update 4.9a
Moderator: Mattk
Update 4.9a
Update to Meteohub V4.9a (NSLU2, x86, SheevaPlug, DreamPlug, iConnect) brings these features:
-
markhiseman
- Senior Boarder
- Posts: 63
- Joined: Wed Nov 05, 2008 4:25 pm
- Location: Maidstone, Kent, UK
- Contact:
Re: Update 4.9a
On the 'setup push services' page, I get an error when I try to 'save and test' the email service:
Mail send failed: 0 (null)#myemailaddress: 0 (null) ... where myemailaddress is, of course, my email address.
I got this problem yesterday on 4.9 when setting up my Iconnect for the first time (I used the same settings as for my old NSLU2, which worked fine). v4.9a gives me the same error.
Everything else (e.g. FTP uploads) seems to work. Does anyone else have this problem?
Mark.
Mail send failed: 0 (null)#myemailaddress: 0 (null) ... where myemailaddress is, of course, my email address.
I got this problem yesterday on 4.9 when setting up my Iconnect for the first time (I used the same settings as for my old NSLU2, which worked fine). v4.9a gives me the same error.
Everything else (e.g. FTP uploads) seems to work. Does anyone else have this problem?
Mark.
Re: Update 4.9a
This has nothing to do with the new version, nothing changed there.
As far as I can remember your provider does give some hurdles to you,
when you post your settings/provider, may be someone here in the forum can help.
As far as I can remember your provider does give some hurdles to you,
when you post your settings/provider, may be someone here in the forum can help.
-
markhiseman
- Senior Boarder
- Posts: 63
- Joined: Wed Nov 05, 2008 4:25 pm
- Location: Maidstone, Kent, UK
- Contact:
Re: Update 4.9a
OK, I'll post the question somewhere more appropriate. Thanks.
Mark.
Mark.
Re: Update 4.9a
After upgrading (sheva plug) I get this message repeated in system.log:
cat: /sys/block/mmc/stat: No such file or directory
cat: /sys/block/mmc/stat: No such file or directory
/home/meteohub/wear.sh: line 37: +: syntax error: operand expected (error token is "+")
I have also noticed, that the ntp client synchronizes once (or a couple of times) after a reboot and then no more - at least no more record in the ntp client log.
cat: /sys/block/mmc/stat: No such file or directory
cat: /sys/block/mmc/stat: No such file or directory
/home/meteohub/wear.sh: line 37: +: syntax error: operand expected (error token is "+")
I have also noticed, that the ntp client synchronizes once (or a couple of times) after a reboot and then no more - at least no more record in the ntp client log.
Re: Update 4.9a
This is the same bug, will be fixed with the next update. Please ignore the messages, they do no harm.
Re: Update 4.9a
A few minor issues that may just be my particular system...
Have not had any luck with the insert a second USB stick into the Iomega Iconnect and clone stick 1 feature introduced in version 4.9. No luck in 4.9a either. Inserting a USB stick results in the blue light turning on, but no amount of pressing the button on my system causes the light to flash above the second stick to begin the clone function.
Noticed that when I manually type in a wireless AP name into Meteohub to access a non broadcasted SSID network, the Iconnect wont connect in wireless mode. Creating a conventional wireless access point with broadcasted SSID name allows the Iconnect to connect correctly. This was also the case in version 4.8. CAUTION...The non connectivity issue could also have been a function of password length as the non broadcast SSID was using a 63 character alphanumeric random character password at the time. Reconfiguring the AP with a broadcasted SSID and using a 14 character alphanumeric password allowed the Iconnect to hook up fine.
I have dedicated (non DHCP) IP addresses set up on the Meteohub. For wired Ethernet IP I have 192.168.1.148. For the WLAN IP, I have 192.168.1.149. The emergency wired Ethernet IP is the default 192.168.1.77. On review of my router log of attached devices, I see all three IP addresses are connected wirelessly to my router and all three show to be attached wirelessly using the same wireless MAC address that agrees with the wireless MAC address shown on the Meteohub system info page. I expected that only the WLAN IP address would show up in my router log when in wireless mode and that only the Ethernet IP addresses would show if physically connected to the network using a cable. I did not expect to see all three IP's connected while in wireless mode. Refreshing and rebooting the router and Iconnect does not change this behavior. I am able to access all three IP addresses wirelessly and connect to the Meteohub system successively.
Again, these are minor issues to me that I thought I would mention in case you were not aware.
Have not had any luck with the insert a second USB stick into the Iomega Iconnect and clone stick 1 feature introduced in version 4.9. No luck in 4.9a either. Inserting a USB stick results in the blue light turning on, but no amount of pressing the button on my system causes the light to flash above the second stick to begin the clone function.
Noticed that when I manually type in a wireless AP name into Meteohub to access a non broadcasted SSID network, the Iconnect wont connect in wireless mode. Creating a conventional wireless access point with broadcasted SSID name allows the Iconnect to connect correctly. This was also the case in version 4.8. CAUTION...The non connectivity issue could also have been a function of password length as the non broadcast SSID was using a 63 character alphanumeric random character password at the time. Reconfiguring the AP with a broadcasted SSID and using a 14 character alphanumeric password allowed the Iconnect to hook up fine.
I have dedicated (non DHCP) IP addresses set up on the Meteohub. For wired Ethernet IP I have 192.168.1.148. For the WLAN IP, I have 192.168.1.149. The emergency wired Ethernet IP is the default 192.168.1.77. On review of my router log of attached devices, I see all three IP addresses are connected wirelessly to my router and all three show to be attached wirelessly using the same wireless MAC address that agrees with the wireless MAC address shown on the Meteohub system info page. I expected that only the WLAN IP address would show up in my router log when in wireless mode and that only the Ethernet IP addresses would show if physically connected to the network using a cable. I did not expect to see all three IP's connected while in wireless mode. Refreshing and rebooting the router and Iconnect does not change this behavior. I am able to access all three IP addresses wirelessly and connect to the Meteohub system successively.
Again, these are minor issues to me that I thought I would mention in case you were not aware.