User Profile: abe

Forum Replies Created

Viewing 11 posts - 16 through 26 (of 26 total)
  • Author
    Posts
  • in reply to: Honeywell WiFi Thermostat #959
    abe
    Participant

    Hello, I’m back with some time to work on this.
    1/2. Red SYS light is on solid. Green WLAN light is also on solid. (Power cord is only thing connected. It is possible that some devices are remembering the WLAN login info that they had from last time I had it plugged in. Or, it sounds like a reset had already been performed by me when I last was trying to fix it a month ago.)
    3/4. After doing this, the red SYS light flashed rapidly and continuously for longer than 20 seconds. After typing this, I started a stopwatch and let it run for more than 2 minutes longer. The red light flashed continuously and never did anything else. So, I’m going to repeat steps 3/4 again.
    3/4 repeat. Pushing the reset button for 20 seconds does nothing. Red SYS flashes continously. So I’ll repeat 1/2. I left the router unplugged for 2 minutes, for good measure.
    1/2 again. Device lights up with all lights except NET and WLAN briefly, then only SYS, then WLAN joins it again. Same as first time. Continuous red SYS and green WLAN. Waiting 4 minutes.
    3/4 again. Same thing, all lights except NET and WLAN flash friefly, then SYS flashes rapid red, and stays rapid red…. presumably indefinitely.

    At this point, let me know what to do next please!!! I cannot get solid red and solid green after step 3/4.

    in reply to: Honeywell WiFi Thermostat #812
    abe
    Participant

    Just to check in, I’ve not had time to do any more work on this yet. I’m not giving up, but I want to make sure that my right to get warranty service or return service are not affected, should it come to that. Not that I want it to. Thanks!

    in reply to: Honeywell WiFi Thermostat #767
    abe
    Participant

    Good morning. I finally got back to this. I took the following steps.
    1) Remove the Netgear. Re-connected PCWRT.
    2) Used Restore to install the updated config file.
    3) Turned off Parental Controls entirely.

    I rebooted the router. But, I don’t think the DNS server function was working as I could not get any data anywhere on any of the connected devices, wired or wireless.

    I removed pcwrt and reconnected Netgear, and I have data back again. DNS working. So it’s not the modem.

    Am I missing something?
    thanks.

    in reply to: Honeywell WiFi Thermostat #760
    abe
    Participant

    Phew! Thanks for doing that. I didn’t even think of that. I tried doing a full factory reset of the pcWRT tonight, twice, and it has not reset. I held down for more than 10 seconds… but… it still remembers my SSID and also the Parental Controls error still pops up. So for now, I reset my Netgear and I’m back to that for the moment. Waiting until I can hear more from you again. Thank you.

    in reply to: Honeywell WiFi Thermostat #758
    abe
    Participant

    System Settings
    indicates required field.
    General
    Hostname
    pcwrt
    Timezone
    Choose from all timezones
    Choose from timezones with the same UTC offset as browser

    America/Chicago

    Current Time: Sun Jun 26 09:09:23 2016
    Sync Time with Browser
    NTP Servers
    Enable local server
    0.openwrt.pool.ntp.org
    1.openwrt.pool.ntp.org
    2.openwrt.pool.ntp.org
    3.openwrt.pool.ntp.org

    NTP Server hostname
    Save
    Administration
    Change Router Password
    Enable SSH
    Allow SSH login with password
    SSH Keys
    Save

    Hosts
    You can add host name to IP address mapping here. One entry per line.

    127.0.0.1 localhost

    Save
    Backup/Restore Settings
    Restore Factory Default Backup Restore Backup
    Flash New Firmware
    Auto update Manual update
    Click the “Check for Updates” button to start firmware update.

    Check for Updates
    Enter your email address below and click “Save” to get email notification when new firmware is available.

    Email Address
    d********[email protected]
    Save
    Applying changespcWRT TORONTO-N v1.21.1

    in reply to: Honeywell WiFi Thermostat #757
    abe
    Participant

    pcWRT StatusSettings Pause Reboot Logout
    Local Time: Sun Jun 26 09:07:10 2016 Uptime: 0h 1m 52s Load Average: 0.37, 0.24, 0.09
    Internet
    Type: dhcp
    Address: x.x.94.194
    Netmask: 255.255.248.0
    Gateway: x.x.88.1
    DNS 1: 8.8.8.8
    DNS 2: 8.8.4.4
    Connected: 0h 1m 26s
    Wireless
    2.4 GHz
    2.4 GHz
    SSID: Degnan
    Mode: Master
    Channel: 4 (2.427 GHz)
    Encryption: WPA2-PSK
    Connected Devices
    Hostname IP Address MAC Address Network Signal
    ABE-DellNotebook 192.168.10.168 xx:xx:xx:xx:xx:xx Wired N/A
    AbePhone 192.168.10.169 xx:xx:xx:xx:xx:xx Master
    “Degnan” -83 dBm
    KidsPhone 192.168.10.134 xx:xx:xx:xx:xx:xx Master “Degnan” -82 dBm
    LisaIPhone 192.168.10.113 xx:xx:xx:xx:xx:xx Master “Degnan” -75 dBm
    Upstairs 192.168.10.103 xx:xx:xx:xx:xx:xx Wired N/A
    ZachPhone 10.0.0.102 xx:xx:xx:xx:xx:xx Master
    “Degnan_Kids” -79 dBm
    Applying changespcWRT TORONTO-N v1.21.1

    in reply to: Honeywell WiFi Thermostat #755
    abe
    Participant

    Hello. I began diagnosing these steps. I discovered that when parental controls are turned off all the way, the phones both work. However now I have a new era. When I am trying to access the parental controls interface on the router I get this error.

    Failed to execute controller function: ?:0: attempt to index field ‘?’ (a nil value)
    stack traceback:
    [C]: in function ‘assert’
    ?: in function ‘dispatch’
    ?: in function <?:338>

    I have unplugged the router and plug it back in again. It appears that it is not loading now. That the DNS server is not working. Help please? Thank you.

    in reply to: Honeywell WiFi Thermostat #753
    abe
    Participant

    So the Netgear is hooked up as an access point, behind the PC wrt. So therefore if I understand correctly, the access point is subject to the same rules that are created by the PC wrt router. So what I think is happening right now is that the Honeywell Wi-Fi thermostat is also not able to connect to the internet because an IP address is being blocked. I have unblocked the 2 check boxes that you recommended for the user profile. The interesting thing is that occasionally throughout the day, I get an alert message saying that the Honeywell has reestablished its connection but then almost instantly I get another message saying that the Honeywell cannot connect. The messages saying that it cannot connect typically repeat every couple of hours. This is very strange behavior and I wish to solve it somehow!

    in reply to: Honeywell WiFi Thermostat #752
    abe
    Participant

    Hi. I have unchecked those boxes. I have also tried to connect the phone and the t-stat to the Netgear AP. Still no luck here!

    in reply to: Honeywell WiFi Thermostat #750
    abe
    Participant

    So there is one problem with that, which is that it is a Smart Phone with internet on it. I want it to be filtered, parental-controlled content. Can you help me to open those ports somehow please?

    Also, the Honeywell thermostat is still not connecting properly. Do you have experience with this issue?
    Thanks.

    in reply to: Honeywell WiFi Thermostat #748
    abe
    Participant

    Hello,
    It seems that I cannot connect the Honeywell to the wifi. I’ll work on that again here.

    I have another problem, and I’d like to also ask about this. I have a Republic Wireless phone and it cannot make or receive calls. So something is blocking the necessary ports. Here is the info on what ports need to be unblocked, according to their tech support:

    Your Router or ISP must not block outbound traffic (from your phone) destined to the following ports
    5090 UDP for call set up
    6000-29999 UDP for audio
    8883 TCP MQQT (used for Voicemail – MMS – SMS)
    While other apps may use other ports. VoIP for our service uses 5090 and 16384 through 16402. That should be all that is needed to support voice.
    5090 is for the SIP Signalling to setup and manage the call. and the ports 16384 through 16402 hold the actual audio. All of these ports are UDP not TCP.

Viewing 11 posts - 16 through 26 (of 26 total)