Schneider claim a 5 year battery life so how do they explain the battery level dropping to 66% after 2 days use?
Can they also explain why this behaviour has only started since the update from v1.6 to v1.7?
I have concerns about the level of support that Schneider are able to provide when I am told that HA gives more status and diagnostic information than Schneider can see on their system.
Iâm going to do some more testing before I go back to them.
First one - I have connected them all to HA va Z2M. 2 units reporting 94% battery, 4 units reporting 93% and 1 reporting 92%. As they were all new at the same time that pretty much on the nose.
Iâll leave them connected and logging for a while to see if the battery % is logged as expected or not.
Iâll also try other brand new batteries in Z2M and again in Wiser and see the outcomes of those tests to rule out the batteries themselves.
Update:
So 24h in and weâve had no apparent issues with the battery levels in all 7 sensors.
The 2 that were at 94% are now both at 92%. Of the 4 that were at 93%, 2 are now at 91% and the other 2 are at 90%. The 1 at 92% is now at 91%.
Im not too concerned at actual drops as the calibration of the voltage > percentage may be off or the batteries may drop initially a lot faster.
Im going to respond back to Drayton with this info, the fact my other similar sensors with the same batteries dont react the same way, and the fact mine didnât exhibit this behavour until the firmware update and see what they respond.
Just to add to the evidence. Hereâs the battery info for my brand new Temp/Humidity Sensor running V1.7.5 firmware. It seems to have a period of almost exactly 90 mins, which is too regular to be simple coincidence
Since I swapped out my hard wired Synology RT1900ac Access Point for a new hard wired TP-Link WA1201 AP, sat about 0.5m away from my 2nd Gen Hub, I have had a solid Hub connection for 75 hours now and counting.
I set up the WA1201 with a brand new, unique, never before used, 2.4GHz only SSID, to ensure that none of my kids/grandkids devices could remember and attempt to connect to it. The WA1201 also connects my four ESP32/ESPHome devices, which have always had a rock solid WiFi connection, unlike the Hub.
I have had an ongoing conversation going with Wiser about the Hub WiFi dropouts, but theyâve never been able to tell me anything I donât already know, so I donât think whatever cloud diagnostics they have amount to much.
The case I opened with Wiser has got a few more days to run, so hereâs hoping the new AP has it nailed.
I installed my 2nd gen hub today. The hardest part was the physical fitting to the wall - not just the changed screw hole positions (this piece of wall already had a lot of holes in it!), but I also found less space inside for protruding cable to be accommodated, and I had to shimmy out the backplate from the wall to allow the unit to fit on (wall not perfectly flat). After that it wasnât too hard!
I was disappointed that the new hub was, if anything, less willing to pair with my smart plugs than the old one. I have a large old house and busy airwaves! I had to move both of my plugs closer to the hub to get them to connect, although they are now doing their job of hosting most of my TRVs and RoomStats - although I have to say the selection of host seems bizarre to me, with many TRVs making an odd choice of unit to connect to.
The other thing that caught me out was restoring my schedules: I have some neat scripts for saving and restoring these, with different season settings - but I rely on the schedule Number (1 to 16) and the Hub only created one schedule per room. I just had to manually create the required schedules, rename all of them, and let my scripts do their stuff.
I was perhaps slightly disappointed that they didnât take the opportunity to allow more than 16 schedules to be defined in the hub - Iâm bumping up against that limit at the moment (and, no, storing infinite schedules in HA doesnât avoid that problem - itâs an absolute requirement for me that the system continues to be usable even if HA goes up in smoke).
Now I just have to deploy the new room sensors, and then sit back and wait to see if the dropout issue is solved! Thanks to all for the info on this thread, its been very helpful.
That pattern looks eerily familiar!
Iâve ask Drayton to not raise it as a âFeature Enhancement Requestâ but as a bug and they have agreed to. Fingers crossed someone looks at it and see a silly mistake they can sort.
Just to add, I have three of these Temp/Humidity Sensors all on 1.7.5, doing the same thing. I note that my three are NOT in sync with each other, in case that helps eliminate an external factor.
I get an information from the french support, this can happenned if you hub is not paired to a cloud account.
I had to replace my hub Gen2 by another one , I create my wiser configuration as an integrator (all my devices were integrated) but my hub is not paired with my account ( the dead hub still stay paired to this accountâŚ)
Our integration works fine, in local (thanks for that it then the only way to have a remote control on it
Other consequences, no external temperature, so no seasonnal comfort for shutters, no energy management, no IA no smart schedulesâŚ
So it is a bug that needs fixing! Did they give any indication on when they will fix it?
I decided to leave the existing wiser account and created a new one so that I can run them in parallel and migrate slowly rather than delete everything.
So does the HA integration support more than 1 hub, any reason why I cannot add them in parallel and phase the old one out ?
It has discovered the new hub but I have not yet added it
Ok, the answer is yes. thought it would but just added it, so now I have old and new hubs connected.
My 2nd Gen HubR (Firmware V4.40.15) is paired to my Cloud Account, but I still donât see an entity named wiser_daylight_saving anywhere in either the Wiser App (V7.2.1 Build 204098) or Home Assistant Wiser Integration (V3.4.16)
Also, my HubR has now been continuously connected to my TP-Link WA1201 AP for nearly 13 days now, so I think for me at least, upgrading my AP and configuring it as I have has sorted things for me.
The daylight saving option is no longer a requirement.
The hub gen2 get its geoposition , so with this information it calculated the local time and the wiser_daylight_service is no more provided.
I have a 2nd gen hubr with temperature and humidity sensors. I noted from a previous post that someone raised an issue where the temp sensor doesnât connect to a wiser plug however from my observations the sensor will connect to a wiser plug but this integration doesnât indicate that it has connected on the Wiser Zigbee Network map. Is this an intergration bug, a bug with the hubr firmware or am I wrong? My reasons for this is that I have a sensor that always reported a poor connection but now that I have installed a wiser plug nearby the sensor reports a very good connection, if I switch the plug off the sensor reports a poor connection again.
Can you open a github issue and provide a diagnostic download when connected to a smartplug so I can determine which of the possible issues it is. Thx
GitHub issue raised.
So the answer is that the hub does not provide that info for these devices. As they are zigbee, i would imagine they will connect to the best router in the mesh as per std zigbee functionality, however just no info from the hub to help draw the map on the zigbee card.
I wonder if we will see that all v2 devices will not report this.
Thanks for the file.
So this is something that Schneider need to fix. Thanks for looking in to it.
Do you know if the same applies to the Smoke Detectors?
I installed 3 over 4 weeks ago and one is still showing a -89dBm signal strength despite being about 10â away from a Wiser Plug and it has never changed.
Since changing to the v2 hub I have 3 valves with very poor connections -92dBm, -87dBm and -86dBm. The -92dBm one used to connect to the v1 hub at between -75dBm and -80dBm.
Iâve tried following the Wiser Plug instructions to make devices use it as a repeater instead of connecting directly to the Hub but it hasnât made any difference.
From my experience it appears that the Zigbee mesh routing appears to be broken, or at least not working very well, on the v2 Hub.
Unless Iâm mistaken all the devices have the latest firmware installed.
In my expereince, also noted earlier in this thread, the v1 hub wasnât great at Zigbee routing either.
I added a Wiser plug some time after the initial installation and a couple of radiator thermostats moved to use it, giving a better signal strength.
Some time later, the âroom display thermostatâ moved to it also.
At some stage, the supply was inadvertently switched off to the Wiser plug and remained off. The radiator trvâs eventually moved back to the hub. The room display never did. It had to be forced to, by removing and re-installing its batteries while locating it close to the hub. I did a further test on this situation and it was repeatable. The room display refused to go back to the hub even when moving it close to the hub unless it was âre-bootedâ by a battery removal.
