toddhutch

(Early adopter) I was able to update to to 5.8, and 3.1.4, but the commands weren't working with alexa. To narrow this down, I tried to run the "run then" for the program that I have. That didn't work. I had to highlight the command, and click the update in the add to program window, then save the changes, and it worked. Seems like the eisy device while visually looked correct, the acition set for door1 close won't work until the action was updated and save. I'm not really thinking this is an issue with the plugin, but the mechanism which things were changed and how eisy handles this. I had to updated each open and close command for the doors. I'm glad I made this variable based, so I only had to update it in 6 places. But I wonder if there was a simple way to refresh those programs. Everything seems to work great now. Thank you @Goose66

The device accepts power from USB. So 12 volt battery -> cigarette usb power adapter -> standard USB cable -> micro usb port on ratgdo. It must be converting the 5 Volts from the USB to 3.3 on it's own. USB doesn't supply 3.3 volts. See the white cord. My solution takes some soldering albeit, super easy, just attaching the wire to the positive terminal and negative terminal on the cigarette adapter. Everything else doesn't require soldering. I used this to connect to the battery wires, only because I had them. Better would be using something with copper to avoid the very long way down the road corrosion. https://a.co/d/8WGxLVE

I decided to go with a car usb outlet, and connect to the ratdgo via a micro USB cable. Just pop the top off, take out of enclosure, a weld wire to terminals and you have a very inexpensive power supply, that you can connect to the battery. https://www.amazon.com/dp/B09CPSXJ98 They sell in 1, 2 and 5 units.

@Goose66 Thank you for taking that approach, I had just updated all my programs. 3.0.3 Door State fix works great!

I'm using the default installed MQTT and not xKing's MQTT Node server. Logs incase that would be helpful. 2023-12-21 14:47:43,479 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door2 - stateData: {'door': 'closed'} 2023-12-21 14:47:43,479 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door2_lt - stateData: {'door': 'closed'} 2023-12-21 14:47:43,601 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: ST to 0 UOM 97 2023-12-21 14:47:46,485 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for door1 Light(door1_lt) 2023-12-21 14:47:46,508 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for door2(door2) 2023-12-21 14:47:46,570 Command udi_interface.node INFO node:reportDrivers: Updating All Drivers to ISY for door2 Light(door2_lt) 2023-12-21 14:47:46,578 MQTT udi_interface.interface INFO interface:_message: Successfully set door1_lt :: ST to 0 UOM 78 2023-12-21 14:47:46,578 MQTT udi_interface.interface INFO interface:_message: Successfully set door1_lt :: GV0 to 1 UOM 2 2023-12-21 14:47:46,760 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'closed'} 2023-12-21 14:47:46,760 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'closed'} 2023-12-21 14:47:46,782 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: ST to 0 UOM 97 2023-12-21 14:47:46,783 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: GV0 to 1 UOM 2 2023-12-21 14:47:46,783 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: GV1 to 0 UOM 25 2023-12-21 14:47:46,783 MQTT udi_interface.interface INFO interface:_message: Successfully set door2 :: GV2 to 101 UOM 25 2023-12-21 14:47:46,921 MQTT udi_interface.interface INFO interface:_message: Successfully set door2_lt :: ST to 100 UOM 78 2023-12-21 14:47:46,921 MQTT udi_interface.interface INFO interface:_message: Successfully set door2_lt :: GV0 to 1 UOM 2 2023-12-21 14:47:46,962 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 0 UOM 97 2023-12-21 14:49:10,540 Command udi_interface INFO nodes:_cmdDON: Opening door for door3 in DON command handler: {'address': 'door3', 'cmd': 'DON', 'query': {}} 2023-12-21 14:49:12,506 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'opening'} 2023-12-21 14:49:12,506 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'opening'} 2023-12-21 14:49:12,626 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 4 UOM 97 2023-12-21 14:49:21,207 Command udi_interface INFO nodes:_cmdSTOP: Stopping door for door3 in STOP command handler: {'address': 'door3', 'cmd': 'STOP', 'query': {}} 2023-12-21 14:49:23,640 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'stopped'} 2023-12-21 14:49:23,641 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'stopped'} 2023-12-21 14:49:23,717 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 9 UOM 97 2023-12-21 14:49:27,693 Command udi_interface INFO nodes:_cmdDOF: Closing door for door3 in DOF command handler: {'address': 'door3', 'cmd': 'DOF', 'query': {}} 2023-12-21 14:49:29,579 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'closing'} 2023-12-21 14:49:29,580 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'closing'} 2023-12-21 14:49:29,696 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 3 UOM 97 2023-12-21 14:49:43,444 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3 - stateData: {'door': 'closed'} 2023-12-21 14:49:43,445 Thread-19 udi_interface INFO ratgdons:stateCB: State callback generated for node door3_lt - stateData: {'door': 'closed'} 2023-12-21 14:49:43,562 MQTT udi_interface.interface INFO interface:_message: Successfully set door3 :: ST to 0 UOM 97 2023-12-21 14:50:03,674 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message setLogLevel

