Problems with Pushover & Pushbullet after tonights git pull

[Paul Reed]

Ran a git pull tonight on both node-red & node-red-nodes (my last git pull was 4th Feb) and have run into issues with both Pushover & Pushbullet since.

Pushover

After restarting node-red, all of my Pushover nodes' 'User Key' & 'API tokens' fields were now blank, and messages confirming so were displayed in the error log;

8 Feb 21:30:38 - [error] [pushover:IP change unsuccesful] No Pushover api token set

8 Feb 21:30:38 - [error] [pushover:IP change unsuccesful] No Pushover user key set

If I add the credentials & deploy, the details are not saved, and the node is obviously non functional.

Pushbullet

I no longer have any pushbullet nodes deployed in my flows, yet I get an error in debug saying that the pushbullet credentials are not set.

I have run sudo npm update, and also restarted node-red. Everything else appears to be running OK. 

Paul

[Nicholas O'Leary]

Hi Paul,

I made an update to the Pushover node to user the proper credentials system. It shouldn't have broken anything, but clearly something has. I'll investigate now.

The Pushbullet node also got a big update with some new features - Dave worked with Daniel on that - they will have to look at that one. Just to be clear, when you say 'I no longer have nay pb nodes'... do you mean they have disappeared after the update? Or do you mean that, despite not having any, you are getting the unexpected error message?

Nick

--
http://nodered.org
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Paul Reed]

No, they haven't disappeared, I don't have any in my flows. I have replaced all of my Pushbullet nodes with Pushover nodes. I've checked my workspace, and can't see any orphaned pushbullet nodes lurking about.

Paul

[Nicholas O'Leary]

Hi Paul,

I've pushed a fix for the pushover node. There was a bug where the input fields in the editor were incorrectly named so the properties weren't being picked up - this made them appear blank when opening the editor, as well as ignoring whatever you entered. That error was entirely limited to the editor - on the runtime side, the migration between the two versions of the node is working for me. Can anyone else using the pushover node give it a test?

Nick

[Paul Reed]

Nick, that could be the case, as I didn't send any push messages, I relied on the error messages, and assumed that it would not work because of them. Sorry for the misdirection!

I've tried to update your fix, but it's showing 'already up to date'.

Paul

--
http://nodered.org
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/cDR2b7SxAcE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+u...@googlegroups.com.

[Paul Reed]

In fact, I can confirm that the Pushover nodes do actually work, despite the credential fields being blank, so yes, that was the issue.

Paul

[Nicholas O'Leary]

Paul - oops, failed to hit enter when I typed "git push"... it's there now.

N

[Paul Reed]

Yes, that's sorted it. Thanks.

I'm surprised that it was highlighted in the error log.

Regards the pushbullet issue, I've checked my flows file, and can see a Pushbullet entry in there, so I assume that I should delete the entry and restart node-red.

Paul

[Dave C-J]

Hi Paul

are you still seeing the pushbullet message ? How exactly did you get to this position ? I'm struggling to re-create it here. If I have an old flow with a pushbullet node in - it gives a warning about migrated settings - but does work. I can then either 

1) leave it as-is and keep getting warnings - but keeps working,

2) edit the node and setup extra options if required - save - message goes away

3) delete the node and save - the message goes away.

Thanks

[Paul Reed]

Hi Dave, yes I'm still getting the pushbullet message, and this what happened;

1) Did a git pull on both node-red & node-red-nodes followed by npm update

2) Upon restarting node-red, I saw the message about migrating settings

3) I didn't think that I still had a pushbullet node in my workspace (I now use Pushover), however I found one hidden amongst a flow so I deleted it.

4) So despite now not having any pushbullet nodes in my workspaces, I am still getting the message.

However, I've had a look at my flows file, and I can see a pushbullet entry still there;

{"id":"6cb7e8d.f934818","type":"pushbullet-config","name":"Imported"},{"id":"7077f5fe.8f880c","type":"pushbullet-config","name":"Imported"}

Should I edit & delete that entry from my flows file and restart node-red?

Paul

[Nicholas O'Leary]

Paul,

if you open up the "Configuration nodes"  sidebar from the drop-down menu, you'll see those config nodes in the list. You can dbl click on each one to edit/delete.

Nick

--

[Paul Reed]

That's cleared the message and all looks well again.

Thanks

Paul