gaetanlord

Cool, It will be a pleasure to test your new code, once ready

You're right, lot of message in Console.log. Shame on me not taking a look before posting. As I mention in my previous post, I had to change the hardcoded port in haremote.py from 8123 to 80 to make it work, but with the error messages in HistoryBuffer I just rescan the code and I found 3 other instances of hardcoded 8123 , that I missed inititialy, in hasshub.py. I replace them with 80, my HA port, and no more messages. I think we found the problem. I would love to help you in your code, but I'm a perl programmer and have to learn python, maybe one day. Great works. Now the fun begin Regards Console.log

You're right, I edit the log file because I didn't want to put my domain name, it is indeed gaetanlord.ca . I did sent my last log file, and I only change the occurence of gaetanlord.ca I have my own local resolver and it does resolv with this name on all the host inside my house. For the internet, it also resolv the same name. But your comment make me think a little bit more, I do not use default port 8123, so I trace the network and voila. You assume that I use port 8123. In fact, I use port 80 or https port 443 via proxy. So I edit file haremote.py and change the port to 80 and all is working fine, no more black screen, I can see the clock. I then check if mqtt would work. The useage note do not mention username parameter for mqtt, after I look in the source code, I found out that you do have "username", so I also rcv console messages But, I still have another question. I notice that disk space was decreasing, and found out that I collect a lot of data in the history buffer, almost every 2 seconds for the 5 minutes mention in your notes. When looking at the error, it is about the HA connection where I do get a connection refused. Maybe you could help me out on that one too. Log files includes, and not edited log2 log1

Trying to learn your software and I have a hard time doing the basic. Wonder if you could just point me in the right direction. No intend to use my ISY, I want to connect only to HA. All my insteon devices are now managed under insteon2mqtt I have a raspberry pi 3 model B with the official 7in touchscreen. I try to reduce my test to a minimum and build from it, but no luck. Once I start the following config.txt, I get a black screen cfglib = cfglib DefaultHub = MAISON HomeScreenName = MyClock PersistTO = 30 DimLevel = 5 DimTO = 15 DimIdleListNames = MyClock, DimIdleListTimes = 20, MainChain = MyClock [MAISON] type = HASS.1 address = maison.example.com password = long_token I would expect to have a clock displayed, and a connection message to HA. I know the HA token key is working I test it manually with the command curl, but I get recurring message about the connection not responding What would be my stupid mistake Console.log

I play a little more on this. After a reboot I tried again, and a kill does return the window manager as expected. But I still wonder if there is a way to have an exit button. Note that I haven't read completely the usage note and it might already be possible to do it I forgot to mention that I have the following input device and tried all of them crw-rw---- 1 root input 13, 66 Dec 28 01:01 event2 crw-rw---- 1 root input 13, 63 Dec 28 01:01 mice crw-rw---- 1 root input 13, 33 Dec 28 01:01 mouse1 I also have message like this in Xorg log file [ 1555.592] (II) input device 'FT5406 memory based driver', /dev/input/event2 is tagged by udev as: Touchscreen [ 1555.592] (II) input device 'FT5406 memory based driver', /dev/input/event2 is a touch device This seem consistent with the device I have when I look at cat /proc/bus/input/devices I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="FT5406 memory based driver" P: Phys= S: Sysfs=/devices/virtual/input/input2 U: Uniq= H: Handlers=mouse1 event2 B: PROP=2 B: EV=b B: KEY=400 0 0 0 0 0 0 0 0 0 0 B: ABS=2608000 3 I also tried the following driver https://github.com/pimoroni/python-multitouch The example work and I could use the touchscreen

Thank Kevin for the quick reply We are progresssing, but not 100% there Instead of changing the config.txt, I simply edit the console.py and apply your last commit changes and it does work fine, I do see the minimal console Now, I'm facing an input device issue. I could run the software, but when I touch the screen I get the following message selected device is not a touchscreen I understand Also, simple question. I plan to use softconsole with some other tool I display on the screen. The softconsole is grabbing the control of the screen, which is fine until we want to exit. I do kill the process, but the X server of the screen do not come back. That screen is not fullly dedicated to the softconsole, is there a way to give back the control to the display manager. May I suggest to have an exit button. Just a couple more issues in your plate I'm in vacation for the next 2 weeks, so I have time to work on this and help you fixing the software for the 7 inches display. Regards

Hi Looking for advise on what I could do wrong. Trying to using softconsole on my PI3 with official 7 inches display. I install softconsole by only running the setupconsole script. That didn't create the config.txt file, so I simply copy the minimaltest.txt file to config.txt I fill the data in cfglib/auth.cfg. Trying to run the console.py by hand. If I do not have a config.txt it report the file not present If I copy the config.txt, syste, start and then crash. I'm suspecting an issue when getting the data from my ISY. it seem to report an error with a device (Veranda), but I do not see anything wrong on my ISY log. veranda is a regular 2477S. I attach my log file if that could help Thank for any advise on what I do wrong Regards Console.txt

Thank you Brian H A reset of the switch fix the problem, good to know.

I will have to try Brian H. reset when I'll be back home at the end of the week. The reason I think Brian have the solution is 2 fold. It is a 2476 switch But more important, I have a motion sensor attach to this switch and when I trigger the motion, the X10 do not react. So I only have a reaction when I manually use the switch itself. More to come

Hi I have a strange problem with some X10 switches. I had many communictaion issues in the past and I'm slowly replacing them. I remove all the X10 devices from my configuration, but I have a weird problem One of my X10 device seem to be hook to an insteon one. I mean whenever I on/off my insteon device it does the same on that specific unprogrammed X10 switch. I would like to disable the X10 module from my ISY994i but I do not see how it could be done via the admin interface. I connect to the console via telnet and I could see that the module is present when I run the command "ve" http://192.168.1.19>ve Product: (1100) ISY 994i 1024 App: Insteon_UD994 Platform: ISY-C-994 Version: 4.6.2 Build Date: 2017-06-21-13:52:47 Other Services: - Programs Enabled Modules: 21010 - OpenADR 21060 - A10/X10 for INSTEON 21075 - Portal Integration - UDI How could I disable or even better remove the X10 module, so I'll be sure there is no interaction from the module Regards