Thank you for the quick response, door1,2,3 are installed. I closed and opened the Admin console (environment is windows using IoX Launcher and Java) No joy. I clicked the Load Profile in the plyglot V3 ratgdo details screen. Restarted the Admin console. No joy. Rebooted the Eisy box. No Joy. Only the closed state is shown correctly for Door State.

Do you want feedback from the releases here? I just updated to 3.02, and I think there might be a bug. Door3 state when open is 1%, door status when opening is 4%, door status when closing is 3% Door2 state when open is 1%, door status when opening is 4% and when closing is 3% Still working on installing Door1

@Goose66 worked as expected. It wasn't clear, that the IoX Eisy has MQTT installed by default. I almost installed the MTQQ in the store that king released. I did some more reading and found a thread stating it was part the base software. So it might be worth adding that note in the document, that MQTT is already there. 👍👍👍

Any idea when the charge showed up for the order? I ordered on the 6th as well, but maybe it didn't come through until the 7th. 👍👍👍 https://paulwieland.github.io/ratgdo/order_status.html

The people who have receive their Ratgdo, did you receive a shipping notification before your product was shipped? I was hoping to have receive my product by now, but I haven't. I've assumed that since this was backordered, that the charge and email about the order wouldn't happen until the product was in. I don't want to order a second set of 3 units, if the ones that I already order have already shipped. Could someone who has received their order elaborate on the process, like what type of email notification did you get? Thx!

Good afternoon, Local access it ideal, and required. Second for me is to not us a device that relies exclusively on polling for status.

The ratgdo option will not trigger the same action as the remote close using the myQ app. The lights won't flash and beep before it closes right?

@jkosharek Thank you for sharing. So now under $160, and better functionality, that pushes me over the edge. Ordering 3 of the ratgdo's. @Goose66 I was going to offer to send you one, but I see you've bought one as well. 👍👍 I really appreciate the work you put into this over the YEARS Goose, and I'll PM you about your day job. We develop software products, and are in the middle of setting up a partnership on a scale I'm looking for some wisdom on. 👍

Thank you for sharing that @Goose66 I like the concept of the ratgdo, with 3 doors, so that would be under $130. Looks like a project for the winter. I'll have to look more closely at this, as my doors have the battery backup option. We lose power up in the hill country where we live, and it's nice to be able to open the doors even when the power is out. The home automation is all on UPS's so depending on the complications it may or may not be viable to leverage the battery which is 12 volt. I like this because it was what I was expecting liftmaster was going to do with their product. I won't need my wireless door sensors anymore, as this look like the open and close detection is real time, and can be queried. 👍👍👍 Do you think we should wait a while to see if they respond to Michael, or the request for partner access? Or has that ship sailed?

I had been grandfathered in from lift master to access to the service. When they first said payment required to access the garages features remotely, the marketing on the packaging stated it was included. This was more than 10 years ago. I have a login to their service, but at least for me I don’t think the devices show up there anymore. But I have the same question, I’d be willing to pay for access until there is another way without it directly via their/my local hardware. This has motivated me to try harder to sniff the network. Now I have two projects to do the same thing for, this and the Hayward OmniLogic pool controller. i suspect if I speak to the CTO about their decision, he will have a list of reasons why they don’t give local access for home automation. Having a solid suggested method for that discussion would be useful. Any solid recommendations?