pjjameso

You are awesome, thank you very much! Will incorporate tomorrow.

Thank you MrBill, here we go... The generator is dumb in that you set the exercise time by pushing a toggle switch that starts the clock for the next run 7 days later at the same time (actually number of hours). So when we fall back or spring forward the time it runs changes by an hour. So perhaps instead of using the day of week and expected time to run we should just know the interval between runs is 7*24 hours. The generator runs for 20 minutes exercising each week. Exercise program works correctly and message is sent by checking state variable as follows: Exercise.SendMessage - [ID 0026][Parent 0025] If $sExercise.State is 1 Then Set 'Notification Controller / Service Pushover polyglot' Send Sys Short With Params To iphone Priority=Normal Format=Monospace Sound=Pushover (default) Retry=30 Expire=60 Else - No Actions - (To add one, press 'Action') There are a total of 18 programs that determine the generator/utility state(s). I have attached a screenshot of them. Here are the state variables

I have a generator that exercises every Sunday at 1pm. Currently have voltage sensors that will trigger a program and send a message that generator is exercising (utility and generator voltage present), powering house (utility voltage zero generator 240), and utility power status (voltage present or not). All this is working perfectly. However in my old age I sometimes don’t remember to check if the generator exercised eg, did I get the message. What I would like is for a program to execute and send me a text IF the generator didn’t exercise as expected. Those dings on the phone do get my attention. Not sure how to go about testing if a state variable did not change at by certain point in time each week. Any thoughts? Thanks in advance.

Display Message in Keypad Line 1, how do I use this? I have the navigator touch screen and can send a message via Area Node. I would have thought the Elk Controller would have changed from False to True if a message was sent/active. Thinking I dont understand the function(s). Thoughts?

I don’t think so as I can go to the pushover web and do a test push w sound and it works while from isy it does not. Will keep playing and see if I can consistently have it fail so we can troubleshoot. As mentioned working now so maybe I should leave well enough alone!

So restarted AC and tried service pushover again and it worked. Edited a network recourse saved and tested both methods and did not work. Restarted AC tried service pushover with screenshot setting and it did work again.... very strange. So currently not touching anything and it appears to be working....

I have tried to send a sound via both the network resources and the service pushover node. No sound from either although all messages come through perfectly. Tested from pushover home page and the sounds work when message is initiated from there. Any thoughts?

Okay, not the sharpest tool in the shed so looking for some guidance. I have created a pushover account and have the userid and api key. I have entered them in the pushover service node section in polyglot and ISY indicates Node server connected and Rest Status is Not Running. I am at a loss at this point... what data goes in: Messages section - ID, Title, Message (1, Pushover, blank?) ISYPortalService Node - Portal API Key (havent found that info) Have setup Network Resources (of course it fails) Name - Pushover POST, ISY IP, 8199, path /send?opt1=val1 (no clue here why) Body - Just put in 'this is a test' What am I missing at this point?

Jimbo, This error popped up this morning. ERROR: 08/20/2022 00:00:03 See log for: ELK Controller: Unknown message AR: 009999160201000100

Was on 3.4.8... restart of ns fixed errors, thank you.

Rebooted this morning, error(s) still there. 2022-08-19 07:08:33,160 ELK-2049 udi_interface.node ERROR node:setDriver: controller:ELK Controller Invalid driver: GV25 2022-08-19 07:09:44,144 Command udi_interface.node ERROR node:setDriver: controller:ELK Controller Invalid driver: GV25

Hi Jimbo, Any idea what this error is in the log, thanks. 2022-08-18 15:03:02,006 ELK-23587 udi_interface.node ERROR node:setDriver: controller:ELK Controller Invalid driver: GV25

Bought the view plus and the Node server works perfectly. Thanks Jimbo!

Just saw this on Node server store and am interested in giving it a try. Before I buy the Airthings View Plus, does this support these attributes? The most advanced indoor air quality monitor measuring particulate matter (PM2.5), carbon dioxide (CO2), radon, VOC (airborne chemicals), humidity, temperature, air pressure and pollen levels.

Deleted and installed UD Node and is working again.... Sorry for the alarm...

Very strange has been working perfectly on UD Mobile. However couple of hours ago UD Mobile is blank with the following error. ISY is showing the correct value and updating but the Node server is showing a bunch of errors. Any thoughts? Kaiterra_8-2-2022_33336_PM.zip

Above my understanding, but appears one can do local storage by flashing the chip. ESPHome Emporia https://gist.github.com/flaviut/93a1212c7b165c7674693a45ad52c512

Bob, Understood. You are a gentleman and scholar, thank you for your response.

Any chance support could be extended for the Vue 2? Would be happy to pay for the functionality.

Hi Bob, thanks again for all your work on this project. Question, Im only showing the total KW on the VUE 2, is the Polyglot suppose to show each of the individual circuits (16) too? If so where should I look for the solution? VUE_7-31-2022_112621_AM.zip

Thanks Bob, not a high priority for me.

Sounds like I need to contact AW to correct their API?

Bob, you are a genius, its working! One question, shows battery levels are low on all sensors which I know is incorrect as I just inserted a new battery in number "two". Any ideas?

Deleted nodes in ISY, uninstalled AW, reinstall AW in another slot, restarted AC multiple times and Polyglot shows correct values under 'main' node, yet ISY only repeats the indoor values for the main values. I see the correct values in the AC event viewer. Any thing else i can try to sort this out? Perhaps a bug in this version of ISY? AmbientWeather_6-1-2022_31814_PM.zip