mmb

@fastbird1 I thought you would so I edited my post and added. But here it is again State variable /rest/vars/set/2/38/1 -> 2 is state table, 38 is variable number and 1 is the value. I have over 50 state variables and the 38th is the motion detected value. "Set" is obvious, BI is setting the value to 1 on motion - classic binary 1 is on and 0 is off So the program is watching for motion (1) and it resets the value to no motion (0) when the program finishes.

@larryllix in this configuration the video stream is just passed along to BlueIris and it does all the heavy lifting - all the features in the cam aren't really used. BlueIris powerful pro sw given its really low price.

@fastbird1 Just make sure you have the Network Module installed is all (I think it's included with Portal) you don't actually have to touch or program it, it just opens the ISY to network calls. As I noted, just create the state variable the program and and the corresponding url on BI. State variable /rest/vars/set/2/38/1 -> 2 is state table, 38 is variable number and 1 is the value Of course BI and the ISY need to see each other on the network. I found the hardest part was finding the Alert setting in BI 5. I have several friends who use this functionality and they love it.

@fastbird1I do exactly that with my BI and ISY994. Set up a ISY state variable and have a program watch it. Setup an alert (on alert) in BI like http://admin:xxxx@192.168.0.169/rest/vars/set/2/38/1 (motion_cam_detect) Have the program turn on a light (or whatever) like this... I also count the number of times it's triggered and the ISY sends me a report in the morning. I've run this for about 10 years without an issue and no false allarms as I have a trigger area set in BI.

@gviliunas thanks for the update. Zooz support did mention others reported the same problem. I still haven't received my replacement yet.

The deeper we get into Z-Wave the more I appreciate Insteon...

Finally! ?

@oberkc, maybe if @Chris Jahn could show up some screen shots and let us know what devices he's using?

Could be, I've done a lot of manual flashes and the likelihood of pooching the flash memory is definitely a concern. Hope you get yours straightened out...

@brians You can confirm by checking the log file as Michel noted and if you're comfortable with SSH.

@larryllix Very interesting, thanks for the information.

@tmorse305 You said I have version 100 of the Bios. Should I just wait for the dust to settle a little more before upgrading? I'm saying this is the expected notification of bios version before upgrading. So should you wait for the dust to settle? Up to you but it is the path forward.

@larryllix Sorry I find this thread interesting. Can you tell from the logs where your update fails? Fyi I posted my successful update above.

@tmorse305 yes, this is the full context. Tue Mar 8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0 Tue Mar 8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded Tue Mar 8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: starting forcing bios update Tue Mar 8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Tue Mar 8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Tue Mar 8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0 flashrom on FreeBSD 13.0-RELEASE-p6 (amd64) flashrom is free software, get the source code at https://flashrom.org Using default programmer "internal" with arguments "". Using clock_gettime for delay loops (clk_id: 4, resolution: 2ns). coreboot table found at 0xcfec5000. Found chipset "AMD FCH". Enabling flash write... OK. Found Adesto flash chip "AT25SF641" (8192 kB, SPI) mapped at physical address 0x00000000ff800000. Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED. Tue Mar 8 16:30:44 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios update ... rebooting [blah blah blah] Tue Mar 8 16:32:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Tue Mar 8 16:32:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Tue Mar 8 16:32:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.1.3 Tue Mar 8 16:32:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios has the correct version

@tmorse305 Don't confuse "version 100" with bios ver: 1.0.0 which is what we're upgrading from and bios ver: 1.1.3 is where we're headed to.

@larryllixI can't find any reference of the "version 100" but I see a reference to bios ver: 1.0.0 which was updated to bios ver: 1.1.3 - is this what you're referring to? Let me know and I'll have a look for it...

@JimboAutomates As an early adopter I expect a few bumps but nothing so far to worry about. I ordered mine soon after launch...

@DennisC A normal message. uftdi -- USB support for serial adapters based on the FTDI family of USB serial adapter chips. As pointed out previously do a "sudo cat /var/udx/logs/log | grep bios" using SSH to see if you updated properly.

@larryllix This is what I see in my log file referencing bios version 100 Tue Mar 8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded Tue Mar 8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: starting forcing bios update Tue Mar 8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Tue Mar 8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Tue Mar 8 16:30:00 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0 [...] Tue Mar 8 16:50:14 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Tue Mar 8 16:50:14 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.1.3 Tue Mar 8 16:50:14 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios has the correct version Tue Mar 8 16:50:14 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: OS Version 1303 Tue Mar 8 16:50:14 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: tpm2-tss is installed, checking version Tue Mar 8 16:50:14 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: tpm2-tss has the correct version 245

@Michel KohanimLooks like I'm good... Tue Mar 8 16:50:14 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Tue Mar 8 16:50:14 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Tue Mar 8 16:50:14 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.1.3 Tue Mar 8 16:50:14 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios has the correct version It would be helpful to insert this bios info in the Help About (someday?) Thanks!

@Michel Kohanim is there a way to confirm the flip to UEFI was successful? I did not watch for lights and listen for beeps during the upgrade process. But I'm on 5.4.1 and everything is working properly with left most light solid. Thanks.

Thanks I increased it to 2 seconds but I’ll leave it with gmail for now as during a couple of the reboots I didn’t think it was going to come back properly. The error and crash seems to occur on smtp Save/Test so nothing is written to the error log and the log file is just startup info after the reboot. I had the event viewer running but the user interface freezes when the ISY994 crashes which forces you to terminate the interface java process.

@Geddy the Outlook.com smtp is crashing the old ISY994 device, it's fine on the Polisy. Proper smtp settings are a challenge to get back on the ISY994 unless you do a complete power down (I discovered), otherwise you get repeated crashing. I didn't know about the Gmail account authentication so I'll be sure to do that, thanks. I'll check into Pushover, thanks again.

Thanks @Geddy, Gmail is working fine with the new 2FA bypass userid and pw. I'd be very careful using Outlook.com's smtp in the ISY as it crashes the device hard and getting proper smtp settings back to something useful was not trivial. I actually tested again just now and it indeed crashes hard and there are no log files and nothing in the Event Viewer. The same settings work fine on Polisy.

I'll look into it, thanks! Update, I created a new Gmail account and turned off less secure apps and turned on two factor then generated a new password. That worked, thanks! I still need to know what's up with outlook.com's smtp...