"Restart IoX" to reboot PG3x/eisy?

[FerventGeek]

Does clicking "Restart IoX" in the UD Console also reboot the eisy and with it PG3?

I'm confused about how PG3x and IoX share the eisy hardware. As a former PM, I'm sure there's a PowerPoint with layer boxes and client apps, likely with the FBSD kernel at the bottom, then C++ IoX and Python PG3 on top of it, each with independent HTTP service ports. But what I can't deduce is the relationship between IoX and the platform in terms of PG3. The "Multifunction button" doesn't seem to do anything if you press it 5 times, and I hate to power cycle the platform just to clean up occasionally wedged PG3 plugin states. 

So really, a few questions for you gurus:

1. Does the "Restart IoX" button in the UD Console also restart PG3?
   • If not, where is the widget to do that?
2. What's the process to soft reboot/gracefully powerdown the eisy?
   • Is there a command line option for the eisy to do this? OR just used standard FBSD shutdown -p {or -r} now command and IoX and PG3 gracefully exit on the OS halt message? 

Thanks for your help, and I appreciate you looking at it here since this also applies in the eisy and IoX forums. 

Edited Monday at 08:37 PM by FerventGeek
spelling

[bpwwer]

47 minutes ago, FerventGeek said:

Does clicking "Restart IoX" in the UD Console also reboot the eisy and with it PG3?

1. Does the "Restart IoX" button in the UD Console also restart PG3?
   • If not, where is the widget to do that?

No, it should not.  "Restart IoX should only restart the IoX process.

48 minutes ago, FerventGeek said:

 

1. What's the process to soft reboot/gracefully powerdown the eisy?
   • Is there a command line option for the eisy to do this? OR just used standard FBSD shutdown -p {or -r} now command and IoX and PG3 gracefully exit on the OS halt message? 

The "Reboot" button in the UD console will reboot the eisy, basically doing a shutdown -r now command. I believe the only way to power down the eisy is via the command line using the shutdown command.

As far as I know, the only way to restart PG3x is to reboot the eisy**.  This is not something that should be needed on a regular basis.  You should be able to individually restart plug-ins using the Restart button in the plug-in's detail page of PG3.  If that's not working, then it's a bug that should be reported. 

** It is possible to restart the PG3x process via the FreeBSD command line, but this is not an operation that is recommended.  When the eisy starts, it starts the various processes in a specific order so that they all set up to communicate with each other properly.  Restarting PG3 outside of the process may cause issues.

[FerventGeek]

15 minutes ago, bpwwer said:

As far as I know, the only way to restart PG3x is to reboot the eisy**.  This is not something that should be needed on a regular basis.  You should be able to individually restart plug-ins using the Restart button in the plug-in's detail page of PG3.  If that's not working, then it's a bug that should be reported. 

Thanks. It's only one plugin that seem to have an issue, for example AmbientWeather https://github.com/BME-nodeservers/docs/blob/master/udi-ambient-poly.md which returns permission errors from the server until PG3 is restarted. (Plugin restarts don't clear it.) I'll SSH in for reboot.

That might be a fun plugin for a weekend project. Or, on second thought, hacking a plugin to do random SSH commands might not be something to release. 😂 I am however, thinking about a plugin to bring in metrics from Grafana/Prometheus, and an OTel event forwarder. 

Edited Monday at 09:54 PM by FerventGeek
typo

[bpwwer]

2 hours ago, FerventGeek said:

Thanks. It's only one plugin that seem to have an issue, for example AmbientWeather https://github.com/BME-nodeservers/docs/blob/master/udi-ambient-poly.md which returns permission errors from the server until PG3 is restarted. (Plugin restarts don't clear it.) I'll SSH in for reboot.

Well, that's one of my plug-ins and there shouldn't be anything that carries over from a plug-in restart.  Next time it happens, download the log package and PM it to me.

[FerventGeek]

14 hours ago, bpwwer said:

