Plugwise Smile custom_component (BETA)

Ok, thanks.

If that is the case: no notification present, the binary_sensor.xyz_plugwise_notification should return to the OFF-state and then the HA Core Notification should be dismiss-able.

And that is not happening in your system, correct?

What is the HA Core version that you are running?
And which Plugwise-beta, which version are you on?

Based on what you describe I think you are not using the latest version, or maybe you are not using the latest Plugwise-Smile version. How did you install Plugwise-beta?

Home Assistant 0.113.2

Capture6

Sorry, I’ve modified my post above while you were answering :slight_smile:

Version 0.4.0 should work, which Plugwise-Smile version is shown in the Plugwise-beta file manifest.json?

Content of manifest.json:

{
  "domain": "plugwise-beta",
  "name": "Plugwise Beta for Home Assistant",
  "documentation": "https://github.com/plugwise/plugwise-beta",
  "requirements": ["Plugwise_Smile==1.1.2"],
  "codeowners": ["@CoMPaTech","@bouwew"],
  "config_flow": true,
  "zeroconf": ["_plugwise._tcp.local."]
}

I install Plugwise-beta through HACS as well as updating. I am running 0.4.0 as shown in the screenshot. The update to 0.4.1 doesn’t seem usefull for me (i.e. the auxiliary modulation level).

That is the correct version. Hmm, what’s going on…

Time to look at the debug-messages in the HA Core Logs.
Can you please enable debugging for plugwise-beta?
Write this in configuration.yaml:

logger:
  default: warn
  logs:
    custom_components.plugwise-beta: debug

And reboot HA.

After the reboot, if the binary_sensor still has the state ON, please look at the HA Core Logs and “Load the full Home Assistant Log”. Scrolling down, you will see many debug-messages from plugwise-beta. Search for the word “notification”. What does the debug-message with this word show?

Also, version 0.4.1 fixes also other icons that are not correctly displayed.
Like the icons for the Auxiliary Devices sensors, which you should have?

OK, that doesn’t lead us to the root cause as a Home Assistant restart seems to ‘solve’ the returning notification.

I selected specific MDI icons myself in my representation of Anna in HA dashboard, so the fixes in 0.4.1 seem not relevant to me.

Capture7

Yes, I feared that would happen.

Can you try to recreate the error, by disconnecting the CV-ketel from the Smile?
Or powering the CV-ketel off for a while until the error appears?

If you don’t want to do this, no problem. The problem will surface somewhere else, I would expect :slight_smile:

Let me see if and when I can reproduce it. Will keep you updated. Fortunately it seems like a minor issue. At least we know when a notification is not disappearing after dismissing it in the notification part a reboot of HA resolves it :smiley:

Just FYI, w.r.t. Plugwise Notifications, the Plugwise-beta component can only detect them, it cannot dismiss them: there is not communication back to the Smile. So, the notification has to be dismissed in the Plugwise App.
Or it will disappear automatically, when the error is resolved. This happens in my system when I plug a Plug back into the electricity-socket. I don’t understand why this does not happen in your system, when the connection to the CV-ketel is restored.

Sometimes people assume too much wrt HA Core functionality :wink:

I wasn’t assuming HA is in any way able to dismiss a notification at the Plugwise side. When I noticed the notification in HA I already quickly saw the corresponding notification in Plugwise was (already) gone. Having notifications in HA is causing me stress because I am striving to a faultless system :wink:

Sorry, I misread your writing :slight_smile:

I know what you mean, getting Notifications all the time can be annoying.

Please let us know here when you were able to produce the error.

Update 3: v0.5.0 is temporary pulled back, we’ve learned there is a way to implement the changes in a non-BREAKING way.

Update 2: a fix is implemented in Plugwise-beta v0.5.0.

Update: I have it working now. I will let you know when the update fixing this is available (on HACS).

@Atarian I am able to reproduce your issue. I’m trying to solve it, will let you know about a solution once I have it working.

@Atarian, others that are interested: Plugwise-beta v0.5.1 is available for testing.


We have taken extra care so that the implemented changes do not break anything, there should be no risk in updating to this version.

Please test this version (by updating WITHOUT removing the present Plugwise integration(s)) and let us know whether you encounter any problem.

Advice: empty your browsers cache and hard reload, after the update, parts of HA Core are cached in your browser, also parts of Plugwise-beta.

Update to v0.5.1 went seamlessly. Running Home Assistant 0.113.3 and latest HACS (1.3.0b1). Haven’t tried triggering a notification myself.

Great, thanks for letting us know!

I have triggered an error by disconnecting one of the wires that run from the Smile to the CV-ketel.

A question: is there anyone that has a legacy Anna that is still on firmware 1.8?

Does zeroconf-discovery work with the HA Core Plugwise component, in Core v0.113?

any chance for support for Plugwise Stretch ?
it is recognized (by the non beta integration) as ‘stretch v2.3.12’

I’ve already tried to change the username in the plugwise-smile code to ‘stretch’ as that is mandatory
after that the integration gives ‘Unexpected error’ when entering the 8 characters ID from the plugwise stretch
my python is really bad, so I can’t solve it myself, I could extract the /core/ pages or others if that could give a jumpstart

No, that is not planned. But you should be able to use the Plugwise Plugs component

The stretch is not a stick but network enabled, I Will first try to locate my old smile p1 to start with it