-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UNO IP Arm Home or Night through Home Assistant sends Arm Away to board #147
Comments
Yes, this was a current limitation of the UNO's TPI interface when I originally added support for it. I've not seen any firmware release notes indicating updates yet but I've sent a note off to enquire if/when additional features are coming. |
I reached out to eyezon about tpi interface. They said that is controlled by the manufacturer which is Envisacor. To me it looks like they are the same company. I can help ask for whatever you need, but I just don't know exactly what would be helpful for you. Thanks. |
Yes, it is Envisacor I've contacted. I know they had plans to add a bunch more functionality but don't know a timeline on it at the moment. |
I also reached out on the eyezon forum about new TPI documentation. The support person I talked to at eyezon says they do answer questions on their forum. Let me know if you get a response. Thanks. |
Any response from envisavor? |
They are just working on updated documentation and will send me a copy when it is complete. It sounds like that will be relatively soon. This should capture additional capabilities they are adding. Based on previous conversations I've had with them, I suspect these updates will have the ability to arm in different modes. |
not sure if it helps the cause or not, but you can arm "home" from the eyezon web interface. does that help to gather what is needed to update the code? |
any updates on this? |
@copperlab No, I haven't heard anything back from Envisacor yet. @deliverer33 Unfortunately the interface used by this integration does not have the same capabilities as what has been made available on the web interface. So it's just a matter of waiting until they release firmware and documentation with the additional capabilities. |
I see a new firmware was released. Did this come with what you were looking for? |
Any updates? I'm unable to arm in night or home mode through HAAS on my UNO IP hybrid system. |
There is another new update that was released today. Also have a thread on the eyezon forum to try to get the attention of the manufacturer: https://forum.eyezon.com/viewtopic.php?t=5442&sid=11530eabfa0b5339462928e48ea92731 |
I just updated to 117 this morning, and it still tries to arm away when trying night or home |
I spoke with Envisacor and the released firmware versions do not yet include the TPI changes needed. While I don't have an ETA, they are actively work on the required changes. |
Well, that is at least something. They are acknowledging there is an issue. The firmware updates seem to be somewhat regular, so hopefully they'll get this sorted out. Until then, I'll need to arm my system manually. |
They've actually been very responsive with me and very receptive to adding features to the TPI. Development sometimes just takes time and I'm sure they have many competing priorities to juggle. |
Okay, that's good to hear. I guess reading the entire thread, it didn't seem like they were entirely responsive at first. Then again, that was 2 months ago with a limited number of responses. |
I updated my Uno panel with the recent beta version and now Arm_stay (home) works. I updated home assistant with the current beta version, restarted HA and Waited for about 6 Hrs and now both Arm_away and Arm_stay functions are working in Apple HomeKit. |
I just heard back from Envisacor and they have a new firmware available which adds additional capabilities to the TPI interface. I still need to make the necessary changes to support it in this integration but I don't own an Uno version so will need some people to test it. Are any of you willing to have the new firmware pushed to your devices to help test? If so, please send me the MAC address of your device and I can pass that along to Envisacor. Thanks! |
I am 001C2A400364 Current Firmware - Firmware: 01.00.104 |
I'm in. 001C2A4013A6 Current Firmware: 117, although it is telling me 122 is available. Queueing that up now. |
Saw new firmware 122 so updated as of this morning. |
The firmware version with the necessary changes is Before anyone does this, a couple things:
I'll update here when I have a beta version available. |
I've got the updated code, 1.0.123 pushed to my device. |
Looks like version 123 is live to everyone now. |
I have published a beta release based on the changes in the latest firmware. Even if you don't find any issues, I would appreciate someone posting some debug logs from startup and when issuing various commands (arm, disarm, zone bypass, etc.) so I have get a better idea of the traffic to/from the Uno device. There is still more to add but I wanted to get something out for people to try. |
I am on firmware version 122 |
I'm in the same situation. I'm on 122, but I'm not being prompted for 123. I'm not sure what to do to get it to provide the update. |
I’m on the new beta and can confirm Arm Home works as does Arm Away. One interesting item I cannot disarm until the alarming period completes. So I can’t click Arm Home and then disarm right away. Happy to send logs just let me know how and what. Great work and thank you! |
maybe a phased rollout? I am not on any beta program and was prompted for version 123 after being on version 117 |
Would it be fine to install the new beta version with firmware 122? |
I suspect they do a phased rollout. If your device is from EyezOn, I believe you should be able to contact them and request that they push the new firmware to your device.
@DineshChr No, the beta will only work with the 123 firmware as it relies on new features added to that version. |
When I issue an arm home or arm night command from HA it always actually goes into home away on the UNO IP system.
I am not sure if this is one of the features that has not been added yet. Other than that seems to be working great.
The text was updated successfully, but these errors were encountered: