Update Server offline

---

Hello together,

I think the update Server is down, i only get a 502 from api.pimatic.org an now my pimatic ist broken after a reboot.

Regards

Hi, because of the ‘502 bad gateway’ error you get some error messages when you start pimatic or a lot of errors when you check if there are updates, but pimatic should start after that.
Did you try a command line restart or reboot?

Hi, thanks for your reply. The problem is that my pimatic is dockerized and i rebooted to test a new plugin version. So i cleared my temp volume for packages und pimatic cant install the missing plugins because the update server is not responding. I fixed this now by manually installing the missing plugins and now everything runs smooth. Except for the update check.

I think it would be nice if pimatic would have an install fallback if the server is not available.

Is the code of the api server open source so that i can setup an own server?

Regards fbeek

Ok, good news pimatic is up again.
I don’t know if the update server is open source. The update server seems to do some checking on plugin and npm data before doing an update. The plugin data is coming from npm and it should be possible to have a direct npm fallback. Building a fallback is core development and its a bit quiet in that area.

@mwittig any news for this?

bump, same issue

same issue, no plugin download.

Day 3 and the Server is still offline.

I think we need here a fallback for the future. I checked the code and there is some sort of fallback to NPM but as it looks it works not really well.

Hi, i also took a look and it seems possible to fall back too only check and update the already installed plugins. But it’s obvious that its not designed to work like that.
The update server has a role in creating and filtering the pimatic plugins, making a fallback for that is another job.

Eventualy @michbeck100 can help here with some informations?

Day 4… yesterday i contacted the pimatic team via info@pimatic.org, but until now no response.

@fbeek I made a small patch for pimatic’s file plugins.coffee.
It’s ment to block the check on pimatic updates and force the search for plugin info to npm.

The changes are
function ‘searchForPlugin’, add first line (before 'return @_pluginsList …)

return Promise.resolve @_pluginList ? []

and in function ‘isPimaticOutdated’, add first line (before 'installed = …)

return false

If you use/test/improve it, let us know the results

@bertreb said in Update Server offline:

function ‘searchForPlugin’, add first line (before 'return @_pluginsList …)

return Promise.resolve @_pluginList ? []

and in function ‘isPimaticOutdated’, add first line (before 'installed = …)

return false

this works for me as i went through a new installation.

I get the same error since days. @pimatic-team please let us know what’s happenin.

@bertreb thank you for the little patch, it worked, i will try to make a real fallback when the server responds a code other than 200.
From the pimatic team i have still no answer.

I hope this has nothing todo with the corona pandemic…

@fbeek said in Update Server offline:

I hope this has nothing todo with the corona pandemic…

No, just holidays

Sorry for the delay and the inconveniences

Successive connection to update server; thanks

Thank for the message, it looks ok again.
For those who used the patch above, please remove it.

Thank you very much. Everything works now.

Hey Together,

the API Server Code is now Open Source, https://github.com/pimatic/update-server

I will try to build a Docker Container for further testing.