Todo/Alert of MyFlowerPower differs from the application one

Other Products Flower Power
#1

Hi all,
I was wondering if it is normal that all the informations available on myFlowerPower are not the same than the one of the iOS App ?

I have my raspberry which perfectly synchronizes data however from some weeks I have no more notification on my iPhone (It was working few weeks ago and I think that I have only one time tested to disable notification in iOS prefs) and now I never had again notifications again of I set naturally the notification permission to on.
Do you know a way to reactivate ?
(I have already to remove and re install the iOS app but no effect.
Thanks in advance!
B.

#2

Hi @B88

It probably because your token from Cloud is expired. Without token, no request to Parrot Cloud and no notification on you apple device. The token expire after about 4 weeks.
I updated the program: auto-refresh token to keep the program alive.

To get the new version, delete the old folder and re-clone the repo:
$ sudo ./run stop // to stop communication of Bluetooth if the program is running
$ cd && git clone https://github.com/Parrot-Developers/FlowerPower-Tools.git
$ cd FlowerPower-Tools/BLE-cloud-bridge/
$ ./configure

Bruno :smile:

#3

Hi Bruno!
Thanks for your reply, but in fact I have well updated from last commit I think:

pi@raspberrypi ~/FlowerPower-Tools/BLE-cloud-bridge $ git log |more
commit 40e9a32fb57b83026005ff7519eded81db38d124
Author: bsautron sautron.brunojj@gmail.com
Date: Wed Dec 9 11:22:31 2015 +0100

If not avalaible, goto the next sensor

I don’t if it is related but when I look at the sudo ./updatedb all 300
the recent log appears in red/brick color:

(between the two I had a power break on my house), I suppose that there is a link?
Thanks for the fast reply! :grinning:
All the best,

#4

The undefined is really strange… Please check the version of cloud library:
$ node-flower-power-cloud/package.json

Must be 1.0.0 and author must be me too “Bruno Sautron”

Don’t worry about color :stuck_out_tongue: It is just random color every new start of program.

#5

ha ok for the colors :wink:
When I was re installing the last version I remember than some optional parts of package produce errors. And If I look at the trace I have only that in pm-trace.log:
npm WARN package.json Flower-Bridge@0.2.1 No repository field.

#6

yes I have well a 1.0.0 from you:
more node-flower-power-cloud/package.json
{
“name”: “flower-power-cloud”,
“version”: “1.0.0”,
“description”: “A node.js module to interface with the cloud service for the Par
rot Flower Power”,
“author”: {
“name”: “Bruno Sautron”,
“email”: "sautron.brunojj@gmail.com"
},
“repository”: {
“type”: “git”,
“url”: “https://github.com/Parrot-Developers/node-flower-power-cloud.git
”
},
“bugs”: {
“url”: “https://github.com/Parrot-Developers/node-flower-power-cloud/iss
ues”
},
“keywords”: [
“Parrot”,
“Flower Power”
],
“main”: “./FlowerPowerCloud.js”,
“engines”: {
“node”: “>=0.8”
},
“readmeFilename”: “README.md”,
“dependencies”: {
“cli-color”: “^1.1.0”,
“node-schedule”: “^0.6.0”,
“request”: “^2.67.0”
}
}
:open_mouth:

#7

It’s only warning, not errors.
And… it works now?

#8

The site is well synchro but just the alert looks not available in particular on IOS.
For instance on the site this morning there was an temperature alert but nothing on the iPhone.
I wonder if it is not a notification pb from the iOS app when we disable the notification and re enable it, it looks that it break all notifications.
Perhaps it could be checked with the dev team of the iOS app ?
(by the way I have no more IFTTT sms, it is perhaps related ;(… )

#9

I don’t know exactly how the IOS app works. Try to clear cash so

#10

For IFFFT I just see that they mention an error…:

Parrot Flower Power Trigger Error Dec 8, 2015 at 7:23PM
An error with Parrot Flower Power prevented your Recipe from working. Edit the Parrot Flower Power Channel or try again. If errors persist, visit the Help page for support.

I Update just update it perhaps it should work again :wink:

#11

Yes I just do it I will see and I will let you know!

#12