larryllix

Put in a ticket and I am sure somebody will be able to help you to fix your problem. UDI is excellent for service, and empathy towards their customers.

I thought you were going to give the old humour thing. I couldn't get my lights back on to fix the problem and now I am burning the midnight oil using a flashlight that is getting dimmer. Another analogous one is MS telling you to go to www.fixYou2.com for help with your ethernet card that has crapped out. Now to return to our regularly scheduled program. Hope you get that eISY running again. I have two polisys, and they are good machines.

LOL! Now I have a complete list in a DNSmasq.conf file. I am going to dump a small test file out of the Netgear router and see if I can hack it, and/or just copy and paste some data into it, so it can be loaded back into the router. Will save me hours and hours of intense typing hex data. Getting old! Yeah, the data entry, and my eyes.

@CoolToys One ASUS router as enough to cover the acre of land, until I purchased more of the same and meshed them. As soon as the mesh happened, the amplitude of the WiFi (even that router) was reduced to the point of having a had time connecting to 5GHz to my wife's iPad, 12 feet across the room with line of site. I solved those multiple problems by garbaging the oldest router with short NVRAM and selling the other three routers after I moved and picked up the fibre router from Bell. That one is done. The long delay with DNS/DHCP is resolved by just giving up on confused and contradicting, Raspbian how-to articles, re-programming my new Bell router and ordering a new NetGear router, to be received today. My plan was, if I could get dnsmasq working on the RPi1 I would move it over to the polisy or my spare polisy for a faster speed. Total failure and I just gave up. Waiting patiently for my Netgear WiFi 7 router to arrive this evening. Hopeful, I can let it do all the DNS, DHCP, and even faster WiFi, and bypass the PITA static DHCP setup in my "new Bell ornament".

I foud the ASUS routers appeared to be fully meshable. I used three units hardwired and one older unit via WiFi backhaul. I learned to play with the transfer specs to make it operate better. However, I found many devices didn't like to switch APs or even worse bands. They would disconnect, get lost, and had to be reconfigured so I had to turn all the automatic features off. I separated the bands into different SSIDs, stopped/reduced the switching of devices to the most convenient AP, and basically the system just became APs. ASUS routers had big problems being stable. I also found after adding more routers to the initial unit the WiFi power levels were reduced drastically. I guess that is what "mesh" is mostly all about...reducing power levels so hundred of routers can exist in the same building and not clobber each other My original router, by itself had no problem servicing an acre property in the rural (WiFi quiet zone) but once I added more routers to troubleshoot some problems with NVRAM inside (I didn't know it) many more problems began. Some factory repairs helped a few of them. Now I have only one router and signals are not a problem. It's just the static IP addresses that are a PITA. I use polisy network resources (4 = On/OFF/LEVELS/EFFECTS) to talk to my inside polisy NRbridge software. That takes a list of devices and send out WiFi signals to my MagicHome bulbs to control them. Magichome bulbs were always cheap and had a lot of features etc.. but their protocols have varied somewhat from version to version. That keeps me busy with python3 hacking the new protocols. Thanks for the inputs on router dementia.

Hi Fred! I had that happen to me many times several years ago. I thought it was fixed now. From what I can recall, if you have a very long post and you use a backspace key, perhaps after using a mouse cursor placement, the whole message text would get deleted. I have never been able to find any trace of mine in the past.

I am discovering these routers have no bypass mode that can be selected. However, I have found reports to put the user router into WAN PPPoE mode, as suggested by the ISP tech, and the ISP router sees that and just passes the packets through, as a self-inflicted bypass mode. Sounds awesome!

