any news on ticket 86567 (regards bug which hides low battery notice if sensors are grouped)? I tried to raise my own ticket, but wyze have changed the way tickets are raised, i literally couldnt get past the bot interface to submit one,
No, I have not received any information other than being told that it was sent in to the developers, and the devs donāt typically respond to anything. In cases like those we might sometimes get a person to respond in the forum itself, but even that is not common. In this case, I have not heard anything.
In fact, if anything, the situation got worse since I told them all about the issues. They did an update to the sensor GUI, and I have had several sensors go to low battery without any notices at all. Last I checked, sensors in groups wonāt even show in the GUI that they are low battery at all even when you pull them up, but even sensors out of groups wonāt send notifications anymoreā¦but they will show you when they are low if you select them and look at them.
Luckily I caught my low batteries in time (one stopped working but didnāt brick yet, and another I noticed the low battery flashing in time, and another I saw in the app that it was low, but wondered why I didnāt get notifications like I used to). I should probably send another ticket about the new GUI screwing everything up the low battery notifications (I took screenshots to show the issues), but I havenāt yetā¦felt too exhausting too do all over again.
Iāve started using HA to monitor the status of the batteries in all my sensors. HA now notifies me when a battery is getting low since Wyze no longer does.
Donāt you have to have them running solely through HA and not Wyze anymore for that though? I eventually want to do this with these V1 sensors, but for now I still need them to work through Wyzeā¦at least until the V2 sensors come in.
Still connected to Wyze cameras. There is a HA integration for Wyze bulbs, switch, and sensors which allows you to access some Wyze devices via HA.
This one?
I didnāt realize this, I thought there was just a link for HomeKitā¦but since I am not an Apple fan (Iāve never even owned a single Apple product), I havenāt looked into anything that mentioned Homekitā¦if there is a link for Home Assistant stuff though, I would be very interested in looking into that. Can you elaborate @mag.gallardo ?
(granted, ultimately Iād like to switch everything over to be local only, but until then, a HA bridge to work with Wyze through the Wyze servers is a GREAT option in the meantime).
I use this one also in homeassistant ⦠it DOES Work.
Have WYZE plugs and bulbs working in HA.
My WYZE motion sensors are up for sale on e bay.
I replaced the door and motion sensors with Aqara products
I am still a WYZE fan. I have 2 packs of the color bulbs on order.
Chas
Whyād you pick those over other options?
Well, I also use Sonoff plugs.
But to test the waters I bought an Aqara Kit from Amazon, which included the Hub, A Motion Sensor, A window door sensor and a switch. Probably best to buy from Amazon since you get the US Version of the Aqara hub. You can use this keeping all info local⦠not going to the cloud.
Every thing went smoothly, So I put in with a large order of Aqara items from the SONOFF Direct store on Aliexpress. com Soooo much cheaper. Same stuff. You just have to wait a month.
Placed my 2nd order last week from them.
In my opinion, Home Assistant isnāt for the faint of heart⦠it takes some playing around, but i think a lot of us on here do just that !
Chas
I was able to execute this tonight with no soldering just the clips. Thanks! Now to buy another battery for this device before it bricks itself again.
Hi everyone
Iām just wondering - did anybody here recently manage to re-flash any v1 contact sensors using the CC1310 Launchpad Board? I followed the detailed steps described by exeljb in post no. 102 but no matter what I try in Uniflash (e.g. āmore infoā, āerase flashā or āloadā) I get one of two errors: "Error connecting to the target: (Error -2131 @ 0x0) Unable to access device register"
or "Error connecting to the target: (Error -242 @ 0x0) A router subpath could not be accessed"
. cjtag ātrafficā is seen on the leads coming from TCK and TMS pins on the CC1310 Launchpad Board so I presume thereās an issue with the sensors. I have two further questions related to this:
- Is there any way to tell if the sensor(s) to be reflashed correctly entered the āfw load modeā?
- Is there a specific reason why the āsmall white plastic meltā inside the sensor āneeds to be removedā, apart from allowing the PCB to be taken out of the plastic case, to get better access to the pads? As in, is this step really necessary, is it the one that puts the sensor in the āfw load modeā? (I donāt expect it does but I need to ask because I canāt see why itās not working with the magnet, as described in post no. 102)
Many thanks!
Ok, so if anybody will bump into the same issue in the future - in my case it was the Windows firewall that was the cause of the errors (!). For whatever reason it needs inbound access for the flash process to work (!). Once I allowed that I could reflash the 2 sensors and they are both working again now. exeljb, your 2 pictures and step descriptions (post 102) were helpful, is there a way I could buy you a virtual coffee or something like that?
Itās nice that thereās a process by which to bring the sensors back to life my question is right now I have a number of the V2 cameras that ceased to function After a firmware update nothing but a yellow light.
I have tried downloading previous versions of the firmware to no avail so what choices do I have and what process might I be able to use to share this problem and bring these cameras back to life
Iād definitely contact Wyze support for this as your v2 cameras should still be covered by the warranty. Thereās no need to mess around with jtag.
Hey buddy, go to this thread and mention the update caused this. They have been offering to replace them, and may do so for you as well:
Or just PM bzhu or WyzeXuLi and tell them you have the solid yellow light issue after the update.
Hi @dannutu. Iām getting those same errors you got (-2131 and -242) and I canāt seem to flash any contact sensors. Can you provide any more details about what you did to fix it? My Googling hasnāt turned up anything useful.
But what if all your sensors stopped working on the same day, batteries are good, with existing or new batteries trying to re add them you get the expected three flashes and it still times out even if sensor is set right next to camera with usb bridge?