firstone

Fixed in 0.1.8.

What Flirc profile are you using and have you tried another remote with 0-9? The logic is pretty straightforward. It should send something if Flirc sending key presses at all. You can PM the logs and I'll take a look. Just note down the time when you're pressing those.

Looking at msata ssd on Amazon, they are all oriented like your current polisy one. It's also consistent with USB to SSD adapter you'd need to image new drive. I don't believe your new drive is a manufacturer's error but could be specialty designed for some different applications? You can try and see if it will mount at all, without turning power on. But, honestly, I'd be concerned with heat dissipation when installed upside down. Probably better off getting another one. Why do you need so much storage on Polisy?

Learn something new every day. I've never seen that and would never expect it. As a side note, blue color LEDs have the highest rate of failure. My power one died on 994. So blue LED going dimmer on power supply is not necessarily indicative on its own.

You can test power adapter with DC voltage tester. Which is a useful thing to have if you don't have one. My light is pretty bright. The real question is - are there any lights on Polisy.

I suggest you load your system onto polisy and look at cpu utilization. A lot of these automation systems, etc run on RPi and such. Polisy hardware is pretty powerful, let alone eisy. Unless you're doing some video editing, compiling c++ files or running docker or vm, you'd be pretty hard pressed to overload them. I think most of IoX would put load on io rather than cpu. There is no intensive processing.

I've tried installing fresh FreeBSD and installing IoX on it. it started up and got recognized by admin console but didn't work properly. Like I've tried to set a time zone and it failed with some totally unrelated error. Also, couldn't get PLM to connect because USB drivers aren't there. Note, that none of that will be supported or approved by UDI. The position is - this software should only run on devices that are old by UDI and having mac whitelisted on UDI systems.

It's the other way around. Micro dimmer needs constant power. If you can find a place to "cut" the line and install micro dimmer, you don't need a switch. Like if there's a bx that goes from box to box and you can disconnect part, you can put micro dimmer into the box you need. You can just control via ISY or install switch any other place and use that to control. Another alternative would be to have 2 micro dimmers and have your current switch control one of them and just hardwire the line.

Since those are just dimmable lights, rather than some smart RGB, why not just get Insteon or zwave dimmer and use "dumb" bulbs? I guess I'm missing the point of why they need to be smart? If it's some shared circuit, maybe micro dimmer.

Mine doesn't have an option of S0. Everything but S2 is disabled. And if I uncheck S2, it fails to enroll.

Thank you. I have 0.11, 0.10.8 and 0.10.9. 11 works but the others don't. Schlage support has told me firmware shouldn't make a difference but I don't really believe them.

Hue integration via Hue NS is superb.

Unless it's a manufacturer with lots of different products and widely used, it's unlikely. If it's not part of the standard, each manufacturer is likely to have their own protocol. You'd need to write NS for each one And like you said, market is flooded with different brands. Maybe a better solution is to buy dumb bulb and use a smart switch?

If you do, what firmware version do you have and can you write/delete user codes? I'm trying to resolve this with UDI but wanted to see if if it's just me.

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.