Feed

  • ESCAM PVR008 Auto-Tracking H265 IP Camera by Steve: I see. I’m interested because the quality and price are very attractive for a controllable camera. I was unaware of ONVIF until I just looked it up (it’s a security device communications standard, for those who don’t know). Unfortunately, I don’t have any kind of Android capability here — I’m an Apple and RasPi household. If anyone else reading this has any insight into getting this working on one of these platforms, I’d love to hear about it. Jul 6, 20:40
  • ESCAM PVR008 Auto-Tracking H265 IP Camera by Jason: Do these cameras have any cloud connectivity/app features? The product description is kinda vague but it sounds like mostly don’t. They sound pretty appealing as a local camera, but I’m always wary to put a device on my network if it’s gonna punch holes in my firewall and phone home. If they are purely local then I think I might have to order some. Jul 6, 19:46
  • Peter Scargill ESCAM PVR008 Auto-Tracking H265 IP Camera by Peter Scargill: It works perfectly in the Onvifer App on Android – that is, it produces the videos you see in the blog entry and also takes snapshots. Pan and tilt work, auto tracking works). I cannot comment on other programs like Home Assist as I’ve only tested it on Onvifer for Android. I did try iSpy on a Windows PC so far without success. Jul 6, 06:19
  • ESCAM PVR008 Auto-Tracking H265 IP Camera by Steve: Hi Pete, not quite clear on what happened — did the camera work using your Android app? Does it work in other control contexts? I’m wondering if it would work in a Home Asst or other Raspberry Pi-based situation. Jul 5, 22:36
  • BigTimer by Jakub: Peter, I am not sure how I can explain it more clearly. If timer is set to turn on on Saturdays 8AM ONLY and we have Saturday 8PM, the start was in the PAST or will be in NEXT Saturday. Jul 5, 07:21
  • Peter Scargill BigTimer by Peter Scargill: I just tested exactly what you referred to Saturday only 8am start – works perfectly. If you wish to progress this I need an exact description – version of big timer, version of Node-Red, any other relevant installation info, on time, off time, any other changes from the default settings. My (standard Raspbian Buster) installation is working perfectly as are numerous BigTimers. ‘If You set “Turn On on 8am” and “only at Saturdays”. At Saturday evening, let say at 8PM- I will be back in my office after travelling, probably by friday. Jul 4, 20:17
  • BigTimer by Jakub: Peter, I still see there a bug. (And I was asking about disappearing because I have no info that You changed Your message and/or delete mine). Jul 4, 20:01
  • Peter Scargill BigTimer by Peter Scargill: Ok, I’m done – there is nothing wrong – it is Saturday – I just set a brand new timer to TURN ON 8am – saturdays only. It is 8:29pm – and as it should, the timer says ON. Jul 4, 19:51
  • BigTimer by Jakub: (I made here another thread as previous one started to have very narrow place for text; but in fact I am talking about new issue here but connected somehow to the previous one) Moreover: If You set “Turn On on 8am” and “only at Saturdays”. At Saturday evening, let say at 8PM, You will see “Off for 12 hrs 00 mins”. What is not true. It will no turn on for next 6 1/2 days. So I expect rather “Off for 156 hrs 00 mins” or the best “Off for 6 days 12 hrs 00 mins” or at least “No action in 24 hrs”. Jul 4, 18:22
  • Peter Scargill BigTimer by Peter Scargill: Your comment disappeareed because I fixed the error in my comment above – didn’t you see? There’s no bug. Jul 4, 18:11
  • BigTimer by Jakub: strange, my comment disappeared. Anyway, if what You stated is no mistake than it looks like a bug (but I do not notice that). In my opinion, in Your case at 6pm You should see “Off for 14 hrs 00 mins” Jul 4, 17:31
  • Peter Scargill BigTimer by Peter Scargill: I changed that to Friday and Saturday as that’s what it is right now. So, 1: running all days – start 8:00am, off 11:45pm – at 6pm it correctly says “on for 5 hours 45 minutes” 2: only running on Saturday – so today (Friday) it correctly says “no action today” Jul 3, 16:59
  • BigTimer by Jakub: Let me try outline it: Two settings: 1. BigTimer set to start at 8am every day of the week 2. Bigtimer set to start at 8am every Wednesday. Suppose we have Tuesday, 8pm. 1. in the first case – we we can see, under the node, info “Off for 12hrs 00 mins” 2. in the second case we will have “no action today”. Is it clearer now a bit? Jul 3, 16:50
  • Peter Scargill BigTimer by Peter Scargill: I must admit I’m not following this at all. Jul 3, 11:44
  • BigTimer by Jakub: Generally speaking You are completely right but… when BigTimer is set to start e.g. everyday at 8AM, in this same situation (we have evening the day before start) it will tell in how many hours it will start instead of telling “no action today”. So the messages in this cases are a little bit inconsistent. Jul 3, 10:47
  • BigTimer by Simon: In my case I wasn’t usng MQTT, I just added BigTimer and set the start and end times. It only started sending messages on output 1 after I added the on and off messages (not payload, I think I replied to the wrong comment) I thought it would have worked ‘out of the box’ as such. Ta! Jul 3, 10:41
  • Peter Scargill BigTimer by Peter Scargill: The MQTT outputs must be set, otherwise there will of course be no output – MQTT isn’t mandatory – that’s just the first use case I had for the timer – the output can go anywhere you like – but with no output – nothing happens. I’ll make that clearer near the top of the blog though countless folk have used BigTimer without hitting such an issue. Jul 3, 10:26
  • BigTimer by Simon: It might be worth menitoning somewhere in the node info that output 1 will not work unless these two properties are set. alternatively default the on msg & off msg to 1 & 0 or “on” & “off”, I’ve just spent 30 mins trying to get the timer to send anything out of the first output. Jul 3, 09:31
  • Peter Scargill Argon ONE Case for Raspberry Pi 4 Updated by Peter Scargill: In response to LucaM – lets hope the company communicate w- we can get get in here and then everyone can have confidence they can fix the earliest cases. I’ve already fixed mine so now I have two (with a third to follow) all able to auto-power up without issue – I know that for sure, as always-on is very important to me. Jul 3, 09:04
  • Peter Scargill BigTimer by Peter Scargill: I just took another look – if the start time is 8am and you have selected Wednesday-only operation then of course yes on Tuesday you will see “no action today”. Jul 3, 04:00
  • BigTimer by sgillf: Hi David – I have the exact same issue, but I can’t tell that Node Red is running inside a docker container. How is it that it was running there without you knowing? I’m not sure if I have the same root issue. Bigtimer was working great for me until recently as well. Jul 2, 07:31
  • Peter Scargill BigTimer by Peter Scargill: On ther contrary I use BigTimer every day to control loads of devices – I’m the author of BigTimer – but with loads of users out there I tend not to make changes very often as it just works for most folk. Right now after months of lockdown I’m gtting ready to head off to the sun, so you can imagine my time is limited. Bigtimer works as well in Node-Red when it is loaded HA as it does stand-alone – but I’m not about to comment on HA use until I have more experience. Time starts at 0 minutes offset from midnight – 1440 minutes in a day. First output does repeat when the box is checked. Jul 1, 17:12
  • BigTimer by Jakub: Thanks Pete for prompt answer. Ad. 1. HA = Home Assistant, sorry. It is node for Node Red but I do have Node Red as add-on for HA. But what about “deploying”? Ad. 2. 8AM is start time. End time in that example doesn’t matter. 24 hour counting as a time window from now for 24 hour or as 0:00 – 23:59? Ad. 3. 2nd output is repeating (beside that example). 1st output should repeat when “Repeat” box checked. Anyway, I do see that BigTimer is not Your favourite kid now;) I completely understand and thanks for that You’ve already done. Anyway it is worth for someone to tune it to not waste Your great work. Unfortunatelly I am not skilled in this area. I will put that on issues to not loose that thoughts if someday someone will have time to work on it. Jul 1, 15:23
  • Peter Scargill BigTimer by Peter Scargill: Did you mean for HA Home Assistant? If so , BigTimer has nothing to do with Home Assistant, it is a node for Node-Red. You didn’t say if 8am is start or end time. Best use for BigTimer is in one 24 hour period. Say for example start at dusk, end at 11:45pm. 2nd output, I don’t recall stating if the second output is repeated or not. Check the two files in your installation – /home/pi/.node-red/node_modules/node-red-contrib-bigtimer – there is one .html file and one .js file, the latter will tell you. After making a backup you can of course change the behaviour. Jul 1, 14:56
  • BigTimer by Jakub: Hi, I faced another questions in BigTimer. Is it true/intended that: 1. When Big Timer is in OFF Manually mode, than HA reset and even Deploying, reset ting BigTimer to AUTO mode? 2. When it is Tue evening and BigTimer is set for 8AM and only in the Wednesday, BigTimer node is showing in NodeRed “No action today” 3. 2nd output node do not resend every minute when the OFF Msg is not set? ON Msg, Topic Msg has no this impact. best regards Jakub Jul 1, 13:58
  • Blitzwolf BW-HL2 Smart Watch by João Leitão: What faces does anyone if we can add more? Jul 1, 12:20
  • Argon ONE Case for Raspberry Pi 4 Updated by LucaM: UPDATE: They responded in the Repo. It seams that there are different Versions of the Argon One “Board” with different Firmwares on it. If someone has the old one, it wont work with Code, because the MCU needs an Update. They are thinking of a Jumper Method for that to keep “the old ones and new ones” Always On. With that said it dose not realy depend on the Pi itself. More on the board of the Argon One. Jul 1, 08:35
  • Peter Scargill Argon ONE Case for Raspberry Pi 4 Updated by Peter Scargill: Yes, good points – I mean getting the latest Argon firmware from their site – as for Pi4, I have 3 of them, none has a power issue so I can’t comment on that. Pete Jun 30, 17:58
  • Argon ONE Case for Raspberry Pi 4 Updated by LucaM: Hi Peter Scargill, What do you mean by: “latest Raspberry Pi 4 and Argon case” Do you mean the fixed one that has no USB-C Power issue? I have tried the lastest “firmware” script from the manual. But still after running: “i2cset -y 1 0x01a 0xfe” When I power off the Pi, cut the Power, give it back. Still have to press the button. Note: I have one of the first Pi4 (still with power issue) and one of the first Argon One Thanks in advance. Jun 30, 15:14
  • DrFragle and MrShark NanoPi R2S OpenWrt miniRouter – where’s the WiFi? by DrFragle and MrShark: new findings on the R2S overheating… https://forum.armbian.com/topic/14365-nanopi-r2s-overheating-and-throttling/ Jun 29, 10:44
  • Peter Scargill More Blitzwolf Blitz from Banggood by Peter Scargill: Hi Bob. I’m hoping to get one of these to play with – I’ll check with Banggood. So far I’m impressed with Blitzwolf – I have a few of their sockets and battery packs – as soon as I get my hands on the BW-SHP11 I’ll do the conversion. Jun 28, 13:30
  • Bob Green More Blitzwolf Blitz from Banggood by Bob Green: Just an update as this week I received two Blitzwolf BW-SHP11 smart sockets. I am happy to report that on 3 different UK 13A double sockets I tried them on, they cleared the On/Off rocker switches. I haven’t taken one apart or tasmotized it either but they do look well made. Sourced from Banggood. Spec is 3520 W and 16A. Input 110 – 240 VAC. 3520 / 240 = 14.66 amps. !6A is at 220 VAC. Unfortunately I haven’t got time to tasmotize them yet to investigate further. Jun 28, 12:17
  • Peter Scargill A ZemiSmart Weekend by Peter Scargill: It has been excellent – you’ll get the model from the Zemismart ads (it’s in my bedroom and I’m in the office). Thanks for that, I’ve updated the blog entry, fixed a few mistakes and it is in fact an E27 model. I must say that some Zemismart lights (E27 Zigbee) have given me grief – but not this one – it’s a little WiFi winner. Jun 27, 23:21
  • Todger A ZemiSmart Weekend by Todger: Could I ask what the model of that bulb is? And how has it been? It is indeed E14 right? It’s just the image shows a lamp which has E27 written on the label but maybe you used an adapter? Perhaps it’s this one : https://www.zemismart.com/e14-candlelight-bulb-rgbw-led-candle-light-work-with-alexa-echo-google-home-assistance-ifttt-voice-wifi-timer-control-lamp-p0054-p0054.html It seems to be on discount atm! Jun 27, 22:19
  • DrFragle and MrShark AWOW A60 E27 9W RGBW lights and Tasmota by DrFragle and MrShark: Sure, hass is not mandatory, but tasmota web gui is not good for such tests… Templates are faulty or incomplete sometimes, report them to blakadder… Jun 27, 22:08
  • Peter Scargill AWOW A60 E27 9W RGBW lights and Tasmota by Peter Scargill: You should never HAVE to use HASS. On my main setup I will not be using HASS for some time. It is very complicated as you know – anyway that is a flaw in the template – I just have to find out what it is as the settings are somewhat inter-dependent (I know, but they are just PWM – but there is an interaction for some reason). Pete Jun 27, 21:59
  • DrFragle and MrShark AWOW A60 E27 9W RGBW lights and Tasmota by DrFragle and MrShark: tasmota web gui is just for debugging or general help during setup, not to be used day by day (this is what tasmota people continue to answer when you report them something weird about the interface)… so, you need to use home assistant, for example, or mqtt topics to manage its full power… Jun 27, 19:13
  • Peter Scargill Blitzwolf BW-PSSD1 256GB USB3 SSD by Peter Scargill: Hi Eric – maybe – well, in my case, the USB C connector on the RPI4 is for power, not general USB – so – another spare lead. Jun 26, 17:51
  • Blitzwolf BW-PSSD1 256GB USB3 SSD by Eric: Dear Pete. Maybe the female adapter goes on the cable so it works C to C ? Eric Jun 26, 17:19
  • AliExpress Sinilink WIFI USB Controller by Ernst: With picture. Jun 24, 13:52
  • AliExpress Sinilink WIFI USB Controller by Ernst: After more than 45 days (probably due to corona problems and shipping from China) the pogo pin adapter finally arrived, by coincidence on the same day 2 extra XY-WFUSB units also arrived. So I immediately tried the pogo pin adapter; it works excellent. It requires a steady hand though to hold it in place for a couple of minutes flashing the ESP chip. All in all happy with it. Jun 24, 13:03
  • Peter Scargill A Better Raspberry Pi Case? by Peter Scargill: Wish I’d read that before binning the fans…. Jun 24, 11:56
  • A Better Raspberry Pi Case? by Richard: Re. Your noisy fan. I have a couple of these for the Pi3 and a couple for the Pi4. On one I found that the fan blades were fouling on the casing under where they are mounted. It was a bit fiddly but I put a washer under the fan at the four screw holes under the fan and the problem went away. Jun 24, 11:35
  • BigTimer by Spunckie: Hi Pete, thanks. I know about that. But I want to change the value during the runtime. I would like to do that in the same way as the import parameter ‘off_override’. Example: OFF-Time in the main panel = dusk offset -120. result of the Big Timer is e.g. 10:00 p.m. If I had an Import parameter “off_offset” and would set them to -60 the result of Big Timer would be 11:00 p.m. Many thanks in advance. Spunckie Jun 23, 19:39
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete Test reults for setting order of boot to USB followed by SD that is 0xf14 in config Tested each separately in USB and the SD also in its slot on rpi4 to see that they did boot 1) With SD card in rpi slot and a usb stick in usb3 lower connector The raspi4 booted every time from the USB stick 2) The same for the usb3 top connector. 3) With sd card in usb top connector and usb stick in bottom 4) The raspi4 booted every time from the SD in the usb 5) The same for reverse connectors. 6) The same when I used a Samsung ssd I did a check on Raspi documentation that has now been updated with Details for msd boot to the current stable condition. Here link https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2711_bootloader_config.md Here snipet from msd docs Multiple bootable drives When searching for a bootable partition the bootloader scans all USB mass storage devices in parallel and will select the first to respond. If the boot partition does not contain a suitable start.elf file the next available device is selected. As with earlier Raspberry Pi models there is no method for specifying the boot device according to the USB topology because this would slow down boot and adds unecessary and hard to support configuration complexity. Update the bootloader • From a standard Raspberry Pi OS SD card boot: • sudo apt update sudo apt full-upgrade • As root, edit /etc/default/rpi-eeprom-update and select stable releases. • Install the stable version of the bootloader and replace the current configuration settings to enable USB boot. See BOOT_ORDER property if you wish to migrate the configuration by hand. sudo rpi-eeprom-update -d -f /lib/firmware/raspberrypi/bootloader/stable/pieeprom-2020-06-15.bin regards Brian Jun 23, 18:27
  • Peter Scargill BigTimer by Peter Scargill: Hi there – the offsets if used are set in the main panel. Regards Pete Jun 23, 14:02
  • Spunckie BigTimer by Spunckie: Hi Pete, I like the Big Timer very much and use ist for all my time depending projects. But now have a little problem. I would like override the offset-fields via input. Obviously there is no input for this case. Is this correct or I am not able to find the right way? If it’s not possible, could you please add this possibility to the Big Timer? Thank you. Spunky Jun 23, 13:09
  • Peter Scargill More Zigbee Learning (or not) by Peter Scargill: Thank you very much – always feel free to comment or make suggestions. Pete Jun 23, 10:07
  • More Zigbee Learning (or not) by Gonzag: Ok, so it’s mainly for its low-power advantage. Nice. Thank you for your response. (And thank you for your blog, tweets and videos btw. I’m been one of these millions of silent followers you certainly have for years 😉 ) Jun 23, 09:16
  • Peter Scargill More Zigbee Learning (or not) by Peter Scargill: Hi I’m not switching to Zigbee – I’m testing Zigbee in case it is useful for outdoor or awkward positions where sensors must be battery powered. For indoors I’m more than happy with WiFi. Depending on the position of the Zigbee gateway it could make sense to have a mains powered Zigbee REPEATER which might also act as a switch or socket, hence the interest in that. As an example, door sensors are often not attached to power and I’ve been experimenting with 433Mhz and Zigbee sensors. Regards Pete Jun 23, 09:08
  • More Zigbee Learning (or not) by Gonzag: Hi, I might have missed your reasoning on why switching to Zigbee now. I will soon have to make the decision for my own home. I am wondering if using wifi for every smart sockets and other IoT isn’t going to overcrowd the wifi bandwidth. I wouldn’t want to decrease the quality of the signal for computers and other high bandwidth needs. Is this the reason you are getting interested in Zigbees? Jun 23, 08:59
  • Peter Scargill Argon ONE Case for Raspberry Pi 4 Updated by Peter Scargill: Hi SteveH – I concur and have updated the blog accordingly as well as using this info on my latest Raspberry Pi 4 and Argon case. After issuing that I2C command on the latest firmware (the CURL command in the manual), I now have a working auto-power-on Pi. Jun 23, 06:14
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete After you have run the eeprom update above check the status using a) vcgencmd bootloader_version b) vcgencmd bootloader_config your result should be similar to the attached pic. note boot order is read right to left 1 is sd, 4 is USB I tried a test on a previus version reversing the order to 14 to try and boot USB first then SD, but this failed although it tried to do it. It could have been a timing problem. I abandoned that, but will now retry with the stable version in the next few days. regards Brian Jun 22, 19:16
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete Absolute min is Change to beta in /etc/default/rpi-eeprom-update 1) sudo rpi-eeprom-update -a 2) sudo rpi-eeprom-update -d -f /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2020-06-15.bin 3) reboot The commands to check the status of what we have in the EEPROM on your rpi4 are a) vcgencmd bootloader_version b) vcgencmd bootloader_config You might have to update all depending what your OS is regards Brian Jun 22, 18:44
  • SteveH Argon ONE Case for Raspberry Pi 4 Updated by SteveH: Myles, You could test that the i2cset command is working as expected by using it to control the fan. For example:- i2cset -y 1 0x01a 0x64 This should turn the fan on at 100%. It will reset when the service cuts in every 30 seconds to check the temperature. In my experience “i2cset -y 1 0x01a 0xfe” then shutting down with “halt” and removing power and then reapplying power will boot straight back up. Reverting to the default (0xfd) then requires use of the power switch on the back again. What I couldn’t find was a way of reading back the values of any of the data/registers using i2cget. Every attempt returned the value 0xc8. Maybe that is by design. Good Luck Steve Jun 22, 11:51
  • Peter Scargill Argon ONE Case for Raspberry Pi 4 Updated by Peter Scargill: Hi Not yet. I hacked the first case to bypass power. Second case I will try using the i2c command but this is not good. Jun 22, 09:39
  • Argon ONE Case for Raspberry Pi 4 Updated by Myles: Did this end up working? I was able to execute the command but it didn’t appear to stick after power cycling. Jun 21, 22:55
  • AIdan Ruff A Better Raspberry Pi Case? by AIdan Ruff: I’ve got two of the fanless versions of these cases. They are very good and only run luke warm in headless mode. For around a tenner, you can’t go wrong. I imagine that Pete could use his thermal imaging camera to show the heat distribution Jun 21, 18:05
  • DrFragle and MrShark More Zigbee Learning (or not) by DrFragle and MrShark: yes, editing their names in the “devices.yaml” file, while hassio addon is stopped… similar if you’re using the local install Jun 21, 11:42
  • Bigted More Zigbee Learning (or not) by Bigted: My point was that there is a way to change the unfriendly name in zigbee2mqtt. Tasmota also gives devices unfriendly names that you can change Jun 21, 09:23
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete and the pic shows what is in lib directory files regards Brian Jun 20, 22:34
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete test results updating with critical in rpi-eeprom with CURRENT: Mon 15 Jun 13:36:19 UTC 2020 (1592228179) version(stable and frozen) Here is what I get running pi@raspberrypi:~ $ sudo rpi-eeprom-update BCM2711 detected Dedicated VL805 EEPROM detected BOOTLOADER: up-to-date CURRENT: Mon 15 Jun 13:36:19 UTC 2020 (1592228179) LATEST: Mon 15 Jun 13:36:19 UTC 2020 (1592228179) FW DIR: /lib/firmware/raspberrypi/bootloader/beta VL805: up-to-date CURRENT: 000137ad LATEST: 000137ad See attached file for what is in each directory run the updates 1)sudo apt update 1 package can be upgraded 2)sudo apt full-upgrade The following packages will be upgraded:rpi-eeprom 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 309 kB of archives. After this operation, 1,585 kB of additional disk space will be used. Do you want to continue? [Y/n] Result still booting from USB Found this in rpi forum STICKY: USB-MSD boot EEPROM third update – 2020-06-15 • Quote Tue Jun 16, 2020 6:06 pm Unlike previous models, the Pi4B has on-board EEPROM storage for some of the firmware (including the bootloader). So once flashed it will remain until it’s replaced by something newer, and that will only happen with a new OS install when a newer version reaches the critical update channel (default setting in /etc/default/rpi-eeprom-update). So re-installing Raspberry Pi OS should not affect the bootloader or VL805 firmware (even after an update/full-upgrade). You can leave critical in your FW directory.(with beta june 15th installed) ++ regards Brian Jun 20, 22:27
  • DrFragle and MrShark More Zigbee Learning (or not) by DrFragle and MrShark: tasmota wants nothing, you can go in its web gui and rename them as you want, then (in case of home assistant) remove the device from HA, go in tasmota console and issue again: “SO19 1” to have them back with proper names 🙂 Jun 20, 07:08
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete I am currently starting to test against the freeze on EEPROM update beta Can you please run sudo rpi-eeprom-update on your rpi4 This will NOT update anything just indicates whether an update is required and gives you what version you have, and let me know the result. regards Brian Jun 18, 16:44
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete Your reply point 2) It is /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2020-06-15.bin In my lib. I put the word file as I didn’t know your bin version. This is the bin file that is frozen and NO more changes or updates will affect it. It was loaded and ran by webmin as a update package for EEPROM 1.7.3 to 1.7.4, because I changed the FIRMWARE_RELEASE_STATUS=”critical” to beta, when I updated from 3 jun release to 12 jun release When I tested my very old sd card from Feb 2019 in rpi4 I used the critical update to reset my RPI4 EEPROM back to no usb boot. This was the April update to retest the new rpi4 EEprom config and bootloader, and to reconfirm the change to usbboot was repeatable That was before the beta bin file was stable and frozen. HOWEVER when you have FIRMWARE_RELEASE_STATUS=”critical” maybe is possible that the freeze flag set to 1 by the 15th Jun update will stop this . I do not know not having tested it, but if you have FIRMWARE_RELEASE_STATUS=”beta“ it will stop it (belt and braces) regards Brian Jun 18, 15:11
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete here is image of part of the article regards Brian Jun 18, 10:46
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete with the rpi4 we now have a completely different animal This article is about real world testing. The Pi 4 is a *serious* NAS contender. Sustained write speeds of over 68 MB/s were obtained, and over 105 MB/s for reading, including saturation of the Gigabit network. Yes, the Pi 4 can push even a 1000 MB/s network to 100%. Here is the link will interest you http://unixetc.co.uk/2019/07/07/raspberry-pi-4-real-world-tests/ regards Brian Jun 18, 10:39
  • GL-iNet Spitz 4G LTE Smart Router by Mike Weaver: And I thought it was Australia that was classed as “Treasure Island”! $212.00 (Aussie dollars) from Amazon here, which is about £117.00 currently. Mind you, still a big mark up on US price which should be about $174.00 AUD. Of course, most US Staes then have at least a 10% sales tax add-on (they never add it on the ‘shown’ price) so that would push it up to about $190.00 AUD which would include our 10% GST (VAT). So about a 10% mark up. Yeah – seems OK. I’ve seen much worse! Jun 18, 07:35
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete FREEZE_VERSION If 1 then the rpi-eeprom-update will skip automatic updates on this board. The parameter is not processed by the EEPROM bootloader or recovery.bin since there is no way in software of fully write protecting the EEPROM. Custom EEPROM update scripts must also check for this flag. At the moment until a full production release nothing will touch your EEPROM which has a stable version in it and is frozen then maybe we can write back critical in etc/default/ file regards Brian Jun 17, 23:02
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: hello Pete It means no more changes to this version. You could freeze updates to your version at any time by changing parameters. I take it that they are going to issue this as a critical version so all pi4s get this as next eeprom update. Thats MY opinion but I am not sure. What is certain is no more changes to this version, as it is stable and frozen until a production release is ready. I would agree for the raspi4 I have had no problem with the last 2 versions on my rpi4 but others have. regards Brian Jun 17, 22:30
  • Peter Scargill New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Peter Scargill: Ok, you;ve lost me Brian – is that to say a new update no longer needs the use of BETA? If not, what if anything do existing users need to do? Pete Jun 17, 21:43
  • Peter Scargill GL-iNet Spitz 4G LTE Smart Router by Peter Scargill: I did say it was up-market – mind you not THAT upmarket – the USA price is around $119 which would make it sub-£100 in the UK were it not that right now people seem to be thinking of prices and doubling them. I’m putting some more specs up for anyone interested. The Mango router was CHEAP so I’m assuming there’s a good reason for this pricing. Read on. Jun 17, 19:26
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete beta update now to STABLE Raspberry Pi4 bootloader EEPROM release notes 2020-06-17 Promote 2020-06-15 to STABLE Promote the latest beta EEPROM and recovery.bin to stable and feature freeze USB MSD support until a production release is ready. regards Brian Jun 17, 18:46
  • GL-iNet Spitz 4G LTE Smart Router by AcmeUK: Cor, £145.90 from Amazon UK! I think I will stick with a “ZTE MF920V 4G Low Cost Travel Hotspot, Unlocked to all Networks” at £34.99 from Amazon UK. Jun 17, 16:58
  • Peter Scargill Another Itead Sonoff and Week now with Zigbee by Peter Scargill: Having fun with Ikea – tried to order the Tradfri gateway and a couple of lampholders on the website – only optio is pickup “at your nearest store – “Belfast” – even the Chinese don’t get it that wrong.. I’m in the Northeast of England – not exactly “pop-in” distance for Ikea Belfast. Jun 17, 08:06
  • DrFragle and MrShark Blitzwolf BW-SS4 1-2-way Smart Switch by DrFragle and MrShark: 2 relays? the blitzwolf (itead ones have bigger cases) 1 relay? the cheaper between the 2… Pete, try the new button behaviour… 1 click turns on 1st relay, 2 clicks the second… it’s default now in tasmota Jun 17, 06:30
  • Node Red Alexa Remote2 by Patric: I also struggled to get it running and I cannot login using the proxy either as amazon says I should enable cookies (which is actually already the case). I could solve it by switching to cookie authentification and geeting the cookie by logging into my account at pitangui.amazon.com (or your desired country server) and aquiring the cookie as described here: https://www.youtube.com/watch?v=Yg7dv4OOFAY (fast forward to 12:55). Hope that potentially helps, worked for me immediately even if other methods I googled on how to get the cookie did not work. Jun 17, 06:06
  • Scott Millken Blitzwolf BW-SS4 1-2-way Smart Switch by Scott Millken: In your opinion, Sonoff or Blitzwolf? Jun 17, 01:27
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete I NOW KNOW IT is important to do the Beta change in etc/default/rpi-eeprom-update Because if at any time you do an update all the eeprom will be over written By the critical EEPROM stream update. This at the moment is APRIL 4 NO RPI USB BOOT. Remember the change is BETA at the moment when it is established it will go in critical Regards Brian Jun 16, 18:40
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete a bit like the search for the holy grail. Last note on this I had a package update for pieeprom in webmin after running it version 1.7.2 to 1.7.3 I had in /lib/firmware/raspberrypi/bootloader/beta/ a new file pieeprom-2020-06-15.bin So I rebooted my rpi4. Worked booting up on my SSD but my bootloader and its config in my EEprom on the rpi4 have been UPDATED from June 3 to June 15 regards Brian Jun 16, 18:26
  • Peter Scargill Node Red Alexa Remote2 by Peter Scargill: Talk to the designer and do let us know what you come up with Pete Jun 15, 19:46
  • Node Red Alexa Remote2 by Massimiliano: hello everyone, I haven’t been able to update or initialize the amazon cookie for a day now, after logging in it gives me back a page where it says: Please Enable Cookies to Continue To continue shopping at Amazon.com, please enable cookies in your Web browser. Once you have enabled cookies in your browser, please click on the button below to return to the previous page. please help me Jun 15, 19:14
  • Brian Gentles Blitzwolf BW-PSSD1 256GB USB3 SSD by Brian Gentles: Hello Pete changeing boot order to 0x14 does NOT work, whether you put sd card in the raspi holder or in the usb, in the end it boots from the sd card. There is a message hub1 a pause then boots from SD. It could be timeing, but as its a work in progress I will leave it to the boys in the higher paygrade. The blank sd worked in both cases. regards Brian Jun 15, 19:11
  • Brian Gentles Blitzwolf BW-PSSD1 256GB USB3 SSD by Brian Gentles: Hello Pete you could just put a blank sd in the 2nd usb then at boot the default would be sd(nothing there!!) usbssd. Works I just tried it. pi@raspberrypi:~ $ sudo rpi-clone sda -f -U Booted disk: sdb 120.0GB Destination disk: sda 32.0GB ————————————————————————— Part Size FS Label Part Size FS Label 1 /boot 256.0M fat32 — 1 256.0M fat32 — 2 root 111.5G ext4 — 2 29.6G ext4 — ————————————————————————— == Initialize: IMAGE partition table – forced by option == 1 /boot (51.0M used) : MKFS SYNC to sda1 2 root (3.5G used) : RESIZE MKFS SYNC to sda2 ————————————————————————— Run setup script : no. Verbose mode : no. ———————–: ** WARNING ** : All destination disk sda data will be overwritten! ———————–: Initializing Imaging past partition 1 start. => dd if=/dev/sdb of=/dev/sda bs=1M count=8 … Resizing destination disk last partition … Resize success. Changing destination Disk ID … => mkfs -t vfat -F 32 /dev/sda1 … => mkfs -t ext4 /dev/sda2 … Syncing file systems (can take a long time) Syncing mounted partitions: Mounting /dev/sda2 on /mnt/clone => rsync // /mnt/clone with-root-excludes … Mounting /dev/sda1 on /mnt/clone/boot => rsync /boot/ /mnt/clone/boot … Editing /mnt/clone/boot/cmdline.txt PARTUUID to use eb0bcb76 Editing /mnt/clone/etc/fstab PARTUUID to use eb0bcb76 =============================== Done with clone to /dev/sda Start – 17:08:51 End – 17:21:00 Elapsed Time – 12:09 unmounting /mnt/clone/boot unmounting /mnt/clone =============================== You could boot on ssd insert sdin usb when the system is booted all ensure boot by ssdusb regards brian Jun 15, 16:28
  • Brian Gentles Blitzwolf BW-PSSD1 256GB USB3 SSD by Brian Gentles: Hello Pete my old ssd drive was 120Gb works well using rpiclone the time taken only 5min 19secs to clone. You could try changing the boot order. Here a snip from BOOT_ORDER The BOOT_ORDER setting allows flexible configuration for the priority of different bootmodes. It is represented as 32bit unsigned integer where each nibble represents a bootmode. The bootmodes are attempted in lowest significant nibble to highest significant nibble order. E.g. 0x41 means try SD first followed by usb boot then stop. Whereas 0x4 would mean try usb boot and then stop without trying to boot from the SD card. The retry counters are reset when switching to the next boot mode. BOOT_ORDER fields The BOOT_ORDER property defines the sequence for the different boot modes. It is read right to left and up to 8 digits may be defined. 0x0 – NONE (stop with error pattern) 0x1 – SD CARD 0x2 – NETWORK 0x3 – USB device boot usbboot – Compute Module only. 0x4 – USB mass storage boot 0xf – RESTART (loop) – start again with the first boot order field. Default: 0x1 Version: pieeprom-2020-04-16.bin pieeprom-2020-05-15.bin – BETA Boot mode 0x0 will retry the SD boot if the SD card detect pin indicates that the card has been inserted or replaced. The default boot mode is now 0xf41 which means continuously try SD then USB mass storage. You could change this to 0x14 then would try cycling msd(usb) pause then SD pause usb etc upto max set tries. lots more information to change the settings in EEPROM here https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2711_bootloader_config.md regards Brian Jun 15, 15:33
  • Peter Scargill New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Peter Scargill: It gets better Brian – see my latest blog entry I’m working on now – my new Blitzwolf 256GB SSD just arrived from Banggood this morning – so fixing the USB BOO issue was SO well timed. Jun 15, 12:29
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete Glad to hear all is now good. You ran my scripts from my June 14, 2020 at 2:58 pm reply According to your reply June 14, 2020 at 4:06 pm These flash the EEPROM on the rpi4 with 1)Bootloader 2)Boot parameters These are the beta parts and can be changed at will. On the rpi3 we did this by burning a link once finished. The parameters for usb boot were held on the boot partition of the SD or usb. Therefor when we rp-clone it goes with the sd/usbstick. On the rpi4 it does NOT!! The rpi holds the parameters for usb boot in its EEPROM I think IT is important to do the Beta change in etc/default/rpi-eeprom-update Because if at any time you do an update all the eeprom will be over written By the critical stream update. Remember the change is BETA at the moment Hope this is clearer Regards Brian Jun 15, 09:03
  • Peter Scargill New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Peter Scargill: Hi Brian – you can stop. I just got to the bottom of this – the sodding USB adaptors. I took my good Pi4 sd-as-usb – put it into the pi4 that would not work, tried the SD that works as SD but not as USB and borrowed the USB adaptor I know works – and THAT worked. So from some point, it has been dodgy USB adaptors. I even put the dodgy one in one of the USB2 sockets and it STILL doesn’t work. Sadly the USB3 adaptor I KNOW works – is no longer on AliExpress’s list of available adaptors – we have Covid to thank for that, no doubt. Jun 14, 21:40
  • Peter Scargill New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Peter Scargill: All working Brian, it seems my problems were largely down to rubbish USB adaptors. I now have 2 RPI4s and an RPI3 running on USB. Thanks for persevering. Your comment June 14, 2:58pm is currently valid. One assumes that before long, someone at RPI will make this all non-beta and remove files that don’t work. Jun 14, 21:18
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete pi@test4:~ $ sudo rpi-eeprom-update -a will load the bootloader or if you have will say so your bootloader is correct. You have not checked the config please run pi@raspberrypi:~ $vcgencmd bootloader_config and let me know what you get regards Brian Jun 14, 16:46
  • Peter Scargill New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Peter Scargill: Hi Brian so many response I’ve no idea hat most are about- this latest response… I took my working (but not on USB) Pi4 – and ran the first line – result was: pi@test4:~ $ sudo rpi-eeprom-update -a BCM2711 detected Dedicated VL805 EEPROM detected BOOTFS /boot BOOTLOADER: up-to-date CURRENT: Wed 3 Jun 12:53:47 UTC 2020 (1591188827) LATEST: Wed 3 Jun 12:53:47 UTC 2020 (1591188827) FW DIR: /lib/firmware/raspberrypi/bootloader/beta VL805: up-to-date CURRENT: 000137ad LATEST: 000137ad So that’s not it…and you mentioned there a file 03 June – I’m sure earlier somewhere you mentioned a later file… anyway I used: sudo rpi-eeprom-update -d -f /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2020-06-03.bin and rebooted. I THEN looked at your previous response and followed the command there. vcgencmd bootloader_version Jun 3 2020 13:53:47 version b5de8c32f4f45a12a1fdfe107254df82965f9d56 (release) timestamp 1591188827 pi@test4:~ $ THAT says I’m running the RELEASE bootloader. How weird is that… So I repeated all of the above on a previously saved clone – exactly the same result…. – it seems I’m running the release bootloader whether I want to or not Jun 14, 16:06
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete just read your note use cloned usbbootable SD card 1)pi@raspberrypi:~ $ sudo rpi-eeprom-update -a 2)pi@raspberrypi:~ $ sudo rpi-eeprom-update -d -f /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2020-06-03.bin reboot I included all before as I might miss something usefull regards Brian Jun 14, 14:58
  • Brian Gentles New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Brian Gentles: Hello Pete This is using cloned SD card from your existing bootable rsp4 These commands are to see state for what you have vcgencmd bootloader_version vcgencmd bootloader_config WHAT YOU ARE AIMING FOR ********** 1) pi@raspberrypi:~ $vcgencmd bootloader_version Jun 3 2020 13:53:47 ******** version b5de8c32f4f45a12a1fdfe107254df82965f9d56 (release) timestamp 1591188827 2) pi@raspberrypi:~ $vcgencmd bootloader_config [all] BOOT_UART=0 WAKE_ON_GPIO=1 POWER_OFF_ON_HALT=0 DHCP_TIMEOUT=45000 DHCP_REQ_TIMEOUT=4000 TFTP_FILE_TIMEOUT=30000 ENABLE_SELF_UPDATE=1 DISABLE_HDMI=0 BOOT_ORDER=0xf41 ************* 3) update the bootloader pi@raspberrypi:~ $ sudo rpi-eeprom-update -a you should get BCM2711 detected Dedicated VL805 EEPROM detected BOOTFS /boot BOOTLOADER: up-to-date CURRENT: Wed 3 Jun 12:53:47 UTC 2020 (1591188827) ******* LATEST: Wed 3 Jun 12:53:47 UTC 2020 (1591188827) ******* FW DIR: /lib/firmware/raspberrypi/bootloader/beta ******* VL805: up-to-date CURRENT: 000137ad LATEST: 000137ad 4) now to update config for boot pi@raspberrypi:~ $ sudo rpi-eeprom-update -d -f /lib/firmware/raspberrypi/bootloader/beta/pieeprom-2020-06-03.bin reboot Check WHAT YOU ARE AIMING FOR ********** pi@raspberrypi:~ $vcgencmd bootloader_version pi@raspberrypi:~ $vcgencmd bootloader_config Hope this is clear. I will dig deeper by resetting my rpi4 to critical pre usbboot April4, and useing my winimg of my Sept 2019 Sd card will do a complete update to usbboot from scratch However it is clear that the EEPROM is modified on the RPI4 when you do the original update NOT FROM THE SdCARD The above is only to modify the newrpi4 EEPROM Then the new rpi4 will boot fromusb useing your already changed SDcard or usbstick (I hope) Regards Brian Jun 14, 14:52
  • Bigted Another Itead Sonoff and Week now with Zigbee by Bigted: Zigbee2mqtt can now update Ikea Tradri firmware, just update one device at a time otherwise you swamp the network Jun 14, 14:22
  • Bigted More Zigbee Learning (or not) by Bigted: Or you could just add a friendly name in the zigbee2mqtt yaml file for each device, Tasmota wants to call every device tasmota which is even less friendly Jun 14, 14:14
  • Peter Scargill New 8GB RPi4, USB3 Boot now WORKS on all RPi4 by Peter Scargill: Hi Brian – thanks for the great feedback – I’m fairly sure you can delete comments..,. you have put so much in here I’m not sure what to read and what to ignore – care to reduce the USB boot on Pi4 solution to one response? My reading capability would no doubt improve if the crappy Vodaphone broadband would stay up for more than 5 minutes at a time. Regards Pete Jun 14, 13:51