New Member
Posts: 13
Registered: ‎11-04-2013

Re: UCRM Plugins, UCRM API

[ Edited ]

Hello,
    we have a problem with FIO bank Plug-in. Everything is set according to the instructions. The plugin version is 1.1.1. The UCRM version is 2.15.0-beta2. The plugin log is:
[2019-01-07 9: 25: 01.285881] [info] CLI process started
[2019-01-07 9: 30: 01.493999] [info] CLI process started
[2019-01-07 9: 35: 01.415395] [info] CLI process started
[2019-01-07 9: 40: 01.632886] [info] CLI process started
[2019-01-07 9: 45: 01.653105] [info] CLI process started
[2019-01-07 9: 50: 00.829826] [info] CLI process started
[2019-01-07 9: 55: 00.867737] [info] CLI process started
Unfortunately, no incoming payments are showing in payments.

Thank you for your answer

 

 

PHP log:

[07-Jan-2019 13:25:01 UTC] PHP Fatal error: Declaration of FioCz\Service\FioCurlExecutor::curlQuery($url, array $headers = Array, array $parameters = Array) must be compatible with FioCz\Service\CurlExecutor::curlQuery($url, array $headers = Array, array $parameters = Array, bool $verifySsl = true): array in /data/ucrm/data/plugins/fio_cz/src/Service/FioCurlExecutor.php on line 9

Ubiquiti Employee
Posts: 1,473
Registered: ‎03-21-2016
Kudos: 242
Solutions: 159

Re: UCRM Plugins, UCRM API

Hello @michal_lbnet, thank you for the report, we'll look into it.

Ubiquiti Employee
Posts: 1,473
Registered: ‎03-21-2016
Kudos: 242
Solutions: 159

Re: UCRM Plugins, UCRM API

Hello @michal_lbnet, we just released FIO plugin v1.1.2 which should fix your problem.

New Member
Posts: 13
Registered: ‎11-04-2013

Re: UCRM Plugins, UCRM API

Hello,

plugin still returns a bug.



[2019-01-11 12:13:01.486783] [info] CLI process started
[2019-01-11 12:13:02.193773] [info] Processing transaction 17729647967.
[2019-01-11 12:13:02.291275] [warning] No result found for transaction 17729647967.
[2019-01-11 12:15:01.645319] [info] CLI process started
[2019-01-11 12:15:04.753809] [info] Processing transaction 17729647967.
[2019-01-11 12:15:04.862257] [warning] No result found for transaction 17729647967.





PHP Log:

[11-Jan-2019 12:15:04 UTC] PHP Fatal error: Uncaught TypeError: Argument 4 passed to FioCz\Service\CurlExecutor::curlCommand() must be of the type array or null, string given, called in /data/ucrm/data/plugins/fio_cz/src/Service/UcrmApi.php on line 57 and defined in /data/ucrm/data/plugins/fio_cz/src/Service/CurlExecutor.php:14
Stack trace:
#0 /data/ucrm/data/plugins/fio_cz/src/Service/UcrmApi.php(57): FioCz\Service\CurlExecutor->curlCommand('https://localho...', 'POST', Array, '{"clientId":nul...', false)
#1 /data/ucrm/data/plugins/fio_cz/src/Facade/UcrmFacade.php(148): FioCz\Service\UcrmApi->command('payments', 'POST', Array)
#2 /data/ucrm/data/plugins/fio_cz/src/Facade/UcrmFacade.php(52): FioCz\Facade\UcrmFacade->sendPaymentToUcrm(Array)
#3 /data/ucrm/data/plugins/fio_cz/src/Importer.php(93): FioCz\Facade\UcrmFacade->import(Array)
#4 /data/ucrm/data/plugins/fio_cz/main.php(18): FioCz\Importer->import()
#5 /data/ucrm/data/plugins/fio_cz/main.php(26): {closure}(false)
#6 {main}
thrown in /data/ucrm/data/plugins/fio_cz/src/Service/CurlExecutor.php on line 14
Ubiquiti Employee
Posts: 4,155
Registered: ‎12-10-2015
Kudos: 1471
Solutions: 315

Re: UCRM Plugins, UCRM API

@michal_lbnet this shouldbe fixed in the latest FIO Plugin version 1.1.4
New Member
Posts: 42
Registered: ‎12-13-2017
Kudos: 83

Re: UCRM Plugins, UCRM API

Patch requests to the service device endpoint aren't functioning correctly. 

 

Issue 1- The ipRange attribute on service devices should not be required when making patch or post requests. An IP address is not required when creating one in the portal, so it shouldn't be required through the API. I have a service device created in the portal without an IP address assigned, and want to change a setting on it, but can't without adding an IP address to the service device.

 

Issue 2- Can't change the IP addresses assigned to a service device through the API, only able to add more IP addresses to the service device. Should be able to make a get request to the end point, change the ipRange attribute, then make a post request to the end point and have it change the IP addresses assigned to the service device, but right now it just adds the additional IP address to the original.

 

Issue 3- If you make a patch request to the end point with an ipRange attribute of the current ipRange of the service device it creates duplicate IP address entries on the service device. Say you want to change 'sendPingNotifications' from false to true. You make a get request of the service device, change the sendPingNotification attribute from false to true, then make a post request with the info, the service device will now have every IP address assigned to it assigned twice. If you were then to do the same to change the createSignalStats attribute, each IP address would now be assigned to the service device 4 times.

Ubiquiti Employee
Posts: 4,155
Registered: ‎12-10-2015
Kudos: 1471
Solutions: 315

Re: UCRM Plugins, UCRM API

@kysevenle note that all the device/network related API endpoints will soon be removed from UCRM and those in UNMS should be used instead, read more here: https://community.ubnt.com/t5/UCRM/UCRM-Service-Devices-IDs-Changing-or-Re-used/m-p/2692515#M14170
Member
Posts: 228
Registered: ‎03-19-2018
Kudos: 52
Solutions: 7

Re: UCRM Plugins, UCRM API

[ Edited ]

It would be helpful if the API docs included a list of exceptions thrown by the UCRM API. Similar to what Stripe does in their docs https://stripe.com/docs/api/errors/handling?lang=php

HTML, SCSS, Javascript(Ember.js), Ruby(Ruby on Rails), PHP
Highlighted
New Member
Posts: 29
Registered: ‎10-03-2018
Kudos: 1

Re: UCRM Plugins, UCRM API

I need a way to add and delete deferred service changes using the API. Is this currently possible?  If not, can this be added?