Well, that's one of my plug-ins and there shouldn't be anything that carries over from a plug-in restart.  Next time it happens, download the log package and PM it to me.

Thanks will do. I might remove and reinstall it to get the specific error message. The "stuck" stake flow is:

1. install plugin, get red "you need to set your API key" box on the detail page.
2. Set the key from Ambient Weather
3. "You need to set key" box remains
4. 2nd box also appears with a message that the API request to AWN isn't authorized, and it includes the url the plugin is trying to hit. (Interestingly if you cut and past it into an editor, there's a space in the url after the AWN endpoint and before the path. IF I remove the space and put it in a browser window it works.) 
5. I can wait hours and it remains in this state. 
6. Restart / Stop / Start on the plugin does not clear the error.
7. Reboot eisy, and the problem goes away.

Like I said it would interesting to remove and re add it to see if it's repeatable. It's a great plug in and I showed an app demo of the PG2 version on stage last year for 1,500 observability geeks. IsyJsonGateway, FTW. Thanks for all your work on these plugins! 🙏
 

{
  "ResponseJson": {
    "properties": {
      "property": [
        {
          "@id": "BATLVL",
          "@value": "0",
          "@formatted": "OK",
          "@uom": "25",
          "@name": ""
        },
        {
          "@id": "CLIHUM",
          "@value": "73",
          "@formatted": "73%",
          "@uom": "22",
          "@name": "Humidity"
        },
        {
          "@id": "CLITEMP",
          "@value": "796",
          "@formatted": "79.6°F",
          "@uom": "17",
          "@prec": "1",
          "@name": "Feels Like"
        },
        {
          "@id": "DEWPT",
          "@value": "692",
          "@formatted": "69.2°F",
          "@uom": "17",
          "@prec": "1",
          "@name": ""
        },
        {
          "@id": "TEMPOUT",
          "@value": "7862",
          "@formatted": "78.62°F",
          "@uom": "17",
          "@prec": "2",
          "@name": "Temperature"
        }
      ]
    }
  },
  "Endpoint": "isyportal",
  "Command": "status/n004_ec63155_5",
  "Timestamp": 1747150361.696,
  "IsoTime": "2025-05-13T15:32:41.696+00:00"
}

[bpwwer]

That's strange.  I'm not able to reproduce any of that.  

33 minutes ago, FerventGeek said:

1. install plugin, get red "you need to set your API key" box on the detail page.
2. Set the key from Ambient Weather
3. "You need to set key" box remains
4. 2nd box also appears with a message that the API request to AWN isn't authorized, and it includes the url the plugin is trying to hit. (Interestingly if you cut and past it into an editor, there's a space in the url after the AWN endpoint and before the path. IF I remove the space and put it in a browser window it works.) 
5. I can wait hours and it remains in this state. 
6. Restart / Stop / Start on the plugin does not clear the error.
7. Reboot eisy, and the problem goes away.

After install, I get the "You need to set your API key" notice.

I enter an API key (I don't have an Ambient system or account so I have to use someone else's key)

The notice immediately disappears and the plug-in starts sending queries out.

The plug-in does not have any code to send any other messages for PG3 to display.  So I have no idea where the second box in #4 is coming from.   The plug-in should be logging API key failures and if debug logging is enabled, it will show the URL it is using there.  But there are no extra spaces in that URL.

If you do re-install, please enable debug level logging before entering your API key and then download the log package (maybe even do a screen capture with both messages on the screen).

[FerventGeek]

Thanks Bob. I'm also tweaking my IsyJson gateway to decode Unicode from Isy. Ex, formatted=:

<property name="Feels Like" prec="1" uom="17" formatted="80.4&#xb0;F" value="804" id="CLITEMP"/>

Didn't realize that's the serialization format for the UD Java console, but that makes sense for its heritage, vs UTF-(8/16/32) string encoding. I worked in EBCDIC back in the day, and ISY's stalwart ascii is just fine. Cheers.