Has anyone tried the new Pentair integration (Pentair ScreenLogic - Home Assistant) that’s built into the latest version of Home Assistant (2021.4)? The documentation is a bit lite, and I fully admit I’m a bit nervous about trying it out.
(Also, I usually wait two weeks on a new HA release, especially when there’s a bunch of patch releases in quick succession from the main release, as there is this month…)
@bwoodworth Brian, any thoughts about what this new “official” integration means for the future of your integration? I’ve been using it for more than a year, and I’m very happy with it! It would be interesting to compare the features of the two, and see about combining them if there are non-overlapping features…
I have tried it out and it is pretty good. It is nice that it doesn’t rely on MQTT. I always had plans to learn python and create a standard integration at some point, but someone beat me to it. You can run both in parallel to test it out.
I installed it and it looks pretty good. I’ve just played with it a bit and haven’t run into any issues myself. There are no lighting controls yet, so keep that in mind.
Quick Question: My friend just had this system installed at his house and have been trying to get him to dabble in HA. Anyone that has this system, do you have an auto cover installed and if so, can this integration control it?
I couldn’t tell reading through the forum if this was possible.
I would like to measure the time the Heater is active. I see where I can see if the Pool or Spa is in Heat mode but not if the heater is running at a given moment. Does anyone see a topic for this?
I’ve been using this for a couple years, works gelreat, no issues.
Last week, my panel dashboard stopped showing the pentair related items, instead showing “entity not available”. I was able to fix easy enough, it seems that somewhere in a HA update, the entities for my pool no longer show as “.pentair_”, now this is appended with the pentair serial/ID.
However, I cannot find the pool temperature sensor, sensor.pentair_pooltemp. The only sensor that shows is airtemp.
Does this need to be addressed by an update or do I need to do something to resolve?
The Screenlogic integration used to use the older format for MQTT configuration, and today MQTT items require the new format. The old format has been deprecated for months, and with 2022.12, it’s removed. See the MQTT section in Breaking Changes of the release notes:
So, if you never converted your Screenlogic configuration YAML to the new format, and you just updated Home Assistant to the latest release, that’s almost certainly your problem. You’ll need to rewrite the configuration YAML in the new format. (Takes about 15 minutes, tedious but not hard.)
If you have converted to the new format, you might want to share your configuration here so people can look it over.
I don’t recall ever doing anything with the Screenlogic YAML - I’ll have to do some digging. Not sure I’ll know what to do. Is this something that needs to be done even with a new install/setup? Can I remove the Pentair add-in and re-add - does that save time?
Thanks for the quick reply - I don’t always pay attention to the deprecation items, but I’ll have to dig into this one.
According to the Screenlogic integration docs, you can configure Screenlogic via the UI these days. (I installed it before that, and have an all YAML configuration for my installation.)
If you used the UI to add Screenlogic to your installation, you might very well not need to do anything, and this is indeed a temporary issue.
If that’s the case, then probably it’s totally fine to uninstall and re-install the integration. Especially if you didn’t need to do any post-install configuration, it should be a safe operation. (Take a backup right before, just in case!)
But, I’m not the developer of this integration, nor an expert on its behavior. (Clearly!) So take that with a grain of salt. The only thing I can say for certain is, I needed to rewrite my YAML configuration for Screenlogic because it was a manual MQTT setup, and the format for MQTT YAML changed.
I commented out all the Pentair Screenlogic code in the YAML and it’s clear that the update ignored the MQTT setup - all of the devices (named changed) I fixed are still good. But when I look under the Pentair add-in, the pool temperature sensor is nowhere to be found - everything else appears to be there.
Does anyone know what this warning is? I still see ‘target’ in the documentation. Only hte super chlorinate has entry_id:
Deprecating target for ScreenLogic services
Use of an Area, Device, or Entity as a target for ScreenLogic services is being deprecated. Instead, use config_entry with the entry_id of the desired ScreenLogic integration.
Please update your automations and scripts and select submit to fix this issue.
There were some merge issues with the documentation PR update that looked like were resolved, but it appears they were not. I’ll submit a fix.
For clarity, the issue created in HA that you reference is correct. HA would like services that act on an integration-level to use the config entry as the point of reference instead of target going forward.
This is to say that obscure ‘entry_id’ that’s in the /config/.storage/core.config_entries? That sounds like a terrible approach considering that people are going to have to dig through a confusing json file to find it. Perhaps they’ll make this easier but at the moment that sounds awful.
Thanks for doc fix, that’ll help. Appreciate it Kevin.
In the meantime for others:
Example entry in: /config/.storage/core.config_entries:
When creating or editing an automation, script, or even a service call through the UI, the config_entry selector will only show you the appropriate integration instances.
If you prefer to edit in yaml and need the actual entry_id, you can go to the the Services tab in Developer Tools, mock up a service call in UI mode, then switch to yaml mode and the config_entry will be populated with the entry_id.