Jimbo.Automates

Looks like your PG3 python interface is not up-to-date, not sure how that can happen. Please PM me the download log package file. You can ssh to your polisy and run this, then restart the node server: sudo -u polyglot pip3 install --upgrade udi_interface

Sorry, I'm asking @bpwwer who is the PG3 developer, not you. Sent from my Pixel 6 Pro using Tapatalk

@bpwwer was this intentionally removed? Interface getNodeNameFromDb Sent from my Pixel 6 Pro using Tapatalk

Awesome, thanks for confirming. Sent from my Pixel 6 Pro using Tapatalk

I've added some issues, please add if you find others: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues I'm not going to make an official release until these are resolved, especially #7 since that could affect existing program references.

Put yours in debug mode, do a query on a sensor and PM me the Log Package so I can confirm what the mold looks like. Their docs say it's a number, but I have no idea what that number means. I've asked their support, but that will probably take a while to resolve. Also, there is a reason it's not included on the others: https://help.airthings.com/en/articles/4418460-mold-do-the-wave-wave-plus-or-view-plus-have-mold-risk-indicators As mentioned in the doc, it should support any sensor they release, but only for the current values being stored.

Airthings node server 0.0.6 released. Fixed https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/6

Last I checked when you delete the NS on PG2 it doesn't actually delete the directory which contains the NS, it only deletes it from PG2 itself and the ISY. The reason this is necessary is this NS stores vital information in a file, which is what the instructions show you how to copy. https://github.com/UniversalDevicesInc-PG3/udi-poly-hue-emu/blob/master/README.md#manual

Airthings node server 0.0.5 released. Fixed https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/5

Airthings node server 0.0.4 released, discover was broken in previous release.

Airthings node server 0.0.2 released, all known issues should be resolved.

This issue is fixed, and it is now released to production as 3.4.4. Let me know if you have any further issues.

I don't see it trying to run discover, please hit the discover in the PG3 UI. If you still have issues, please PM me the file generated by "Download Log Package".

Check the PG3 node server log for errors, and this sub-forum is for ISY On Polisy, not PG3 node servers. You should post about weatherbit here: https://forum.universal-devices.com/forum/296-weatherbit/

Lot's more issues https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues Most importantly is #4 because I forgot to add token refreshing, so when the token times out the node server stops updating.

@macjeff and @johnnyt, The initial version is released to production see https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/blob/main/README.md https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/blob/main/CONFIG.md Only minimal testing has been done and already found one issue https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues Not sure I'll have time to work on it the rest of the weekend so thought I would release it for you guys to give it a try. Let me know your thoughts on this thread.

Very odd because like I mentioned, ST has nothing to do with the state of the Tag Hub, or node server, it is solely managed by PG3. Sent from my Pixel 6 Pro using Tapatalk

The ST doesn't come fr the API, it is handled my PG3. With the previous logs I posted the excerpts of node server and PG3 sending the 1 to the ISY. I'll review these new logs.

Yes, send sys short with params is the best way, and probably all I tested.

That's odd... I can see the bug, but not sure why it's not happening to me. I'll try and test and fix tonight.

In PG3 UI select non production store and install it. If you have issues ask on the Notification node server forum post about it.

Yes, that's why it confused me that they are unique based on sound because customizing sounds is one of the options. @DaveStLou are you using the notification Node server? Would like a couple more testers to confirm beta is good before I release.

If users want to enable/disable showing date/time, but seems important enough to always show it. Also, when I mark one as read in the app, would be nice to close the notification if possible. Also, would be nice to have a mark-all-as-read button.

I see you edit a device and add it to the group, could you also make it so I can open the group and see all devices and turn them on or off there? Sent from my Pixel 6 Pro using Tapatalk

Javi, When you pull down and select the group of notifications from the shade it just takes you to the default page because the notifications are grouped together with the ISY service. Message. Can those be grouped separately? And make it so the group can all be swiped away at once? Can you show the date/time the message was sent in the UD Mobile Notifications list? Maybe with an option for users to disable it? The notification configuration in Android lists them all separately by sound, is that intentional? Sent from my Pixel 6 Pro using Tapatalk