firstone

Can always add code by hand and remove later. But https://support.ring.com/hc/en-us/articles/204736064-Ring-App-Compatibility-With-Smart-Lock-Systems-from-Kevo-LockState-Kisi-and-Lockitron

I have 4 BE469ZP installed and added them multiple times with no issues. I cannot write user codes into 3 of them but that's a different story. Not sure if you want to try but here's what you can: ZWave -> Synchronize -> New and Deleted with Interview I've had issues with Aeon sensors not having nodes created and the synchronize would bring them up after a few tries. I think in my case interview didn't work at first.

I think either will work on polisy. I'm using it with serial port directly but no reason USB shouldn't work. I think eisy only has usb though so that's the only way.

Probably can change requirements to point to specific version? Not >=.

It's possible it's a new version from the one I have. I will give you an info command to run and we can check that way.

Plug it in, run sudo command as before. If that doesn't work, PM me log packages. Same as you've done above. Also, run: sudo ls -la /dev/u* And PM that also, please.

Do you get DSK code prompt? Do you type in correct code? Or is this lock not S2. If you type incorrect code, it will silently fail. You can maybe look in Event log for messages.

You only have to run reset if you unplug or reboot. I'm working with Michel on permanent solution. NS cannot print to ssh being that Unix is multiuser system. It does log into a log, which you can look at or send to me. I can also give you small test app to print out raw output. And you can test with Flirc UI I think. You can go to Device Log and press some buttons and see what you see.

My fault again. Fixed it on my test polisy and forgot to merge changes. Try 0.1.2. But the steps are: * Plug Flirc into PC software * Teach buttons. You don't need to save. * Plug Flirc into eISY * Rerun sudo command to reset driver. If you don't do the last step, node server will not find Flirc.

My fault. I've pushed a fix. It should be under version 0.1.1.

This I don't know for sure. I don't believe it comes preloaded with any signals though. You can try it and if you don't see any responses to key presses, just download Flirc software, load Kodi profile and tech whatever keys you like. It's very intuitive and easy to use.

Kind of looks from here you have capital H at the end? Likely saved the file with ".sH" extension. Linux is case sensitive. You an try 'ls' command to double check. [admin@polisy ~]$ curl https://raw.githubusercontent.com/firstone/eisy-ir-poly/main/reset_flirc.sh -o reset_flirc.sh % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 170 100 170 0 0 684 0 --:--:-- --:--:-- --:--:-- 688 [admin@polisy ~]$ chmod +x reset_flirc.sh [admin@polisy ~]$ ls -la reset_flirc.sh -rwxr-xr-x 1 admin admin 170 Jan 18 22:06 reset_flirc.sh

"Motion Sensor" node doesn't work for me either btw. It's always "On". But programs written based on top level node (Security Alarm) are working fine.

I've opened a ticket about this and Chris said they know about it and it's on the list. I see same problem with Trisnesor as well as multi sensor 7. It somehow changes from C to F after interviews sometimes. And sometimes not. Weird. Sensor clearly sends F but IoX creates degrees in C and so does a translation.

It's not a generic adapter but that very particular one. Although Flirc gen 1 can be used as well. The way it works is you teach Flirc RC commands. You can use Harmony with any code set or any other remote or code set. Flirc will act like a virtual keyboard. Node server will then create a Node for a key that you can use in your programs.

I've released eISY IR node server into beta. It adds IR receiver functionality to eISY / Polisy using Flirc IR USB receiver. The only caveat you need to run some commands over ssh to set permissions to Flirc. Feel free to test it out and see if it works for you.

It looks great. I think UDI should sell it.

I could see Z-Wave chip going into some state. But not connecting, almost seems like it died. If removing power doesn't fix it, I don't know what will. Check /var/log/messages, see if you can find something. Here's what it looks like when I pull ZMatter USB out: Jan 8 15:42:45 polisy kernel: ugen0.2: <Silicon Labs CP2105 Dual USB to UART Bridge Controller> at usbus0 (disc onnected) Jan 8 15:42:45 polisy kernel: uslcom0: at uhub0, port 3, addr 1 (disconnected) Jan 8 15:42:45 polisy kernel: uslcom0: detached Jan 8 15:42:45 polisy kernel: uslcom1: at uhub0, port 3, addr 1 (disconnected) Jan 8 15:42:45 polisy kernel: uslcom1: detached Jan 8 15:44:27 polisy kernel: ugen0.2: <Silicon Labs CP2105 Dual USB to UART Bridge Controller> at usbus0 Jan 8 15:44:27 polisy kernel: uslcom0 Jan 8 15:44:27 polisy kernel: on uhub0 Jan 8 15:44:27 polisy kernel: uslcom0: <Enhanced Com Port> on usbus0 Jan 8 15:44:27 polisy kernel: uslcom1 Jan 8 15:44:27 polisy kernel: on uhub0 Jan 8 15:44:27 polisy kernel: uslcom1: <Standard Com Port> on usbus0

When Insteon originally came out it was I1 engine. Links had to be written one byte at a time, etc. When I2 came out, which is all of current devices, it was a huge change in protocol. If i3 devices are slightly different, it's one thing. But if it's new Insteon engine and requires a huge change in IoX code, it remains to be seen if UDI will want to support it, especially, given limited number of such devices at this time. A node server could be potential solution but Insteon protocol, with linking, etc is not for a faint of heart. Also, not sure how it could co-exist with current Insteon functionality in IoX.

While it's certainly annoying, you technically paid for production device (with Beta software/firmware) 😀 At least I think they were upfront about it. Give it time, it will settle down eventually. For my limited set of devices, it works better than 500 (except annoying Schlage locks issue).

Both of these look awesome. Except I've never touched 3d printer. But, If you use extension case, female USB-A end is probably going to be almost as wide as the unit itself. The first one you can probably put on the side. Not sure if you can use second one. Edit: Passive extension is much smaller but still something to be considered. Active could be pretty big.

This seems to be hardware/USB issue rather than iox firmware. I'd try to power down polisy and restart. Could be issue with a machine or could be issue with zmatter. If yours Is integrated and not USB, pulling the plug is probably the best way to restart it.

Polyglot profiles are stored on ISY/IoX. But actual polyglot DBs aren't. PG2 is in MongoDB and PG3 is in sqlite. I, personally, don't think it's a huge deal if I had to reinstall node servers from scratch. But if you're thinking of full backup, you should include it. rsync is basically network copy. You would normally have another machine or NAS drive running rsync server and then you configure a script to copy any files you want over rsync to that device. That's an automated way. You can also tar+gzip whatever files you like and scp by hand if you prefer. Should create sqlite backup first rather than copying raw data files though. Something like this: sqlite3 my_database.sq3 ".backup 'backup_file.sq3'"

Would you, please, update when you figure this out? This is pretty scary - don't want to upgrade until this gets sorted out. Do you have up to date Java Admin console?

If you ask UDI for an official image, that gives you full system. Taking the drive out for backup seems like an overkill. You'd want to backup IoX and maybe PG3 databases. Everything else is kind of static. IoX has its own backup. You can probably backup PG3 databases via rsync.