Thanks for your long info rant. The router I use is a Bell Home Hub 4000 fibre WAN. The WiFi works much better than my ASUS mesh junk, and very well with tri-bands. I am only buying 150 Mbps fibre access right now for it's 2.5Gbps & 10Gbps ports are just fine. Reserving IP addresses can be done, despite ISP denial ignorance, but it is very clumsy and time consuming. My biggest problem is that it (DHCP especially) cannot be backup up or restored from/to a file. I have had to rebuild my IP DHCP table from scratch several times, and every time I swear I will replace this with my own router. However, Bell states this cannot be done by replacing their router with a Fibre/Ethernet media converter, saying THEIR modem must be in place to get service connected. I am not sure a bridging mode can be established. There doesn't seem to be any selection to accomplish this. A remote DHCP server (dnsmasq on a RPi) does seem to work. It does accumulate leases, in it's file, but once the ISP DHCP & DNS servers are disabled, only LAN items can be accessed. I have pulled my hair out with all the simple "make it work" articles I can find but LAN items cannot get any connections to WAN websites. I have been trying to disable the DNS function out of dnsmasq but cannot make any sense out of any of it, if it is even possible. After a few days of hacking at this, I have restored my replacement HH4000 router with full static IP addresses again. It may take another week of tweaking IP addresses to get this back to normalcy again **sigh ** Right now, I am considering purchasing/borrowing a new Wi-Fi 7 router and disabling DHCP, DNS, and WiFis on the ISP router, to try this out. If it doesn't work, it will get returned for the exorbitant prices being charged for the latest and greatest. I guess I could try my older Netgear router first to see if this is going to work....hope, hope

Yeah conflicting logic in the OP. If the IP was static inside the eISY there would not be greyed out boxes. This should go away with an HTML5 i/f soon. Greyed out boxes are just frustrating users. [emoji120] Sent from my SM-S711W using Tapatalk

I think we have some misunderstanding here. I believe the OP is saying he was using his router to reserve IP addresses on a static basis, not from his devices. I am right in the middle of this same problem as my ISP router suddenly locked out my 2.4GHz WiFi. After much hacking and finally calling Bell support, I had to do the unthinkable, one more time....Factory Reset the router. Well it all came back and I got my WiFi back but lost all my static IP reservations for about 30 WiFi devices. I swear every time that I will find another way to create a DHCP server as this ISP router has no save files feature. Means about 2 days of manually discovering MAC addresses and assigning IP addresses inside the same old router. BTW: They sent me a new router to replace it and I think that may have been a good move, since I am starting from the beginning...one...more....time!!! I decided to add in DNSmasq to another RPi I have running as a genealogy server now. What a mess this has been. ISP is telling me I cannot get my own media converter and my own router as they will not connect it. A separate modem can be connected but typically the master router controls all the DCHP IP address handouts and that doesn't solve anything here. I have DNSmasq running somewhat successfully by splitting the subnet into 192.168.0 - 127 as ISP router DCHP handled address (and dynamic assignments), and my RPi dnsmasq server handling the upper half 192.168.128-254 with static IP addresses. Works somewhat. Here is the problem. When a device send in a DHCP request, the DCHP servers do not know who should handle the assignment...and somehow it takes about 45 seconds for some polisy commands to find their devices. I am not sure how that could be possible but it indicates some real server fighting going on, at times. Now I wonder if I can install dnsmasq into my polisy and let it internally handle DNS/DHCP assignments for home automation devices only. Not sure if this is possible or could even work. Getting old and over my head somewhat here.

Are we almost there yet? [emoji2] Sent from my SM-S711W using Tapatalk

I am on 5.8.xx also. Me thinks that is the O/S version of FreeBSD.

More retries doesn't mean they will take effect every communication attempt. Retries only take effect when a device doesn't get and ACK back, showing successful communication transmission from the receiving device. Most communication packets do not take any retries unless you have bad comms, having interference on your power lines or RF noise in your air. Note that "Retries" are not "Echoes" that Insteon does between devices, to support it's mesh featured protocol structure.

Use the Restore for each device in the admin console. Insteon devices can lose one channel of comm upon being volt jolted.

