I’ve been working on integrating my NUKI V3 system with JEEDOM, and while the initial setup seems straightforward, I’m encountering some API and callback issues that I can’t quite resolve. Let me walk through my setup and the problem I’m facing, in case someone has encountered something similar or can offer some guidance.
Setup Overview:
- NUKI V3: Installed and functioning properly via both local Bluetooth and the NUKI Bridge for remote access.
- JEEDOM: Running on a SYNOLOGY NAS using Docker, with the official NUKI plugin installed.
- API Configuration: Generated an API key on the NUKI Web interface and configured it within JEEDOM’s NUKI plugin.
The Issue:
When attempting to synchronize my NUKI V3 devices into JEEDOM, I receive an error related to the callback URL. The error message is as follows:
2022-06-15 10:15:03 nuki Erreur sur la fonction cron15 du plugin : Echec de la requête HTTP : http://192.XXX.XX.XX:XX/callback/list?token=[APIKEY generated by NUKI_Web] cURL error : Failed to connect to 192.XXX.XX.XX port XX: Connection refused
What I’ve Tried:
- Network Configuration: I’ve checked my router settings to ensure that the required ports are open and not being blocked by any firewall rules.
- JEEDOM Plugin Settings: Verified that the API key and callback URL are correctly entered in the plugin configuration.
- NUKI Support: Reached out to NUKI technical support and provided them with the necessary details, including my API key, IP address, and port information.
- Local vs. Cloud Integration: Tested both local and cloud-based configurations to see if the issue persists across both setups.
Possible Causes:
- Callback Configuration: Suspect that the callback URL might not be correctly formatted or accessible from the NUKI Web API.
- Port Restrictions: Concerned that certain ports might be restricted by NUKI’s API, preventing the callback from being established.
- JEEDOM Plugin Limitations: Wondering if there are any known issues with the official NUKI plugin for JEEDOM that might be causing this problem.
Seeking Assistance:
If anyone has successfully integrated their NUKI V3 system with JEEDOM or encountered similar API/callback issues, I’d greatly appreciate any insights or troubleshooting steps you might suggest. Specific questions I’m looking to address include:
- Are there any additional configuration steps required for the callback URL to work properly?
- Is there a way to test the callback URL independently to isolate the issue?
- Are there any known limitations or restrictions with the NUKI API that might affect JEEDOM integration?
Thank you in advance for your time and assistance! I’m eager to get this working smoothly and would be happy to share any solutions I find along the way.
Best regards,
Christophe