We need a summer mode that can be selected from automations in the Wiser app. Problem is Schnieder doesn’t appear to listen to its users so no user requested enhancements ever come to fruition. We don’t even get bug fixes!
I know for a fact that is untrue.
The reason summer mode has not been implemented is because scheduling is already complicated. You have scheduled events by hour, by day, by room, by device. Adding another element like summer/winter mode is just a step too far for most users. We are looking at how we can make scheduling simpler for the vast majority of users.
am I missing something, but does the wiser scheduler card not allow you to create multiple schedules, and assign rooms to them, you would just need to create a schedule for summer and then enable when you need to.
Spot on. The functionality to support this is intrinsic to the underlying Wiser system. You can create multiple schedules and assign a schedule to one or more rooms. Whilst HA allows you to automate the switch between schedules to accommodate summer (or any other criteria) it’s not a requirement.
For my summer need I’ve just created a simple schedule of 16C 24x7 which effectively disables the CH. and pointed my rooms at that schedule. Come September or so I can point my genuine schedules back to their appropriate rooms.
I’ve just had new central heating system complete with DW Hubr, 13 DW TRV’s and a DW Smart plug. all is working fine but I notice in HA any TRV that is connected to the hub via the smart plug is showing the batteries at 0%. in the DW app it’s correct.
Is it me have I done something wrong or is it a symptom of the connection throught the Smart plug. It’s all new to me so be gentle!
Edit…ignore this, one by one the incorrect battery 0% are changing to %100 .
Welcome to using the DW integration Brian. I hope you like it.
Recommend reading our wiki to see all the things you can do but also, please ask questions here if you need help. They’re all a very friendly helpful bunch!
You may be right but where is the enhancement for away mode to be time dependant so that a date can be set for it to automatically be disabled? What has happened about the requests for a temperature offset on iTRV’s? Both requested months ago.
On bug fixes why within the app has the relay type option been missing since v6 was released? Why is the smart plug firmware version missing within setup/devices/appliances? These are just two bugs reported months ago to Schneider via email. I know there is a Schneider community forum where some issues are reported but no one from Schneider replies to any posts as far as I have seen. Users end up talking to each other or themselves.
Hi David,
Feature requests get evaluated based on number of requests, ease of implementation, perceived value to all customers, and what is already on the roadmap. Unfortunately not all requests can be satisfied.
As for the two bugs you mention, these are fixed in an upcoming release.
Since the Drayton immersion heater solution still doesn’t seem to be available I’m now thinking about getting this instead. https://www.amazon.co.uk/gp/product/B0BTCPBQ7N/. Did you go ahead with another solution?
New Wiser App update, fix the OpenTherm boiler type selection in UI.
We have been waiting for this fix for months and the day after I raise it on this forum a new version of the app is released with the fix! The new app version also fixes the missing firmware version for smart plugs but has broken the section displaying the “name” of the appliance.
Follow up for the interested.
Turns out the hubR is DHCPing but not getting anything from DHCP.
This isn’t because DHCP server isn’t working, it appears to be because it’s connected to wifi via a devolo magic 1 wifi device (ethernet over power) which seems to interfere with the DHCP dialog.
I’m picking this up with devolo support, both the devolo devices which are used to get dhcp to/from the hubR are static IP now and should not be participating in DHCP dialogs. To be confirmed, investigation ongoing.
I would very much rather drop an ethernet line into a hubR but they don’t make one. Next best alternative is a decent wifi access point not an ethernet over power device. Despite being expensive I don’t think it’s very reliable tech.
So the hub never successfully obtains an IP when connected via that Devolo’s wifi bridge?
If rather it is intermittent, I’d be inclined to suspect wifi. The hub, like some other IoT devices, can apparently have issues with some mesh environments. AIUI the devolo is mesh capable.
I don’t have mesh and TBH my wifi issues were never that bad. More a case of irritation as to why it was happening. However my AP was deteriorating with age and gave me the excuse to buy a better AP. But I suspect the real solution, for me, was the firmware update and the more robust connectivity monitoring it brought to the hub.
I agree, the hub is sufficiently critical piece of kit to warrant an ethernet port.
I’ve begun to modify the Wiser integration to work with the hub second generation, it works with the actual integration. This new hub provides some new informations for the devices, manage new devices, new features like automations, summer comfort, electrical management (normal when you call Schneider Electric) but we loose also some data in the devices…
The backward compatibility is not guaranteed, and this is what a customer wants, needs first
When I use le log of the integration I notice that we loose some informations like:
* electrical consumption , and energy for the plugs and the heating actuators
* quality of reception of the devices
* …
@jamiebennett , is it possible to update the data provided like the first generation.
The data model is the same across the different hubs.
@jamiebennett
Here are some exemples of the differences between the two datasets
No more battery data in a roomstat …
If you want I can send you the log of the integration…
It’s there, it’s just elsewhere in the data model
Est-ce que ça va être réparé ?
The electrical data are important to manage the consumption.
Perhaps you should run a full diagnostic report to see if these missing fields have moved to an alternate location.