Hi and thanks for developing the plugwise integration!
I have an (ancient) plugwise stick plugged into my Odroid N2+ that runs HA. When I install the integration I select stick and then it’s asking me for the USB Path. How do I figure out what my USB Path is? I’ve tried the default /dev/ttyUSB0 but that doesn’t work.
I’ve also tried ha hardware info in the terminal, but I don’t see USB devices listed there. Do I need to do anything to get it to recognise the USB stick?
I suggest looking at and using the /dev/serial/by-id/... or /dev/serial/by-path... options, these will always stay the same after a reboot.
You need to check these paths from outside HA, in Linux itself.
Thanks, I’ll have a look at that.
hi dev’s,
should the select entity already be available in the dev nightly and core integration? Currently running 2022.4.0.dev20220324
I believe to have seen it being merged, but still I dont get that entity in my integration panels. Or is it still only in the custom component?
Hi Marius,
It should be in dev, the PR has been merged 3 days ago.
Please note, it will only show when you have more than one Schedule defined, if there’s only one, there’s no selection possible.
ofc… that was it, I only had 1 schedule. fixed that:
nice, thanks!
guess Ive got to make a more definitive choice with naming to pick Dutch/Schema or English/Schedule…
Available schemas will be depreciated in a future release.
The available options are can now be found as the options-attribute in the select-entity.
ok, I see, will that be happening to the others too?:
I simply templated these out of the core entities
Now that you show it like that, yes, it might happen for Preset modes, these could also be made selectable.
But not for Hvac modes, these belong to the climate domain and can be changed via the climate-card.
btw, I now remember I have this too:
- unique_id: front_room_thermostat_current_preset_mode
name: Current preset mode
state: >
{{state_attr('climate.front_room','preset_mode')|replace('_',' ')|capitalize}}
icon: >
{% set mode = state_attr('climate.front_room','preset_mode') %}
{% set icon = {'Temporary':'mdi:gesture-double-tap',
'Regulier':'mdi:check-circle',
'Manual':'mdi:gesture-swipe-vertical',
'away':'mdi:home-export-outline',
'vacation':'mdi:beach',
'asleep':'mdi:bed',
'no_frost':'mdi:snowflake'} %}
{{icon[mode] if mode in icon else 'mdi:home'}
not even sure these Temporary, Manual and Regulier are still possible, but I must have added them for some reason a long time ago… need to check the source code for those.
yep, its like with the simple_thermostat:
my templates were simply made for checking the possible options in the integration, not doing anything else
Update: no, presets can be set via the climate-card, they will stay as they are.
haha ok, no worries, I take it you mean the more-info on the climate card:
guess the only thing ‘in need’ of some love is the formatting of those selections. Underscore, user/lowercase. It could be a bit cleaner imho.
thx!
HA Core has matching climate presets for Home and Away.
Plugwise preset asleep could be renamed to match HA Core preset sleep.
But preset for vacation and no_frost would need to be added to HA Core.
Thanks Bouwe, I got it sorted now.
Plugwise-beta RELEASE v0.22.0
Various bugfixes and a few new features:
Please note:
Question I couldn’t find in the documentation: How can I add more circles to the Plugwise integration? At the moment I have 3 circles connected in HA, but I have 5 plugged in.
Do I need to connect them to the stick in Plugwise Source or can I edit something to add the serial numbers?
Factory-reset each of them. After that they should connect to the available Stick automatically.
Brilliant, worked a treat.
For reference, if anyone else has an ancient circle plug and needs the reset produre: 2 seconds ON, 2 seconds OFF, 2 seconds ON, 2 seconds OFF, 8 seconds ON, 2 seconds OFF. Then it has been reset.
Thanks so much for this project!
as noted in the #beta, the select entity is acting up… could also be #dev
even though I have 2 Schema’s, Regulier and Gast, the integration only sees
It was alright as you can see in Plugwise core and custom_component - #206 by Mariusthvdb, and the select entity was available before.
