Does @bsmappee have an idea?
The Smappee integration has changed from local polling to cloud based. Using the API requires you to pay a monthly fee now…
And they do this without any notice and no mention in the notes to the 0.112 upgrade?? Very customer unfriendly business model!
1 Like
@Trouble-51, today I have the same error 
It is indeed a very customer unfriendly business model. I’ve been a smappee customer for a long time, I own one of their first models, the time where you had to do the installation yourself…
I don’t like being put in front of a ‘fait accompli’.
What do you think about this @frenck ?
The previous integration did use the local webapi and without any documentation or warning it is changed to a paid cloud version?
Or am I wrong and it is just a temporary ‘network’ problem?
Any way to go back? Why is this implemented in home assistant without notice. I had fait in an improvement when upgrading. It was mentioned in the blog like that. 
1 Like
You can download HA source code for release 0.111.4 here:
Unzip it, and in the component folder, copy the Smappee folder and paste it in your config/custom_component folder. It should work until something broke.
I agree with @evb, it should have been a breaking change and mentioned in the release note. And the HA core team should tell us why they let a manufacturer change a working local integration by a paid cloud one. That’s no more “local control and privacy first”.
You can always use MQTT for the local readings of your smappee
@gieljnssns, I will give it a try. It should be easy, I already use MQTT for my MySensors. I will report back. Thank you for mentioning!
I emailed Smappee and they asked me to report it as an core issue which I did. They said that the integration only works with Infinity and conceded that they should also have an option for the other Smappee products. So let’s see what happens
1 Like
@evb
I think that’s not true.
I have this model https://theblueadapter.com/smappee-home-energy-monitor-review/
The smappee solar and i have mqtt.
Since the troubles with the new Smappee component, I decided to remove the whole component.
As I said earlier, I use Smappee with MQTT.
This are my MQTT sensors (Voltage, Power: total, L1, L2, L3, Solar: total, L1, L2, L3, Standby Consumption and Cosinus Phi)
The only values that I do not get via mqtt are the totals in kWh, so I have to calculate these via Riemann sum integral
You can find them here
I have a few template sensors to check whether I am using or generating more energy
The most important is eigen_verbruik, this is the energy that I suddenly consume while it is being generated
Then I have some utility_meter over here
As last, I use MQTT switches to track the state of my smart plugs and template switches to change the state
1 Like
@gieljnssns, ok, but I was one of the early adopters, so I have a model MonitorE1 or SmappeeT
Mqtt is not supported for my model
Oh, wait, there was an advanced checkbox, not checked. I checked it and now I see the entries for a mqtt local broker 
I will try this.
The integration still supports all kinds of Smappee monitors. The idea behind the renewed integration is to also support the newer models and have an additional number of entities in HA. However some issues have been opened about the older series and are being fixed.
1 Like
The issue regarding Homekit and voltage sensors has been located and fixed, the PR awaits approval. With the in house implementation of the renewed integration we aim to get the most out of all the monitors and are definitely open for suggestions.
@bsmappee, maybe it is a good idea to clarify the whole smappee integration in home assistant?
- explaining why the configured local smappee sensors are not working anymore after the update to the new smappee integration. If I understand correctly your answer, the integration can/will poll still the local smappee possibilities and not work completely only on the cloud api or am I wrong?
- clarify the fog around the web cloud apis and the mentioned paid cloud apis?
- besides the correction for the voltages sensor problems, the integration did work in my case for one day, but now I see the mentioned error : HTTPError: 401 Client Error: Unauthorized for url: https://app1pub.smappee.net/dev/v3/servicelocation
About your question that you are open for suggestions, I can only respond that I had a working smappee integration before the update and after the update, I have only not available sensors
Just to let everyone know, this is the email i got from the help desk of Smappee, hence my reference to infinity:
Hi Jos,
I’ve discussed it with the developpers.
The best (and fastest way) would be to log an Issue regarding this on “https://github.com/home-assistant/core/issues”.
By pressing " New Issue " and selecting " Report a bug with Home Assistant Core " you can report the issue to the developpers.
“sensor.casa_girassol_line_voltages_a unavailable
sensor.casa_girassol_line_voltages_b unavailable
sensor.casa_girassol_line_voltages_c unavailable
sensor.casa_girassol_phase_voltages_a unavailable
sensor.casa_girassol_phase_voltages_b unavailable
sensor.casa_girassol_phase_voltages_c unavailable”
For the sensors above it is however normal to be unavailable, because you have a Smappee Solar.
These sensors were designed and can only work with Smappee Infinity.
Our devs are working on a version thats skips these when you have a Smappee Solar. (because it is indeed not very clean that these are shown as well)
"
sensor.casa_girassol_always_on_active_power unavailable
sensor.casa_girassol_always_on_today unavailable
"
These should work however.
Best regards,
Mathias
Smappee Support Team