Push notifications do not get through

Questions & Help
14

This means we have not found the cause … It might be a network related problem.
What is left:

Summary Table: Troubleshooting Steps

Step Action
Check notification settings Ensure Homey app notifications are enabled and not restricted by OS features
Reboot devices Restart both Homey and your phone
Reinstall app Uninstall and reinstall the Homey app
Review script parameters Provide both athomId and id for user in push notification scripts, we did this!
Avoid flooding Insert delays between notifications to prevent rate-limiting or timeline lockout
Test on another device Try sending to a different phone or user

If nothing above helps, please contact Homey Support:

App or Homey Platform Bugs

  • Occasionally, timeline or push notifications stop working due to bugs in Homey’s firmware or app. Checking the Homey status page or community forums for ongoing incidents can help2511.
  • If you suspect a bug, contact Athom support.

Additional:

run the script (getUsers) below to check the users and usernames:

try {
  // Attempt to fetch all users
  const users = await Homey.users.getUsers();

  // Check if users object is valid and non-empty
  if (!users || Object.keys(users).length === 0) {
    const msg = 'No users found on this Homey.';
    console.log(msg);
    return msg;
  }

  // Prepare output
  let output = 'Available Homey Users:\n';
  Object.values(users).forEach(user => {
    // Check for required properties and handle missing ones
    const name = user.name || 'N/A';
    const id = user.id || 'N/A';
    const athomId = user.athomId || 'N/A';
    const email = user.email || 'N/A';
    output += `\n- Name: ${name}\n  id: ${id}\n  athomId: ${athomId}\n  Email: ${email}\n`;
    console.log(`User found: Name="${name}", id="${id}", athomId="${athomId}", Email="${email}"`);
  });

  return output;

} catch (err) {
  // Log and return error details
  const errorMsg = `Error fetching users: ${err && err.message ? err.message : err}`;
  console.error(errorMsg);
  return errorMsg;
}