Jump to content

Bladerunner

Members
  • Posts

    22
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Bladerunner's Achievements

Member

Member (3/6)

4

Reputation

  1. Still Investigating. I did find that I could dim/brt two other bedrooms. They are on a different circuit. I was able, via UD Mobile, to change these rooms. The master bedroom and bath, that are not responding to dim/brt, are on the same circuit! The two rooms that are dimming and brightening have the same X10 switch module as the master bedroom. So, it's not that. Now I need to start disconnecting/testing to see what's affecting that line to such a degree. It's so odd that it's just the dim and brt that aren't working. More to come!
  2. Yes, I saw that response but I thought it was the LM465 responding. Yes, signal suckers. I had noticed some missed commands a while back. I got out the ACT004 and found some noise at the crossover. But it turned out the laptop power supply from my wife's laptop was sucking signal. I added a block to that location and the signal greatly improved. I found noise from some dimmed incandescents and turned them off. So noise was gone and the signal killer was taken care of. What's funny is that the ON and OFF commands work perfect. If it was noise or signal suck, I would at least get some intermittent dim or bright commands to work. I did find a newer Leviton paddle switch is also not responding to dim or bright commands. And it is on a different circuit. I need to do more investigation into this. I have a trouble ticket open as well for his opinion on this. I have the ACT phase coupler/repeater. I do believe it is functioning. I will double check that however.
  3. Thanks for taking the time to try that. Nice to know others have old parts boxes too. And I would think that the LM465 is a pretty good match for the old wall switch. I did create a ticket to ask for support on this question. I am suspicious of the device definitions but the event viewer and my ACT004 meter don't show a difference. I got out my ACT 004 meter tonight, finally got back to this. I tried commands from a 16 button X10 controller, from UD Mobile, so removing HA altogether. UD Mobile is also failing to brighten or dim on these old wall switches, even though the X10 controller module dims and brightens just fine. I did notice that I used the type of X10 on those old switches while I had used A10 for the newer Insteons I installed that respond to an X10 code. The event viewer shows the same command for F2 (which functions) and G14 (which does not function). The ACT 004 meter shows a valid F2 DIM and a valid G14 DIM as well, the same displayed as the X10 controller. Sun 11/10/2024 22:03:58 : Create REST U7 [/rest/nodes/FF%2007%200E%201/cmd/BRT] Sun 11/10/2024 22:03:58 : U7 Rest: submitCmd([FF 07 0E 1],[BRT],[<NULL>]) Sun 11/10/2024 22:03:58 : [ X10] G14 Sun 11/10/2024 22:03:58 : [ X10] G14/Bright (7) Sun 11/10/2024 22:04:23 : Create REST U7 [/rest/nodes/FF%2006%2002%201/cmd/BRT] Sun 11/10/2024 22:04:24 : U7 Rest: submitCmd([FF 06 02 1],[BRT],[<NULL>]) Sun 11/10/2024 22:04:24 : [ X10] F2 Sun 11/10/2024 22:04:24 : [ X10] F2/Bright (7) Here's the XRay of each of those devices. <nodeInfo> <node flag="128" nodeDefId="X10"> <address>FF 06 02 1</address> <name>Family Room Fan Light</name> <hint>0.0.0.0</hint> <type>113.2.0.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>FF 06 02 1</pnode> <property name="" uom="100" formatted="On" value="255" id="ST"/> </node> <properties> <property name="" uom="100" formatted="On" value="255" id="ST"/> </properties> </nodeInfo> <nodeInfo> <node flag="128" nodeDefId="X10"> <address>FF 07 0E 1</address> <name>Bedroom Master Ceiling Light</name> <hint>0.0.0.0</hint> <type>113.1.0.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>FF 07 0E 1</pnode> <property name="" uom="100" formatted="On" value="255" id="ST"/> </node> <properties> <property name="" uom="100" formatted="On" value="255" id="ST"/> </properties> </nodeInfo>
  4. My device is a an old X10 wall switch. It will turn on with a press, off with a press, dim and brighten on hold, accepts on, off, dim, brighten from an X10 console. In UD Mobile, I can on, off, brighten, dim. The dim and brighten are incrementals of course, % not supported. Neither is status (different issue to address). Here's the code that I created in a script, just an action. However, the light did not act on either brighten or dim script actions. Any thoughts as to what I did wrong? Was hoping the node command would get it. I'm really new on HA but learning, that time when it's easy to make mistakes. action: isy994.send_node_command metadata: {} data: command: brighten target: entity_id: switch.bedroom_master_ceiling_light
  5. I have some Insteon but primarily X10 still operating on Eisy. Those X10 devices correctly show on, off, dim, bright command in eisy and in UD Mobile. However, when those entities come over into Home Assistant, I only get on and off commands. Is there anyway to also get the dim and bright commands to carry over into Home Assistant? This is the only issue I have had getting full functionality into Home Assistant.
  6. After Z-Wave removing the devices in Eisy, I then went over to HA. I attempted to delete the devices but it said they couldn't be found. So, it seems that they were gone but that the devices were not removed from the integration. So all is well it seems. I guess.....
  7. Well it was Z-Wave and I didn't remove them via the Z-Wave menu. I went back and removed then via that menu options allowing Eisy to remove them. Tried a reboot of Ha and it still shows them. Will keep trying.....
  8. Interesting. I did a full HA reboot and I still see those devices.
  9. I removed some devices from Eisy. I then went over to HA and reloaded the Universal Devices integration, expecting the devices to be gone. They were not. I thought that reloading the integration would cause the Eisy to be queried and only the existing devices/entities would be there. Do I have to remove those devices manually?
  10. Yeah, I need to learn a lot more before I start getting this deep. I'm a whole 4 days into my Home Assistant adventure on a new Yellow. Getting this up and running wasn't bad, now it's how deep is the lake. And it seems pretty deep. I just went through the migration from ISY994i to the Eisy. And I love that the Elk M1 I installed communicates with my serial RCS thermostat and Eisy and now can be front ended with HA as well as UD Mobile. I used Homeseer on Windows with a non communicating Ademco alarm panel not long ago. I had to get off Windows on to dedicated platforms before I lost my mind. The whole goal for HA is to build a simple dashboard that fits my wife's needs that can be on her phone.
  11. That link was great to actually see the template code. I have not, however, in HA been able to find that template code and pull it up to mess with it. How do you get to the template code in HA? I'm trying to watch vids and learn but it's vast topic. I have several things in Eisy that I would like to use and I can see that I need to create some states of things that make them more usable in HA. I see references to templates but I cannot find where to get to the actual code. It's a pain starting in something completely new.
  12. I like your dashboard. I was a computer systems engineer and data architect for my career. Suits me fine. And thanks for the template tip! HOWEVER, I am married to a very analog human. They can be hard to interface with even in simple vocal communication so I am looking for a much simpler version of a dashboard for her. Something reminiscent of the car dashboard with simple indicator lights and a few buttons. I know she occasionally looks at the big dial with the needle as she comments about it when I'm driving but those little gauges showing coolant temp, battery, etc. not so much. She REALLY dislikes that I enter addresses in the GPS with latitude and longitude. Kidding aside, I actually have changed things around in the house so I could get to Home Assistant just so I could build more usable dashboards for her. I have two Fire tablets that will be getting reused for this with Fully Kiosk. Now I just have to learn the HA ecosystem. There's a lot there. I was previously on Homeseer and ISY994i so this is quite a change.
  13. Thanks, I did not see an Elk integration in the store so I didn't think one existed. I installed it in HA and it does work. The only issue seems to be that it needs a code entered to arm the system. Not sure why as I don't need it on the Elk keypads or on the UD Mobile interface. I wasn't sure how to edit the cards yet, that's how new I am in HA. Maybe it's possible to set an arming code in HA YAML. I was actually trying to use the Elk devices from the Eisy but I didn't see how to get that one going. I really need to read more on that UDI interface. I hope to build a simple dashboard that my wife can use just for what's important. That's that got HA into the mix.
  14. I have my Home Assistant Yellow up and running. I have it using the UDI integration. This took more time than expected but got it done. I'm glad I already had the Eisy in place and fully migrated from the ISY994i. I can see my Eisy devices. I see the Elk Connector and I can see the device Home Alarm. The Home Alarm has several variables that include the alarm state and armed state, etc. These are well represented in UD Mobile and I have been able to arm the system. Works well. Has anyone added the Elk alarm to a Home Assistant dashboard, including buttons to arm/disarm/status etc? I would appreciate any info or examples. I have a LOT to learn about the HA and its terminology. I'm developing an appreciation for all those nice HA dashboards I see on Youtube! I want to be able to build a simple dashboard for my wife that allows her to control those things important to her and simple to use.
  15. i recently replaced an older X10 Pro inline device with a new Insteon inline device. So, the definition in Eisy is wrong for that device. It still sees it as an X10 device. Is there any way to replace a device in Eisy with its new configuration? I only see where you can set the device type as you enter a new device. If an Insteon device is set to issue an X10 command, does it not act or identify as an Insteon device? I have several Insteon devices that are set to issue X10 as that was the basis in my old Homeseer system. These all should be changed to the appropriate Insteon device.
×
×
  • Create New...