Error executing virtual command [].sendNotificationToContacts: (13ms) java.lang.NullPointerException: Cannot get property 'translatedMessage' on null object`

fixed

#2

I have the same issue when it was previously working OK. Looks like it started happening on the 13th.


#3

Same error and issue here, first noticed the lack of notification and the error in the logs yesterday.


#4

Add me to the list. I’m still able to send the same message via notification, just not via SMS. Same error message.


#6

Please report this error message to SmartThings.


#7

I’ll look into it and see if anything changed.


#8

When did this start happening? Any approximate date?


#9

Oh the 13th somewhere between 7am and 6pm. Thanks :slight_smile:


#10

Based on logs, anywhere between 7am and 7pm EST on the 13th.


#11

If it helps at all, here’s a snap of part of the piston and logs that apply to this:

The SMS/notification message and the log debug are the same message. The notification and log debug still work OK. The SMS used to work too.


#12

I noticed this as well with my pistons and also with some native ST SmartApps when it came to notifications (the same error showed up in the Live Logging section of my ST account).

I contacted ST about the issue and they said it was being caused by Notifications to Contacts. The only course of action they gave me was to stop using Contacts as it was unsupported and to send notifications directly to the phone number itself instead.

It’s mostly an easy change in pistons, but it becomes quite tedious if you have a LOT of notifications.


#13

Found the issue internally and reported it to the relevant dev, he is aware of the issue and working to fix it. Thank you for reporting it :slight_smile:


#14

That’s great news, even though SmartThings does not officially support contacts it’s good that they are willing to fix this!


#15

I’ve pushed a non-release fix to webCoRE - please update to latest piston code, it adds a fix to get the SMS working again until ST releases a fix for this. It’s coming, but this piston update can fix it now.

@Rozzly @ryry @bthrock @lflorack


#16

@ady624
Works great! Thanks!


#17

Can confirm, works great!

Additionally, I just got a reply from ST Support this morning:

Hey Robert,

This should now be resolved to receive SMS messages again via WebCore.

Let us know if there continues to be an issue or you have any additional questions - we’re always happy to help!

Cheers,

Jennifer L
SmartThings Support Agent


#18

sendNotificationtoContacts is still failing for me. I had several pistons using it and have changed them to “Send SMS Notification”.
I just checked the one piston I didn’t change, and am still receiving:

** +564ms ║Error executing virtual command [].sendNotificationToContacts: (8ms) java.lang.NullPointerException: Cannot get property ‘translatedMessage’ on null object**

I’m not sure if it matters, but I have been unable to edit devices in the Smartthings IDE for about a week.


#19

Are you on the latest version of webCoRE


#20

Thx. Checking github, webCoRE Piston was obsolete. I’ve updated and will test tomorrow.

Added the next day…It’s working now


#21

SmartThings Technical support also recommended that one remove notifications from their Routines if they are failing like my were and referencing the ST Contact book.

SmartThings Technical Support Response

To answer your question, yes, this is a known issue that just recently popped up with the problem lying in Contact Book no longer being supported. We are looking to fix this issue with automations not running completely (as scheduled), but we, unfortunately, don’t have an ETA yet. I have tagged your account to our problem ticket so as soon as there is an update/resolution you will get notified!

We would recommend (in the meantime) removing notifications from the Routines or getting rid of Contact Book altogether and using the normal built-in notification system.

We can remove Contact Book for you but would need your help in having you remove the contacts from any/all SmartApps/automations first and let us know when that is done. You may run into an error removing the last one, however. we can clear that for you - just let us know!

I did remove the notification from all my routines and will see if this helps get them working again. I did not remove them from WebCore and 25+ other apps that alert me to home automation activities.


#22

Following the Contact Book deprecation on July 31st 2018, webCoRE v0.3.106.20180731 and later provides a way for users to automatically redirect all Contact Book requests to PUSH notifications - this is not optimal, as more people could receive notifications than initially intended, so the option is turned off in the SmartApp’s settings. Enabling it would allow you to continue receiving the notifications, but be aware that other people (those sharing your account) can start receiving them too. Best to visit each piston that uses the now defunct Contact Book and replace that task with a SMS notification, most likely.