Hi @Jimbo.Automates

Just installed Notification (3.6.6)  on eISY (5.6.2) PG3x (3.1.27).

Trying to set it up, the Configuration Help is not showing up. Github says that 3.6.6.

Using GitHub files to do the install. Let's see, how far I get. The instructions are VERY technical sir!

I'm sure it will get clearer as the product matures. The potential is very exciting for sure.

My first application is to send a notification every time GeoFence triggers, so I can see where exactly I breach the perimeter. Potentially huge help in finetuning that technology.

THANK YOU!

Sorry, I'm not a technical writer... Writing clear documentation is difficult.  But I fixed it last night in 3.6.6 to show more docs, 

You should see the below, but if not the doc is at: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/POLYGLOT_CONFIG.md

14 minutes ago, Jimbo.Automates said:

Sorry, I'm not a technical writer... Writing clear documentation is difficult.  But I fixed it last night in 3.6.6 to show more docs, 

You should see the below, but if not the doc is at: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/POLYGLOT_CONFIG.md

No worries on the instructions🙂

I show this:

the collapse/expand is missing.

Oh, that's not good.  @bpwwer are you aware of this issue?

@Jimbo.Automates Your node server controls when configuration help is available. 

When the configuration button is pressed, the UI checks to see if the customParamsDoc key is set in the database.  Only if it is set will it display the button to show/collapse the configuration help text.

Looking at your node server code, it seems to set that key quite late in the nodes/Controller.py somewhere in write_profile()?  So it's possible that after the initial install it won't get set until after the user has clicked the configuration button.

Or, it's also possible that the browser cache needs to be updated.

In both those cases, refreshing the page will probably allow it to show the configuration help.

Thanks @bpwwer
The node server has custom config information generated on the fly, but I thought it set the initial data in startup to the .md file, but I'll have to check.

Sent from my Pixel 6 Pro using Tapatalk

This is fixed in 3.6.9

Sent from my Pixel 6 Pro using Tapatalk