Jimbo.Automates

Sorry, no. Make the key a short <= 8 character unique name which will be used as the node address. The instruction says: So make the Value: { "name": "HarmonyHub RomName", "host": "192.168.58.16" } Including the curly braces and all.. I could spend time to make this a better way, but it's so rarely used it hasn't been worth the effort.

Yes, it's alive. But ping packets are different than discover packets, by default some routers do not allow those across. But if you can't find a setting then it must be ok. You can try adding them manually as mentioned in the doc https://github.com/UniversalDevicesInc-PG3/udi-harmony-poly?tab=readme-ov-file#manual-hub-entries Sent from my Pixel 8 Pro using Tapatalk

There may be a setting in the router to allow discover packets from Ethernet to WiFi? Can you ssh to the eisy and see if you can ping the Harmony? Sent from my Pixel 8 Pro using Tapatalk

It says 1.5HP https://www.advancedmistingsystems.com/wp-content/uploads/2022/05/Manual-PullyDriven.pdf I emailed Insteon support and Steve Lee said: So maybe I'll try that if the Zooz doesn't work out, I may have one here at the lake or at home to bring next trip. Thanks for everyone's great info as usual, much appreciated. - Jim

I ended up not going the Sensibo route, and used this which is working perfectly: https://www.totalhomesupply.com/p/airzone-azai6zwumel-aidoo-z-wave-plus-residential-wifi-adapter-for-mitsubishi-mini-splits#product_manuals_tab It was very simple to install, just remove the cover, open one flap, and plug it in. Looks like Airzone has many options for other mini splits. The one I wanted wasn't listed on Total Home Supplies site, they only had a WiFie model so I emailed their support and they added it.

Thanks @larrylix but I've no idea how to install MOVs across the motor windings. I've ordered a Zooz Z-Wave Plus Power Switch ZEN15 for 110V AC Units, Sump Pumps, Humidifiers, and More https://a.co/d/0eS572it Hopefully that will handle the load. Others on reddit have said it works well for this purpose. Sent from my Pixel 8 Pro using Tapatalk

Thanks, I was suspecting a startup surge as well and was hoping there was something simple to help alleviate that.. The cable is 6, is that short?' I tried a filterlinc but they are only rated for 10amps so it blew quickly. Sent from my Pixel 8 Pro using Tapatalk

Thanks, load sensing was off, so I tried turning it on, still no power when toggling with the button, turned it back off and still nothing. I also confirmed my plugin sensor worked on another plug of the same model. Sent from my Pixel 8 Pro using Tapatalk

I have my mister pump plugged into a dual on/off outlet 2663-222 which was working fine, but now fails to supply power to the pump. The label on the pump says 11.9 amps, but the spec sheet says 13.5. The outlet says it's rated for 15amps so should be fine unless peak startup current is to much. The LED still turns red/green and I can hear the internal click when it turns on/off but now power. This was in the bottom plug, now I switched it to the top plug and it works fine, but I assume it will eventually blow as well. Is there anything I can do to alleviate this or must I switch to a higher rated plug?

Pixel 8 Pro, Android 14 with May 5th update Same issue for me on 1.1.78 Sent from my Pixel 8 Pro using Tapatalk

I reported the same on my Pixel 8 Pro. Sent from my Pixel 8 Pro using Tapatalk

Sorry,y fault. I'll release a fix when I get a chance Sent from my Pixel 8 Pro using Tapatalk

Sorry, not possible, they won't send it: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/18

The API does send a notice when the battery is low as mentioned in this old issue https://github.com/Einstein42/udi-ecobee-poly/issues/49 It's difficult to parse the error, but I actually did start to look into it last weekend, but no progress. Sent from my Pixel 8 Pro using Tapatalk

As I discussed with Benoit, these have never changed, I've had plugin installed from day one on my production system, with no issues. We have no clue how this could have happened. You can see the full history of the editors file and it was never uppercase so something funky happened at some point on the PG3 side. https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/commits/main/profile/editor/editors.xml This was exactly why I told you a while back to delete or move to another slot. Deleting plugins is part of PG3 that I don't own, but pretty sure it will only delete the one in the slot you request to be deleted. But, as always, if you are not sure, make a backup of IoX and PG3. As for programs still working, yes they will still function. Delete the plugin from that slot, reinstall it, then reboot IoX and all programs should be fine.

Works fine for me on my Android phone. Sent from my Pixel 8 Pro using Tapatalk

Thanks! I agree, log level should also be retained. Sent from my Pixel 8 Pro using Tapatalk

Thanks @bpwwer , one other question. When it sets the values at install time, does it know not to set them for an update install? Sent from my Pixel 8 Pro using Tapatalk

That is bizarre, @johnnyt has reported similar issues. But, the nodeserver itself has no control over the short/long poll values, it can only read them, not set them. Will need help from @bmercier or @bpwwer if they have a clue. I've also been discussing with @bmercier to add a custom polling that is settable by the nodeserver, so hopefully that can be implemented soon. But in the meantime we need to understand how/why PG3 is resetting the short poll value.

It helps to tag the person, otherwise I assume you are talking to me. I've never seen this issue before, and it's out of my control so doesn't help to keep on it. Post to the ticket. But, I would suggest moving it to a different slot, something is not right with that one, or delete all the nodes in the PG3 UI Nodes page and restart the node server, but that might not help either. The "will try to discover on next poll" is because you really pissed off the Airthings servers and they are not allowing access. I did this earlier today because I had my production and test servers running at the same time and it took almost 40 minutes before it gave me access again.

As I mentioned, nothing I can do about that, it's on the PG3 side.

That's exactly what was fixed in the new version if you read the release notes...

PG3 Airthings Consumer node server 1.1.2 released, see OP.

Tracking of Polled devices fixed in 1.1.2.

Looks like an internet or Airthings server issue, but plugin should handle it better: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/22