webminster

I had to open a ticket to get the reflash chip... I haven't had a real problem since doing the recovery. Now that I have mine in "production" I haven't done many power cycles, but it does run stable and relatively cool.

On my Polisy I have a slot "Plex-WebHook(2)" that shows as unmanaged, in both the PG2 and the PG3 dashboards. I'd think at least one of the two would be managing it. I've rebooted both polyglots and is still there. Is there a reason it would be unmanaged in both? Can I remove it somehow? The button says "no details available."

The update to 2.0.1 fixed it. Thanks! -Alan

I can't seem to get the (3.0.59) PG3 version of this node server working, it appears to react to the webhook, but throws an error (and nothing seen on the ISY:

I'll give that guy a +1... I had him do one of mine (hedging bets). Took about a week or slightly more, but the repair job seems good, and it works. -Alan

Appreciate the replies, and thanks for info about loopback. I've changed to PG configs to use the loopback IP instead. Didn't solve the issue, though, after a reboot the IoP is up, the node servers (PG3) show up and connected - but the status of the devices in all the PG3 nodes is not correct. It becomes correct when I do a restart of PG3 (not the IoP or Polisy proper. -Alan

It's a new Polisy, so I'm in process of moving to it, want to make sure it reboots OK in case it has to. I've had chronic issues with setting the PG2 settings and rebooting, to be given a red box "ISY automatically discovered at http://localhost:8080 however the username and password need to be set in the settings menu." Recurs even after I reenter the config, save, and reboot. Yes, I had forgotten about the "edit current ISY", that's editable. I've changed to the IP address and will see how that goes. Odd that it'd have more trouble with localhost than a DHCP-provided IP. I'd normally think loopback is easier to get right.

The ISY is same address, same box. On PG2, config for ISY is localhost:8080. On PG3, is the policy/ISY address (not changable). I'd probably set locahost there too, but cannot be edited.

That's fine. As I said it works OK after a restart, not changing/adding parameters. What I'm saying is it doesn't start right after a reboot, I have to restart them again to work. Like a race condition where the node servers start too early and don't connect or something. I mentioned above that it says I need to set the password. But I did before the reboot. So if it's not got a password, it didn't save it. But it's fine until the reboot if I set the password in PG2 config. -Alan

I have issues with my Polisy after it is restarted or started cold. None of the ISY nodes show functional until I restart PG2 and PG3. Here's two issues I see: PG2 - After reboot, the PG2 console shows the message: "ISY automatically discovered at http://localhost:8080 however the username and password need to be set in the settings menu." It shows that until I either reset the password in settings (again) or reboot PG2. PG3 - No nodes show any status or values in the ISY console until I restart PG3. Can PG2 and PG3 be patched or fixed to work properly after Polisy reboot? Thanks in advance. -Alan

Thanks... I've been through all those guides, and added filtering, moved devices around, but my house is probably 90 percent reliable still... Direct device control is better than scenes (and I understand that scenes are more fire-and-forget, no acks), and I can't correlate the failures to something else that would make noise or something. If it's a switch or lamplinc defective? how would you know if it's not obviously malfunctioning?

I have tried the 4-tap in the past and found the phases covered... I will try it again this weekend (and probably trying another repaired PLM). Been trying for (literally) years to get my system stable. I have to use mostly single-band devices for light switches. Issues have spanned multiple ISY's, PLMs, etc. And, 90% or more of my devices are on lighting circuits. I can't check lighting circuits specifically (can't plug anything in exactly). Is there any recommendations for checking for noise or other issues for lighting circuits? As mentioned, I have a bunch of the Lamplinc modules all around the house. -Alan

Tried the beta version, and it connects. A few things worked, oscillation and power. Setting fan speed didn't work. I'll attach logs, and I'll try to reply back with a little more test results. As far as capabilities, not sure if I can add much more than this page says: https://homeairguides.com/dyson-pure-cool-review-tp02-tp04-link/ Thanks. -Alan

So, an update: I found this posting and tried opening the Dyson app on my phone first: https://github.com/shenxn/ha-dyson/issues/5 That worked. I was able to get the credentials from my account, 2 fans. They are TP02 fans, the app shows type 475. I added the parameters to the PG3 Node server install, but failing to get the right status. The log shows: 2022-04-26 17:20:29,179 Thread-35 udi_interface INFO dysonfan:dysonConnect: Connecting to host 192.168.1.152 2022-04-26 17:20:29,180 Thread-35 udi_interface ERROR dysonfan:dysonConnect: Error connecting to 192.168.1.152, 'NoneType' object has no attribute 'connect' 2022-04-26 17:20:59,201 Thread-36 udi_interface INFO dysonfan:dysonConnect: Connecting to host 192.168.1.152 2022-04-26 17:20:59,203 Thread-36 udi_interface ERROR dysonfan:dysonConnect: Error connecting to 192.168.1.152, 'NoneType' object has no attribute 'connect' That is the correct IP for the device. Is this because the TP02 isn't supported, or something else? This is PG3 version 3.0.59 on Polisy.

I have no problem logging into the Dyson website (myDyson). As shown above, copy/paste the email address (user name). I'm not prompted by the program for password - it fails right after the email address. Python 3.8.10 on Ubuntu 20.04, changelog on libdyson shows 0.8.9 at the top. Setup.cfg says 0.8.11. Not sure why the mismatch.

Thanks for the response. Tried US in upper/lower case, also tried my email in upper case as well. Same traceback. -Alan

Understood, and I've been trying for a long time to solve the issues. A lot of my network is powerline only (the toggle switchlincs are needed for WAF, and they're not dual band). I do have 7-8 LampLinc modules at various places in the house, some of which aren't actually controlling anything - hoping that they'd act as repeaters/bridges. Based on the distribution of them, I'd hope they'd help fix the lighting control issues - but I don't know how to be sure the signals are good on the lighting circuits. Between the plugging and unplugging, the lamplincs, FilterLincs on UPSes and other potential noise sources... was hoping bumping this up a smidge might help.

After cloning the libdyson repo, am trying to run the get_devices.py script, but no luck: Please choose your account region 1: Mainland China 2: Rest of the World Region [1/2]: 2 Region code: US Email: asparks@zzz Traceback (most recent call last): File "./get_devices.py", line 22, in <module> verify = account.login_email_otp(email, region) File "/home/asparks/libdyson/libdyson/cloud/account.py", line 122, in login_email_otp response = self.request( File "/home/asparks/libdyson/libdyson/cloud/account.py", line 114, in request raise DysonInvalidAuth libdyson.exceptions.DysonInvalidAuth What should I be looking for to solve this? Thanks.

Yeah, I had already cleared the Java cache and verified the versions as part of the 5.3.4 upgrade instructions. And I do use the launcher. Thanks for the reply. -Alan

I understand about solving the comm issues... and I've been trying fruitlessly for awhile. My system isn't very large and doesn't have too many issues, but there's a few I'm trying to see if a couple more retries might help. What I did question was why the error popup... Not sure if this is a firmware 5.x issue (I recently upgraded to 5.3.4), or something else.

Running a 994zw with firmware 5.3.4. If I select one of my switches (2466S), and select Advanced / PLM Communications, and change the retries, a popup "Request failed" is shown... but I also see in the background a popup showing writes at the device. How can I be sure that the retries actually changed? Happens on more than one device, and if I go back into the PLM dialog again it shows the right value... Thanks for any advice.

I recently purchased a Polisy and started setup (moving from ISY 994zw) last week. Had the device up and let it update, poked around a bit and enabled INSTEON support. But, had no working cable to connect to the 2413S so I shut down for a while waiting for a cable. Started powering up stuff today to try again, and the Polisy won't boot. 3rd light only solid, which I understand means corrupted flash. So I have a ticket open for help with that. Device was off and disconnected during the wait. So, the fact that on "second" boot it needs saving is a little concerning, don't know what would have corrupted it a week out of box. Also, it is HOT. I haven't measured the temperature, but it's uncomfortable to hold in my hand after a 10-15 minutes up. Is this behavior normal for a Polisy? Anyone who has one that can offer their experience here? It's hotter than most other electronic devices that I've installed. -Alan

Thanks for the replies... I do have the old zwave board, but I've never actually moved forward with any zwave devices (so there's no devices or topology there to move). I'm assuming that if I've never used any zwave, the empty board won't cause any migration issues... I'm aware I need a PLM of some sort, so I have purchased the 2448A7 USB PLM. Would seem unless I can find another 2413S, it's this way or retool everything. My programs don't use any "adjust scene" or other stuff, so I'm guessing this is not a risky upgrade... but I did not want to take another risk if I don't need to. -Alan

I guess I'm looking at migrating to Polisy due to issues with my PLMs, and general unavailability of replacements (I recapped one, but it still acts flaky). I'm still running 4.9.0 on the ISY994zw. Do I have to upgrade to 5.3 on the 994 to get a "migratable" dump to restore on Polisy? Just hoping to not add another possible failure aspect to the move. Thanks in advance for advice. -Alan

You might have to do 2 scenes for each combo, one to turn on stuff and the other to turn off stuff. For instance, for your A/C combo, create two scenes and include buttons A and C in both. Turn on A and off C in one, and vice versa in the other.