@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
@gieljnssns, can I first congratulate you on your clear configuration setup in your home assistant installation?
Many people can learn from it, including me!
With this method of working, using the build-in MQTT client, I can recreate mostly of my existing smappee configuration. Like said, luckily, I already had an MQTT broker running for MySensors, otherwise it is some supplementary work to get one running.
Only the water and gas sensors are not directly possible. I see them as configuration in the mqtt, I can see the temperature, the humidity and the battery level of the sensor.
Probably I must work with the params index0Delta and index1Delta and do the sum per day myself…
Knowing that everything worked before the update, this is a bit unfortunate. But of course better than nothing at all.
Thanks very much.
@Trouble-51, are your other sensors working again?
Mine are still giving the message unavailable and still the error about HTTPError: 401 Client Error: Unauthorized for url, in the logfile.
Thanks
If you have some questions, just ask…
For the water and gas sensors, you can compare the data in MQTT-Explorer and your smappee app
So are mine. My understanding is that the development team is working on an updated version. see:
there will be a fix in update 0.112.4, lets see whether that solves the problems
Does anyone know if you can control the Smappee plugs via mqtt? My understanding of mqtt is limited, but if I understand correctly the monitor only mqtt information to a server. It doesn’t receive commands. Correct me if I’m wrong.
I’m still rather disappointed that the devs chose to support an integration built by the manufacturer that forces you to pay for access to the api, or settle for a lesser integration with more complications to set up. Especially with it being so nonchalantly glossed over in the release, no prior mention of it anywhere in the blog or forum, and nothing being wrong with the previous integration (from what I can tell from reviewing prior logs). It’s also in poor taste (though I’m not surprised) at smappee somewhat sneaking in their written integration and pretty much all but abandoning older hardware. The monitor was not cheap and to abandoning it in less than 2 years is crap.