Purchased some of these beauties, https://www.amazon.ca/Wyze-Wireless-Camera-Android-Version/dp/B076H3SRXG/ref=sr_1_3?ie=UTF8&qid=1541290010&sr=8-3&keywords=wyze, for the house to replace my way more expensive - but dead - IP cameras. With the addition of a small/cheap 4-16GB SD card and an awesome hack from https://github.com/EliasKotlyar/Xiaomi-Dafang-Hacks, I can link them to my existing home PVR. I've used Sighthound for years https://www.sighthound.com/, but you don't need to have any software to use these cameras with with Duet Wifi. All you need to do is extract the folder 'firmware_mod' from the Dafang zip file to the root of your sd card. Edit the file \config\usb_eth_driver.conf.dist and add your SSID and password (only 2.4 Ghz). Rename \config\usb_eth_driver.conf.dist\ to \config\usb_eth_driver.conf. That sets up your Wi-Fi connectivity. Once you figure out the cameras IP just enter it into your browser http://www.xxx.yyy.zzz, you will be prompted for the user name 'root' and password 'ismart12' - all lowercase. You can, and should, change the password straight away. Monkey around with the settings but make sure under the camera controls you have RTSP h264 server running. Probably don't need to change much. Then go to your Duet W-Fi under Settings / User Interface enter this for the camera address https://www.xxx.yyy.zzz/cgi-bin/currentpic.cgi - replacing www.xxx.yyy.zzz with the camera IP. Set the web cam update interval to your liking, mine is set at 1 sec. Save your settings and when printing the job status window will update with an image from your camera based on the update interval you entered.
The cameras will also work, generally, in low to no light, I forgot where i got the info but think it just needs a file in the config folder called 'autonight.conf.sw' and all it contains is '-S'

Interesting, turning it off seems to have done the trick. However turning it back on doesn't make it jump any more. Will see how it goes and report back

@Foden Happy Days!!! Was able to apply the 3.2.2 upgrade and it applied OK. Wifi showed as connected but not able to connect to it just yet. Will reset and retry that shortly

@fcwilt BLTouch was working great, just bugs me that I can't get the Piezo to work for better accuracy. THat is back on so will re-calibrate and leave it now

Thanks again everyone, my DuetWifi and HEVO are back in sync. Have put back my BLTouch to replace the Orion as it was ticking me off, once i get some better prints I mat put it back.

BLTouch is now dialed in and I just need to tweak the prints to stop extraneous links between parts - another self inflected issue I'm sure.

Not replacing the cracked carriage until it fails completely - it's a royal PITA replacing it and setting up again IMHO

Have made note to self that whenever I monkey around with the hotend and/or carriage I run an autotune, fan on fill, before i do anything else ;o)

@Phaedrux Hi

IP was correct, cache was cleared and tried different browser - also tried different PC completely - no go. Left everything switched off for a few hours then powered it up and left it alone for 15mins. Bingo - able to connect to it via the web - no idea what the hell that was all about. Powered it off/on a few times and each time all good.

@fcwilt Nah, likely its me - I've been known to be defective before ;o). I have 2 Orions and 2 of the previous PCB's and have never been able to get the consistency i have with the BLTouch

@danal Noticed that myself awhile back but didn't see your post until now. My fix, workaround really is to open a browser and go to the cameras IP. It will prompt for username & password and then show you what it sees. No surprise there, however - go back to the web page your Duet is on and you will be happy to see the camera view will now miraculously work!

@Phaedrux Hi

IP was correct, cache was cleared and tried different browser - also tried different PC completely - no go. Left everything switched off for a few hours then powered it up and left it alone for 15mins. Bingo - able to connect to it via the web - no idea what the hell that was all about. Powered it off/on a few times and each time all good.

@Foden Hmm. Duetwifi reports it is connected to Wifi, as does my router, but I cannot connect to it via it's IP address

Going to switch it all off and walk away for a bit as my brain was obviously in DFU mode earlier and may still be stuck there

Appreciate your help guys - as always

@Foden Happy Days!!! Was able to apply the 3.2.2 upgrade and it applied OK. Wifi showed as connected but not able to connect to it just yet. Will reset and retry that shortly

@Foden I'm an idiot - in the process of detailing the above it dawned on me I had NOT pressed Erase Doing so allowed me to connect via Bossa to upload Duet2CombinedFirmware.bin
(deleted the large post with photos as it was redundant and in the way - sorry)

@Phaedrux It did say 3.2.2 but now I can't get to it via Bossa at all

Not sure what happened - tried a different card but am now NOT able to connect to the DuetWifi via USB and Bossa. Laptop shows the Duet as Com5, Bossa sees Com5 but says "Cannot connect to device on Com5"

K, will try a new card

Same error - "ERROR: Operation 3 failed after 5 retries" - Web page shows "Please wait while updates are being installed..."

Hi Phaedrux

Hope you are safe & well. Have downloaded the file again, 3rd time, and about to retry the update again

Current M122 is
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4S8-6J9FD-3S86R-9MYVX
Used output buffers: 3 of 24 (24 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73376 of which 76 recycled
Never used RAM 15168, free system stack 115 words
Tasks: NETWORK(ready,183) HEAT(blocked,308) MAIN(running,449) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:43:42 ago, cause: power up
Last software reset at 2021-01-30 13:14, reason: User, GCodes spinning, available RAM 15168, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU temperature: min 25.3, current 30.2, max 31.9
Supply voltage: min 24.4, current 24.6, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 18752, standstill, SG min/max 0/88
Driver 1: position -1152, standstill, SG min/max 0/60
Driver 2: position 2937, standstill, SG min/max 0/473
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-02-16 14:01:23
Cache data hit count 3203037067
Slowest loop: 42.50ms; fastest: 0.21ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 40.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 80640ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 10, completed moves 10, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.54ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

• WiFi -
  Network state is active
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.25
  WiFi MAC address ec:fa:bc:0b:ef:f2
  WiFi Vcc 3.44, reset reason Power up
  WiFi flash size 4194304, free heap 23760
  WiFi IP address 192.168.1.52
  WiFi signal strength -49dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0

Have a DuetWifi (v3.1.1)

Downloaded RepRapFirmware 3.2.2 upgrade and installed, as per notes, Duet2and3Firmware-3.2.2.zip through the System page of Duet Web Control. Once uploaded I was asked if I wanted to apply to upgrade and I said Yes. Web page cycled continuously looking like it was upgrading, left it for 2 mins. Checked the Duetpanel display and it said "ERROR: Operation 3 failed after 5 retries" . I clicked the X xlose gadget and the printer said 'Firmware uploaded in the top right corner of the screen. Checked the web interface and it was still cycling as though it was upgrading. Power cycled the printer and it's not very happy. Stuck saying 'Initializing' to right.

So I followed Fallback procedure #3 and uploaded 'Duet2CombinedFirmware.bin' via Basso, once the printer was reset it seemed to be OK. So I retried the upgrade via the web interface and got the same issue.

Not sure what I'm doing wrong