Jimbo.Automates

Issues created for all, and will begin working on these. Sorry for the delay real job and personal life have been crazy for a while and not getting better, but will try to push them through.

Issue created, will starting working on these next. https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/20

Sorry I missed this post as well, must not have marked this forum for notifications. I'd prefer not to do this since the serial number is already available in the node_name, can't you use that?

Sorry I never saw this post, will look into it. Issue created https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/19

PG3 Airscape Plugin 3.0.7 Released, see Release Notes If you have issues or questions please create a new post in this sub-forum.

The PG3 Plugin for Flume Water https://flumewater.com/ version 3.1.0 released. If you are going to buy one, please use my affiliate link: https://flumewater.com?grsf=0tbrt2 See the README for more information. The Release Notes are also available. Users of this plugin please comment on this issue if you have an opinion Consider adding 2 new variables to help with GPM Calculation either directly in Github (preferred) or on this post if you don't have a github account. I can no longer use this device because my water company installed a fancy new meter that is not compatible, but I will continue supporting the best I can. I still have the hub turned on to test, but can't see any water flow.

Did you close and open the AC? Sent from my Pixel 8 Pro using Tapatalk

3.1 released with this added, please confirm since I don't have a water meter that can use Flume anymore.

Looks like it'll be pretty easy issue added https://github.com/UniversalDevicesInc-PG3/udi-poly-FlumeWater/issues/8

I see. I could add an option to turn off polling for a device, I have that option on other plugins. Sent from my Pixel 8 Pro using Tapatalk

There is not, when the plugin restarts it will add it back. Sent from my Pixel 8 Pro using Tapatalk

Sorry, I've been traveling a lot and haven't had a chance to look when on my computer. Will try to take a look soon. Sent from my Pixel 8 Pro using Tapatalk

Fixed in 3.6.14

The notification node server 3.6.14 is released, see Release Notes for more information. See the README for more information see the post Instant Notifications!,, Official Documentation and @Kentinada's Notification for Dummies V2 If you have any issues please create a new post in this sub-forum.

I have this working and will do more testing and release soon. I'm not sure how we would have a list of appropriate subjects since AC doesn't allow inputting any string. What about just making the node name the Title? I have done that and can release if you think it makes sense and nobody has an issue with it.

Yes, will look into it issue created: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/issues/55 But I'm not home, and my development Polisy seems to be down and not coming back up so will try to work on it when I return home.

This is also an AC bug that Chris said he would look into fixing. Sent from my Pixel 8 Pro using Tapatalk

Not a recent upgrade issue. More likely you deleted those customization that used to be there? Sent from my Pixel 8 Pro using Tapatalk

Yes, this would have to be fixed in the AC, nothing I can do about it. Need @Chris Jahn to fix. Sent from my Pixel 8 Pro using Tapatalk

It's working fine for me. Sent from my Pixel 8 Pro using Tapatalk

See Editions https://github.com/UniversalDevicesInc-PG3/udi-poly-notification Sent from my Pixel 8 Pro using Tapatalk

Sorry, missed your previous posts, I'll look into it when possible. Sent from my Pixel 8 Pro using Tapatalk

I'm not sure why you are seeing SD's, the manual says: These commands allow programming and reading Insteon device addresses via the M1XSP Serial Port Expander configured in the Insteon mode So the SD is a response back from the M1EXP with an insteon device description. Must not be supported by the Python API I use. The KA is M1EXP response saying which areas all the keypads are assigned to. No need to worry about this one. The KF is M1EXP response reporting a function key was presses, not sure why you would see a timeout. The CS is M1EXP response reporting the control output status. I'm not seeing any of these timeouts in either of my ELK plugin logs. I'll have to dig into the Python API to see if I can figure out why it's complaining.

It happens if I just unplug the PLM then plug it back in.

I shut down the plugin, disconnected the Autelis and it still randomly turned on. Pool tech is going to take a look. Sent from my Pixel 8 Pro using Tapatalk