First of all: Thanks to all contributors to this perfect project!
I really love my just finished HeaterMeter (even though I didn’t do a cook with it yet). Images will follow in a separate thread.
This will be a bit longer - I though about splitting it into more threads, but it wouldn’t have benefited. I’ll try to keep the different parts separated a bit.
------------------
General remark:
One minor remark for the Software page in the wiki:
The B+ also needs the current snapshot image. Or you manually exchange get the latest boot files "bootcode.bin", "kernel.img" & "start.elf" from Raspberry project and replace the current ones, as given on the openwrt page.
------------------
Bug?
Then, there seems to be a WLAN bug in rt8192cu in the current HM builds that gave me headache for a weeks evenings. I stumbled upon that while working on scripts to change the WLAN AP (see below).
I’m not sure if it is known already as I just read the last sentence on the Software page about rebooting to switch to WLAN.
I’ve got a "Edimax EW-7811Un 150Mbps Wireless 11n Nano” which is basically working. I can connect to my WPA2 secured AP at home.
However, I can only connect once after reboot. If I press the “reconnect” button for wwan on the network page, the WLAN stick does not reconnect correctly. It blinks periodically, show on the web page that it is connected to the AP, but doesn’t get an IP. Also running udhcp on the command line (ssh via network cable) doesn’t help. My AP shows it to be connected, but with extremely low speed. Only rebooting the pi helps.
The same state can also reproducibly be reached by associating to different APs. via the Wifi page, I can switch the AP once, on the second change of AP it ends up in the same unknown state.
I tried to isolate this one a bit, but didn’t get too far.
- I tried the 12.09 AA from openwork.org, but this doesn’t have support for rt8192cu
- I tried the 14.07 BB from openwork.org, but this had more general problems in the downloadable build. "lsmod” didn’t show any modules, and the rt8192cu module didn’t load, even though I installed the package
- I tried the current trunk (Jan 30) from openwork.org and it worked perfectly after installing the modules. Hence my WLAN Stick and pi are fine.
This bug is not nice, but also not serious. Connecting to a WLAN after a reboot perfectly worked up to now. also no connection losses up to now. Hence, this is no urgent problem, that will disappear after switching to a newer openwork version. If this is known, maybe just add the information to the wiki, so other do not also waste the time...
------------------
Feature request / workaround / finished scripts to include?
As the HM is only controlled via the four buttons / joystick and the RJ45 network connection is not accessible without opening the box.
I need to be able to easily switch the WLAN AP, as the coverage here is bad. Hence, I have several APs, and I need to connect to a different one, depending on wether I use the HM a the garage or in the garden. With the current HM, you always have to switch the HM on in the AP rage you used it last, and then reconfigure it for the AP you want to use it. If I take the HM to a friends house I have no WLAN access at (first), I would like the HM to go to AP mode, so I can configure it from my tablet.
The feature request: switch WLAN from a list of preconfigured networks via the AVR buttons.
Possible way to do it: add a config file with the different WLAN configs to /etc, add a variable for the chose WLAN in the AVR. A script then periodically (or only once at boot) checks for that value, sets the WLAN config and reconnects (or opens up an AP).
But with the current WLAN problems (reconnect problems, see above), it cannot be done without a reboot anyway. Hence (and as I didn’t want to change the AVR firmware), I made up a script which I want to share.
Workaround: I started with the AAP scripts from here, but failed with a non-reconnecting WLAN. After isolating this, I made a modified script - Nevertheless credit goes to dabyd64 from the openwrt Forum, as I modified his script to solve my problem.
What it does: At boot (boot script 99), the script looks for known WLANs from the config file /etc. It gives some output of what its doing to the LCD (and system log file).
-> If it finds one and it is different the one currently configured, it sets it up and reboots.
-> If it is already configured, it just does nothing.
-> If it doesn’t find a known WLAN, it sets up the AP from the config file and reboots.
With this script, I can switch my HM on anywhere without worrying about the last WLAN setting and end up with a HM I can connect to.
It works perfectly for me, maybe it helps someone else, maybe it could even be added (in this or an optimized version) to further versions of the HM software.
You can download the files here, for convenience.
I really love my just finished HeaterMeter (even though I didn’t do a cook with it yet). Images will follow in a separate thread.
This will be a bit longer - I though about splitting it into more threads, but it wouldn’t have benefited. I’ll try to keep the different parts separated a bit.
------------------
General remark:
One minor remark for the Software page in the wiki:
The B+ also needs the current snapshot image. Or you manually exchange get the latest boot files "bootcode.bin", "kernel.img" & "start.elf" from Raspberry project and replace the current ones, as given on the openwrt page.
------------------
Bug?
Then, there seems to be a WLAN bug in rt8192cu in the current HM builds that gave me headache for a weeks evenings. I stumbled upon that while working on scripts to change the WLAN AP (see below).
I’m not sure if it is known already as I just read the last sentence on the Software page about rebooting to switch to WLAN.
I’ve got a "Edimax EW-7811Un 150Mbps Wireless 11n Nano” which is basically working. I can connect to my WPA2 secured AP at home.
However, I can only connect once after reboot. If I press the “reconnect” button for wwan on the network page, the WLAN stick does not reconnect correctly. It blinks periodically, show on the web page that it is connected to the AP, but doesn’t get an IP. Also running udhcp on the command line (ssh via network cable) doesn’t help. My AP shows it to be connected, but with extremely low speed. Only rebooting the pi helps.
The same state can also reproducibly be reached by associating to different APs. via the Wifi page, I can switch the AP once, on the second change of AP it ends up in the same unknown state.
I tried to isolate this one a bit, but didn’t get too far.
- I tried the 12.09 AA from openwork.org, but this doesn’t have support for rt8192cu
- I tried the 14.07 BB from openwork.org, but this had more general problems in the downloadable build. "lsmod” didn’t show any modules, and the rt8192cu module didn’t load, even though I installed the package
- I tried the current trunk (Jan 30) from openwork.org and it worked perfectly after installing the modules. Hence my WLAN Stick and pi are fine.
This bug is not nice, but also not serious. Connecting to a WLAN after a reboot perfectly worked up to now. also no connection losses up to now. Hence, this is no urgent problem, that will disappear after switching to a newer openwork version. If this is known, maybe just add the information to the wiki, so other do not also waste the time...
------------------
Feature request / workaround / finished scripts to include?
As the HM is only controlled via the four buttons / joystick and the RJ45 network connection is not accessible without opening the box.
I need to be able to easily switch the WLAN AP, as the coverage here is bad. Hence, I have several APs, and I need to connect to a different one, depending on wether I use the HM a the garage or in the garden. With the current HM, you always have to switch the HM on in the AP rage you used it last, and then reconfigure it for the AP you want to use it. If I take the HM to a friends house I have no WLAN access at (first), I would like the HM to go to AP mode, so I can configure it from my tablet.
The feature request: switch WLAN from a list of preconfigured networks via the AVR buttons.
Possible way to do it: add a config file with the different WLAN configs to /etc, add a variable for the chose WLAN in the AVR. A script then periodically (or only once at boot) checks for that value, sets the WLAN config and reconnects (or opens up an AP).
But with the current WLAN problems (reconnect problems, see above), it cannot be done without a reboot anyway. Hence (and as I didn’t want to change the AVR firmware), I made up a script which I want to share.
Workaround: I started with the AAP scripts from here, but failed with a non-reconnecting WLAN. After isolating this, I made a modified script - Nevertheless credit goes to dabyd64 from the openwrt Forum, as I modified his script to solve my problem.
What it does: At boot (boot script 99), the script looks for known WLANs from the config file /etc. It gives some output of what its doing to the LCD (and system log file).
-> If it finds one and it is different the one currently configured, it sets it up and reboots.
-> If it is already configured, it just does nothing.
-> If it doesn’t find a known WLAN, it sets up the AP from the config file and reboots.
With this script, I can switch my HM on anywhere without worrying about the last WLAN setting and end up with a HM I can connect to.
It works perfectly for me, maybe it helps someone else, maybe it could even be added (in this or an optimized version) to further versions of the HM software.
You can download the files here, for convenience.