Indigo Domotics

It appears there maybe a general Smappee system issue as my Smappee has stopped working and the plugin is no longer capturing data.

See this support post - App cannot connect after 24/7 2015 16:00 CET

Thought I would give a heads-up in case any other users of the Smappee plugin are having connection issues.

Just seen this posted on the Smappee forum:

The Smappee service is currently experiencing problems. Your Smappee may show a red light and you may not be able to use the App. We are working on resolving the issue this weekend. There is no need to restart your Smappee or the App. We apologize for the inconvenience.

Hopefully it will be fixed soon

An update from Smappee (extract):

The Smappee services have experienced a temporarily problem, which has now been resolved. In case your Smappee unit has not automatically recovered, you may need to perform a power cycle. Some historical consumption data may look incorrect. This issue will be fixed on Monday. We do sincerely apologize for any inconvenience that this downtime may have caused.
The API is still offline and will be fixed on Monday too.
This also implies IFTTT is offline till we fix it on Monday.
Your Smappee Team

In summary the iOS App is back but the API isn't and so the Smappee plugin won't be able to extract any data until the API is fixed.

Another Smappee user has posted a question regarding local access to the Smappee box which if available would have got round this particular issue as the Smappee boxes were and are still recording data even though they couldn't connect to the Smappee servers.

If local access happens, I will update the plugin to use it.

This whole incident goes to show (IMHO) that making Home Automation dependant on the Internet is potentially asking for trouble - that's why Indigo is perfect as a local based system.

" that's why Indigo is perfect as a local based system. "

+1. Cloud-based services are very unsafe. OK for a non-critical applications, but not smarthome control (or security).

...

Local access works from scratch, some information is available... Default password is "admin"

You can retrieve instant numbers
http://172.16.x.x/smappee.html

Instantaneous values:
voltage=240.4 Vrms
FFTComponents:
Phase 1:
current=12.607 A, activePower=2689.429 W, reactivePower=1399.87 var, apparentPower=3031.941 VA, cosfi=88, quadrant=0, phaseshift=0.0, phaseDiff=0.0
FFTComponents:
Phase 2:
current=5.864 A, activePower=1408.426 W, reactivePower=75.159 var, apparentPower=1410.43 VA, cosfi=99, quadrant=0, phaseshift=0.0, phaseDiff=0.0
FFTComponents:
Phase 3:
current=17.959 A, activePower=4097.856 W, reactivePower=1364.529 var, apparentPower=4319.07 VA, cosfi=94, quadrant=0, phaseshift=0.0, phaseDiff=0.0
FFTComponents:

Load[259720] state[0] power: 0.0 on Sun Jul 26 15:25:40 GMT 2015
Load[302278] state[0] power: 0.0 on Sun Jul 26 14:40:07 GMT 2015
Load[305934] state[1] power: 754.5 on Sun Jul 26 15:25:00 GMT 2015
Load[259723] state[0] power: 0.0 on Sun Jul 26 12:33:41 GMT 2015
Load[310925] state[1] power: 997.8 on Sun Jul 26 14:47:24 GMT 2015
Load[281683] state[0] power: 0.0 on Sun Jul 26 16:26:18 GMT 2015
Load[259721] state[0] power: 0.0 on Sun Jul 26 16:25:23 GMT 2015
Load[281387] state[0] power: 0.0 on Sun Jul 26 12:37:18 GMT 2015
Load[259722] state[1] power: 2002.6 on Sun Jul 26 16:29:58 GMT 2015
Load[261430] state[0] power: 0.0 on Sun Jul 26 16:27:17 GMT 2015

Phase 3, peak active power 16035.136 W at 01/06/2015 21:58:35

Hi Shapa,
Yes I have seen that - it is the data log in the Smappee Monitor Portal.

Not sure how I would use that info (which appear to be instantaneous values) to replicate what the plugin is already doing.
The Smappee box must be shifting the 5 minute average values up to the Smappee servers.
Ideally I would just be able to retrieve those values from the Smappee box.

Hopefully after this latest problem, they might release an API for local access - we'll see

Good news - it looks like the API is working again.

I had to reload the plugin to get it to reconnect otherwise it was failing with REFRESHTOKEN error.

BTW, I've seen REFRESHTOKEN issue quite a few times.

It happens when internet is down and back online again...

May be you can check for the error in the code and restart the plugin automatically?