larryllix

@bpwwer Since Govee seem to be taking off and releasing dozens of cool lighting gadgets, at decent prices, I installed their Curtain, and now the 5m RBGICWCW led strip. IIRC the Govee plug-in seemed to be working well for the Govee Curtain previously. When I installed the 5M LED strip it showed up in PG3x and my polISY and are fully functional but the Govee Curtain disappeared and is not accessable from my PG3x, or polISY, on IoX. Does anybody know if this plug-in can only handle one device? When I rested another api_key and installed it, the plug-in config removed the former one and replaced it with the new one. Also:It would be nice to see an update to the brightness level to match other devices 0-100% (not 256%)

Looks like my estimation was fairly accurate. However, I don't find any API description document on that website, mostly only sales info for their silabs chip. There seems to be some discussion of some code but no actual code or links to anything. Am I missing something?

Where is the local API? I haven't seen anybody that even knows what Matter is, let alone why we would need a new piece of hardware to broadcast a protocol over WiFi hardware that is already built into every router EISY is attached to. From what I can deduce, Matter is just a standardized way of interrogating a device to find out what it is, and what parameters it will accept. That sounds like a huge database to handle every style of device that can be thrown at the EISY. However, I detect the same secrecy for Matter, no different than every other protocol that was destined to fail because the manufacturer always tried to keep it a secret, or was too lazy to write an API document, that programmers could understand and support their products. "Total control...end to end" (we won't mention the EU threat of banning that one! ) I sure hope I am wrong in some of these assumptions.

I have a Govee LED curtain light set and it supports BT, WiFi, and Matter. Alexa sets up with it automatically when permitted. That is over WiFi via the Alexa server through my fibre router and Wifi. Router is a few years old and belongs to the ISP. Just the same old 2.4GHz WiFi AFAICT. Nothing special about this router so I don't understand what the big deal about Matter is.

Does V5.9.1 have support for that bulb yet?

I had one of the early release polisys. IIFC there was an early BIOS chip that had to be udated. UDI spec'd a microSSD to USB interface and gave me an image to update the BIOS, and I still run my polisy with the latest updates. IIRC the USB/microSSD adapter cost about $9 on amazon.com.

Thanks Goosgle! Goose gives little hints called.... .....goslings!

@Guy Lavoie Many apps have learned to ask the google android spy network what your SSID and password is now. I guess the assumption is if you allowed it to install then you already trust it with your credentials. Hassle saver but scary. AI (oneUI guessing?) at your service.

Write the text down in the QR code on the side of the bulb. I write the MAC address on the side of all my WiFi bulbs.

Then you will still be running. v4, similar to running MSDos. Beta means all the 1000s of devices are not installed yet. Sent from my SM-S711W using Tapatalk

..or jack up the price to pay for a support person. People here are happy to help donating their time and actually have used the equipment, instead of just reading a fake AI monitor with a language translator. Sent from my SM-S711W using Tapatalk

@CoolToys Yeah I thought about trying the split IP address technique. Trouble with that is, when a device connects and asks for an IP address assignment from the DHCP server, both routers would see only it's MAC address and both attempt to assign it an IP address from both ranges. There is no "steering" mechanisms. This is not "bridge mode". That could be done with most routers but then the user supplied router, in bridge mode, has it's DHCP server disabled. Only the master router assigns IP addresses and contains the NAT storage. Using the Bell HH4K DHCP server is the problem. There is no backup/restore facility. PPPoE was the real only way this could work, allowing the HH4K router to just act like a dumb modem, and Bell has disabled this function in their routers. Bell will not allow and will not support another modem on their fibre lines. The Netgear went back for refund. I am considering a different ISP now.

Looks like this will only be the second upgrade I won't install since v3.xxx when I bought my ISY994. Too scary and the upgrades don't matter yet.

I think that should have been (typo) $Timer -= 1 For more complete If $sTimer > 0 Then Repeat While device is OFF <---- avoid repeated useless comm traffic if desired Set device ON Repeat 1 time(s) Wait 1 second $sTimer -= 1 Else Set device Off Now to turn device on for X seconds, and automagically turn it off after X seconds. $sTimer = X

I wrote my own interface and had to update the firmware many times each time a new version of the bulbs came out. Then white variations use a completely different level technique also. I have them all compensated with patches now and they work well. I can control up to 10 bulbs simultaneously on the fly with some ISY program code and 3 NRs. All software is contained inside my polisy. Sent from my SM-S711W using Tapatalk

Tariffs are starting on all sides. I buy my equipment, made in UK or S.E Asia anyway. Things are not healthy with this trade war somebody started. It's a way for our governments to take money out of our pockets and many happily support it.

Oh Jeez. You mean we are going to hear... 'are we almost there yet?' ....'are we almost there yet?' . . . . . . . .'are we almost there yet?' over and over? Reminds me of V5.0.1 Sent from my SM-S711W using Tapatalk

Plus or minus 90 days, based on the coding world realities.

Sounds like two guys in Michigan are already setting up a date. Here's hoping you don't have to pay a tarrif on my Canadian data bits.

Complete failure. Double NAT does not seem to be a working option and turning off DHCP would hang the system with no DNS service, causing no accces to the Internet. I suspect switches, instead of the old hubs, are a problem for devices (DHCP servers) on the side as they cannot intercept packets between other devices. I tried a new Netgear WiFi 7 router in PPoE setting with the same problem. Another website suggested using ADMZ in the Bell router but it hung the router completely, every time on both Bell routers each time. After rebuilding the DHCP table (about 8-10 hours) each time I discovered another blog about Bell destroying usage of ADMZ on their routers. https://itnerd.blog/2023/08/28/a-firmware-update-for-bells-hh4000-seems-to-have-broken-advanced-dmz-functionality/ Looks like a business account is necessary (router allows static IPs and can back-up data) with Bell or another ISP that allows user equipment. One tech, admitted they cannot support and do not want any other routers on their systems. They have a hard time creating enough "AI" to support a simplified router/modem. Rebuilt the DHCP tables again. However I do notice the Bell WiFi reaches lamp bulbs around the concrete walls better than the Netgear did.

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.