From Newsgroup: rec.sport.rowing

<div>I installed one of my switches today and was able to update it to the current Beta FW Update. So far things are working as expected. I have noted that the time it takes to actually enter the switch from the Home Menu takes a bit longer on an Android in comparison to iOS. However, using it from the Home Menu is quick from either.</div><div></div><div></div><div>I am working with another Forum Member to see if he can get his switches functioning as they are supposed to. He had an issue with his Doorbell Pro as well. We are testing to see if it could be related to the iPhone. He redid his Doorbell Pro using his Android device, and it is now functioning as expected. I will let you know what happens when he tries setting up his switches via the Android as well.</div><div></div><div></div><div></div><div></div><div></div><div>download switch firmware</div><div></div><div>Download File: https://t.co/spIff8A2RS </div><div></div><div></div><div>It is version 2.26.21. I connected my third switch, and it connects to my router but will not download the firmware. I still need to try my iPad. I talked to the support desk and went thru all of their tests with no success. They said there will be an update to the iOS app by the end of the week. Give it a try and see if that works.</div><div></div><div></div><div>I have two Wyze switches installed and they connected correctly. Problem is that the additional controls I setup all of a sudden quit working. Th e switches work fine except for the additional controls. I rebooted the router with no success. will retry power down and back up to see if that works. Any help would be greatly appreciated as I have another 4 switches to install. Thanks in advance,</div><div></div><div></div><div>I had the same problem. I had a second plug and I set it up, and I was able to update the software without any problem.</div><div></div><div>I plugged the first plug back in. I reset the plug (Hold power button down for 5 seconds) and I did this 3 times. You can hear the plug switch on and off.</div><div></div><div>I then set up the plug as if it were a new plug. It notified me that there was a software upgrade and I was then able to upgrade the software without a hitch.</div><div></div><div></div><div>Last weekend we upgraded our switches (MS425 / MS220) to the 9.32 firmware. Most of our switches are part of switch stacks (with stack modules or flexi stack configuartions) and I noticed that after the firmware upgrade all the switches in a stack rebooted at the same time. I was on the assumption that the switches that are part of a stack never rebooted all at the same time but one-by-one so redundant links from my server clusters and storage would stay up and running.</div><div></div><div></div><div>I also asked Meraki support a to send me a report with the exact time of when the switches did reboot (Dasboard is not able to give the precise time). Think of a 'show version' in Cisco classic equipment. Again, they were not able to provide this.....Do you have any tips trick how to obtain this?</div><div></div><div></div><div>Hey Team, Support is now aware of this issue and actively investigating, and seems to be limited to 220/320 models that have been running for a long time (long uptime) and when upgrading from a 9.x firmware. You should see updated release notes shortly on this. But for now, if you need to upgrade, the best way to mitigate this issue is simple but involves a double reboot. Simply do a reboot of the switch prior to the actual firmware update (so you're first rebooting it with no changes and existing firmware), and then proceed with the firmware update like normal (which will download the firmware and reboot the switch into the new firmware). Please do open a case with Support to assist with properly tracking and resolving this.</div><div></div><div></div><div></div><div></div><div></div><div></div><div>The firmware issues is definitely not resolved. On this round of updates to my MS320 switches from 9.30 to 9.32, all but 5 of my switches had to be manually rebooted post deployment in order for the firmware to update. I thought last Friday's snow day was a great day to update all the switches. I was very wrong, since that required me to come in anyways and go closet t closet pulling power to switches until they were all updated and back online.</div><div></div><div></div><div>The inovelli red series dimmer (LZW31-SN) has firmware updates available. Reading their page here ( -to-s-general-how-to-update-firmware-z-stick-z-wave-pc-controller), it says I can update it via usb z wave stick but that requires excluding each switch, updating firmware, then including back in hubitat. I did some reading on adding the z-wave stick (aeotec) to hubitat itself, this is where I get confused. Does hubitat use that stick to then do the firmware upgrading? Is there anyway to upgrade the firmware without having to exclude/include?</div><div></div><div></div><div>I've also been following along the Inovelli firmware updates. Its currently in beta but apparently they're working on an over-the-air process. I would wait for that personally as I currently have 13 of these switches.</div><div></div><div></div><div>I've been using a Silicon Labs z-wave usb stick and Silicon Labs PC Controller for updates. You don't need to unpair the switches. Just set up the stick as a secondary controller. It works pretty fast and you don't have to fuss with any Hubitat driver changes or pairing/unpairing.</div><div></div><div></div><div>I was thinking about updating the firmware in my Inovelli Red switch, but I realized I should know what version I already had, which led me to the Hubitat Basic Zwave Tool... But from the version report I see nothing like the Inovelli firmware numbers. The current firmware is 1.17 (beta) so I would expect to see a version number the same or less, somewhere in the log. What am I missing?</div><div></div><div></div><div>That looks like the Hubitat-provided driver. You may want to grab "Inovelli Drivers (Gen2)" from Hubitat Package Manager (HPM), which is Inovelli's custom integration code and what I'm using with the Red Series switches.....</div><div></div><div></div><div>If it fails for some reason, you can try to manually restore the settings. Open the configuration file in a text editor and copy all the settings. Open a CLI session with the switch, if you see the prompt > type enable and login with manager credentials then type configure terminal. The prompt should change to something like</div><div></div><div></div><div>You don't need a license to unlock any features on Aruba 2530. But you should keep in mind that 2530 are positioned as Layer 2 access switches. For this reason they lack a lot of features which can be found in Aruba 3810 but this is by design and cannot be changed with a license.</div><div></div><div></div><div>Firmware downgrade is possible. The switch has 2 flash partitions for firmware, also known as firmware banks -primary and secondary. The switch can be booted either with the firmware version in primary or secondary. Both firmware banks can contain different firmware versions which makes a downgrade very easy. For example you have the old version in primary and you upload a new version in secondary. You upgrade the switch by booting from secondary (CLI command boot system flash secondary). If you notice that the switch doesnt work as expected the downgrade is simply a matter of booting the switch from the primary flash where the old version is still stored (boot system flash primary). Of course if you need to downgrade to a version which was not used before you have to upload it to one of the firmware banks.</div><div></div><div></div><div>I can confirm that the switch doesn't use separate files to store VLAN database (vlan.dat files) if you mean that. The whole vlan configuration is stored in the configuration file along with all other settings. (Only the local admin credentials are stored in a separate file by default but this can be changed)</div><div></div><div></div><div>However the VLAN name is not a parameter used in the copy command. I can only speculate that determining the VLAN in which the TFTP server is operating is only necessary in order to make sure that the switch has Layer 2 and IP connectivity to this VLAN.</div><div></div><div></div><div>We don't have a plan to include this in the AM64x SDK. The Ethernet support is up to 5 ports in parallel, of which 2 can be wire rate switched (CPSW3G) at 1G with IEEE802.1Q-2018 support. The other ports can be used as 1G Ethernet MACs, or in pairs as industrial protocol with switching.</div><div></div><div></div><div>Theoretically an approach like -dl.ti.com/processor-sdk-linux-rt/esd/AM65X/08_02_00_01/exports/docs/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/PRU_ICSSG_Ethernet_Switch.html could be enabled on AM64x to enable a second switch. Does your use case need two gigabit Ethernet switches?</div><div></div><div></div><div>we also have use cases where we need the option to use the AM64 ICSSG as 1G/100Mbit switch. In our use cases it should be possible to use the same hardware to offer industrial protocols, 1G Ethernet MACs and 1G/100Mbit switching on the ICSSGs. The use of different FW for the ICSSGs, fieldbus stacks, etc. is managed by our software.</div><div></div><div></div><div>The Linux SDK plan is as I stated limited to CPSW3G, the switch support as a switchdev API as documented in -dl.ti.com/processor-sdk-linux-rt/esd/AM64X/latest/exports/docs/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW3g.html?highlight=switchdev#multi-port-switch-mode and a demo is in -group/processors/f/processors-forum/1009997/am6442-linux-time-sensitive-networking-on-sitara-processors-including-am64x .</div><div></div><div></div><div>I need to do a firmware upgrade to my SG200 switch. My current version is v 1.1.2.0. It's my understanding that I'll need to upgrade to 1.3.5.58 before going to 1.4.1.03, which should be easy enough. My question is with regard to the order of the upgrade files. Should I be upgrading MIBs_Sx200_1.3.5.58 before Sx200_FW_Boot_1.3.5.58? Are these firware images, boot code, or language files? Also, am I able to do these updates vie HTTP or via TFTP? I just want to be sure that I get it right. If I crash my company network it won't be pretty. I'm familliar with doing firmware upgrades on many different devices but switches are a little new to me. I appreciate any direction that you can offer.</div><div></div><div></div><div>After accessing the switches interface via browser (192.168.2.10), I go to Maintenance\Update-Manager, I select update-method = HTTP, browse = p.1.20.stk, update-type = code, Image = active, followed by download, nothing happens</div><div></div><div></div><div>I have several LZW-30 black on/off switches running firmware 1.11 that I am struggling to update to the latest firmware using my hubitat C-5 hub. I have tried both the Binary Firmware Updater and the legacy one. I am using _1.22.otz as my firmware link to download.</div><div></div><div> 9738318194</div>
--- Synchronet 3.21a-Linux NewsLink 1.2