Christmas and New Years breaks. That is unusual from my experiences.

I had to use the UD mobile app to enable the Portal connection again. The mobile app now contains enables that defaulted to disabled. https://forum.universal-devices.com/topic/44358-geographic-location-restrictions/#comment-388687

Also should be noted that part of the WiFi spec for 5GHz is that it shares frequencies with aeronautical radar and anytime a 5GHz router sees any radar usage it is required to shut down immediately and change frequencies. This only applies to the middle half-dozen channels or so (IIRC). This can cause you hiccoughs in data streaming. Most devices will never show this up to the user but some are sensitive to it. If you are near any airport or in a flight path, choose your 5GHz band channels carefully and possibly consider disabling auto-selection by locking your router onto one the unshared channels.

A month or so back I did a sync in the newer UDMobile app and it disabled my Alexa connection from inside the mobile app. It took me a week to stumble onto enable switches for every function and re-enable them again.

I have a polISY Pro. IIRC it includes the NR module with Pro. I remember I could pass values back and forth each direction. For some time I was using my ISY for sensing and detection and my polISY to send all the commands. It got to a pint where I had to commit to the new hardware and abandon the ISY due to complications and needin two PLMs if I continued.

I did this while moving over from my ISY994 to my polISY. For each parameter, write a program and Netwrok Resource, to detect and trigger each Network resource (on ISY994) that sends the value into a variable using the target's (eISY or polISY) REST interface. Once you have done one parameter (trigger program, and NR) the rest are just copies with the target variable changed. The speed is amazing. It will appear native to the target machine.

Wasn't 2025 one of the dividing lines to determine if the year was 2000-2025 or 1926-1999 depending on the two digit year, above or below the value '25' ? The skill may still have to be enabled again. Alexa cuts off unused connections. AI... you know!

Mine dead also. Ontario Canada

You can calibrate the sensor on the main unit only. I found sensors with varying distances to the wall makes a big difference. Don't place sensors above the stat electronics or you'll get about 3-4F higher readings. Careful with the calibration and repeat after sitting for a few hours keeping in mind the math the stat does on the front face. Use the CSV file reports for more accuracy. The sensors in the main stat are placed at the bottom to eliminate heat influences from the electronics. This is a big problem with many stats where WiFi is a big heat source. The user cannot compensate for it as the manufacturers would like you to believe. Trying to compensate makes the stat sensitive to draughts across the sensor and you will get heat waves from your HVAC system. Yeah, I am very sensitive to 0.5c changes. That is why I am stuck on ecobee stats. I don't like the 3-5F temperature swings built into other brands.

IIRC, those "climates" are spare climates/time segments for custom heat schedules that you can name in your schedule tables on the ecobee stat. I have several custom named schedules like Afternoon, Evening, and Wee Hours, that show up as selectable in my ISY. I might mention that these are safer to use than meddling with the setpoints. They can also eliminate the possibility of programs ramping setpoints to the top or to the bottom in the event of an ISY program logic runaway error. Your stat will not show the actual temperature accurately. The displayed reading will be a result of all your remote sensor's average and possibly the result of a advanced setback or setup compensation. For accurate reading see the downloadable spreadsheet information available in the ecobee webpages. It gives 15 minute updates to every sensor including stat readings and averages to 0.1c resolution accuracies. Stat rounds off to 0.3c. This is why the ecobee stats are so accurate and can operate to such tiny differentials to eliminate heat waves better than most other brands.

I had years of minor troubles with my Champain GDO causing Insteon interference. However it was minor and I always thought it would be my PV inverter system. Years later I installed another GDO system with a battery backup inside and my Insteon comms went to about 10% successful, even though it was further away. After unplugging one and then the other I ordered two Insteon FilterLincs and it solved my Insteon noise problems. It wasn't the motors, but rather their cheap power supplies. When the motors ran it didn't bother the Insteon comms, only the power supplies plugged in.