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.
