Announcement

Collapse
No announcement yet.

Temp05 v4, v5 / Temp08 1-Wire Interface xAP Node Linux use

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Temp05 v4, v5 / Temp08 1-Wire Interface xAP Node Linux use

    I still have the old Temp0X test xAP plugin that is still working on my mcsSprinklers Linux box.

    Can I use that application on any of my Linux boxes today to broadcast xAP from my 1-wire devices? Could I run multiples of it to connect to multiple USB and serial 1-wire stuff?

    I haven't touched my 1-wire stuff in a long time. I have 3 Temp0X devices and a couple of USB devices installed next to small Leviton patch panels in my Leviton 42" can.

    I was thinking of maybe just moving the serial / USB connections all to one little RPi such that it talks xAP from multiple serial devices.
    - Pete

    Auto mator
    Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
    Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

    X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

  • #2
    I have been updating xapmcsTemp0x for Linux as the other updates have been made. I think the version you are using is fine for reporting, but does not accept xapbsc commands to send data to Temp08. Multiple on the same computer will have an issue with the xap source address as they would all look the same. I do not since I have an instance text box on the browser setup. Other than this multiple can be run.

    Let me know specifically what you want and I will see if I can accommodate.

    Comment


    • #3
      Thank-you Michael.

      It would just be a simple autonmous device with multiple serial 1-wire networks broadcasting xAPBSC statuses.

      The Temp0X devices all continue to work just fine. The adds have been Maxim serial and 3rd party USB (serial) 1-wire devices.

      I think the version you are using is fine for reporting, but does not accept xapbsc commands to send data to Temp08.
      Yup; current utilized for this testing Temp08 has only temperature / temperature-humdity combos. I have 1-wire dual counters / single counters on another Temp0X device right now. Still many times just reset counters via a terminal session.

      I did originally just wire individual sensors in a star fashion via CatXX to a punch panel inside of the Leviton 42" can. Adjacent to the punch panel are the Temp0x devices layered horizontally with connectivity to the punch panel (used the Leviton telephone style ones years ago). The RS-232 outputs utilize catXX to 9 pin RS-232 devices to the Digi serial Edgeports. Its sort of primitiive looking as I use one tiny 2" patch cable per 1-wire leg (run) on the Leviton telco patch panel.

      I have added more temperature sensors to the legs of the original cat5e creating a little bit of the hub and spoke stuff and they work fine. I continue to use the tiny parasitic AAG combination temperature/humidity sensors. The temp/humidity adds have been the larger style AAG combos, Midon combos and Hobby Boards.

      Having one instance of the xapmcsTemp0X connecting to multiple serial 1-wire devices would also work. I never much used the console GUI rather just the web gui instance per port to configure the multiples of instances in Homeseer 2.

      IE: configure, save and broadcast on one side then capture (A) and renaming of devices on the other side - takes a minute to do.
      - Pete

      Auto mator
      Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
      Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

      X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

      Comment


      • #4
        I added the Instance parameter. I can test basic operation on RPi, but don't have Temp05/08 to test with. Let me know if there are any issues. It will run in console mode on either Linux or Windows. Note the format for serial port is shown by example under the text box entry on the browser page.
        Attached Files

        Comment


        • #5
          Thank you Michael.

          Trying to break it today with the old testing Temp05 with my star topology adding more tiny combo parasitic temperature / humidity sensors. I had to add one 100 Ohm resistor to one stub of 4 connected combos such that its working fine still.
          - Pete

          Auto mator
          Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
          Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

          X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

          Comment


          • #6
            Installed the new application on a Wintel and 2 non Homeseer Linux boxes. It runs great with the new Linux mothership with HSPro on it.

            It opens a console window in windows with a little status icon.

            By accident though going to my box-o-automation grabbed a 9097 (have a few of these around) initially then went to the Temp0X devices.

            Tonight installed the app on the Zee in the Homeseer directory and have it starting with the Zee and created a link in Homeseer to it. Runs fine. I also just ran it separately and that works well too.

            Curious if you are doing any linux serial to linx serial via the network or are you still doing wintel serial to the network?
            - Pete

            Auto mator
            Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
            Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

            X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

            Comment


            • #7
              Curious if you are doing any linux serial to linx serial via the network or are you still doing wintel serial to the network?
              Don't understand the question. With xapmcsTemp0x, for example, the serial port can be specified as a device managed by the OS or as an IP address where the assumed client is an IP/Serial device. I don't think I actually tested the IP address from Linux, but don't know why it would be any different than running from Windows as logic is all .NET sockets.

              xAP is UDP on the LAN so Windows or Linux can send and receive

              Comment


              • #8
                Well relating to Linux / Terminal server with multiple serial ports connected to 1-wire serial devices talking to another Linux box running multiple xAP instances.

                Temp0X = = > Serial Port ==> Network ==> Linux Box (IP to virtual serial port) = > xAP 1-wire application

                Or

                Temp0x = = > Quatech 4 port Serial Server = = > Network ==> Linux Box (IP to virtual serial port) = > xAP 1-wire application
                - Pete

                Auto mator
                Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                Comment


                • #9
                  Your network diagram has been implemented, but the virtual serial port is not needed. xapmcsTemp0x processes the raw stream of characters from the network just as if they came from a virtual port. I do not understand however your first sequence where there is a direct serial port to network connection. There needs to be some device in the middle to translate serial to socket.

                  Comment


                  • #10
                    Thank you Michael.

                    Just thinking out loud relating to the variety of serial transport connectivity things that I am using in Wintel that I am not using in Linux at this time.
                    - Pete

                    Auto mator
                    Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                    Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                    X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                    Comment


                    • #11
                      Testing the Linux/Wintel posted xapTemp08Console_2002.zip on 32 bit Windows, 32 bit Linux (RPi) and 64 bit Linux noticed that the Linux version goes "deaf" after about 12 hours or so. Wintel 32 bit version keeps running fine. I cannot tell for sure on the timeline. Will continue to test it. mcsxAP plugin in Linux runs fine with no issues.
                      - Pete

                      Auto mator
                      Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                      Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                      X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                      Comment


                      • #12
                        Looking this morning at the logging of the plugin running on the Zee.

                        Looks like something is getting messed up with the polling. It is still connect fine though as I sent it a DIS and it works fine. Just going deaf and not broadcasting the xAP updates and status on web page remains static from the day before.

                        Note here the break in Temp0X communications until I do a DIS.

                        2/3/2015 7:06:11 PM | 01 84000800E947A110 DS1820 OK P
                        2/3/2015 7:06:11 PM | 02 F900000009EA8F1D DS2423 OK P R
                        2/3/2015 7:06:11 PM | 03 5400000075150626 DS2438 OK P H
                        2/3/2015 7:06:11 PM | 04 BC0000004CE93526 DS2438 OK P V
                        2/3/2015 7:06:11 PM |
                        2/3/2015 7:06:12 PM | Poll = 00 minutes
                        2/3/2015 7:06:12 PM | Temp disp = F
                        2/3/2015 7:06:12 PM | Serial # disp = On
                        2/3/2015 7:06:12 PM | Wind dirn rev = Off
                        2/3/2015 7:06:12 PM | TUE 18:22:21
                        2/3/2015 7:06:12 PM | >
                        2/4/2015 8:55:31 AM | [Sent to Temp0x dis
                        ]

                        2/4/2015 8:55:32 AM | 01 84000800E947A110 DS1820 OK P
                        2/4/2015 8:55:32 AM | 02 F900000009EA8F1D DS2423 OK P R
                        2/4/2015 8:55:32 AM | 03 5400000075150626 DS2438 OK P H
                        2/4/2015 8:55:33 AM | 04 BC0000004CE93526 DS2438 OK P V
                        2/4/2015 8:55:33 AM |
                        2/4/2015 8:55:33 AM | Poll = 00 minutes
                        2/4/2015 8:55:33 AM | Temp disp = F
                        2/4/2015 8:55:33 AM | Serial # disp = On
                        2/4/2015 8:55:33 AM | Wind dirn rev = Off
                        2/4/2015 8:55:33 AM | WED 08:11:43
                        2/4/2015 8:55:33 AM | >
                        Message Log shows following continuously. On wintel it shows it opening the com port once only.

                        2/4/2015 5:07:56 AM | Temp05 Comm Port ttyUSB0 Opened
                        2/4/2015 5:07:56 AM | ConnectionMonitorTimer Last Received=2/4/2015 5:00:56 AM, MinuteInterval=3
                        2/4/2015 5:07:56 AM | Temp05 Comm Port ttyUSB0 Opened
                        2/4/2015 5:08:56 AM | ConnectionMonitorTimer Last Received=2/4/2015 5:07:56 AM, MinuteInterval=3
                        2/4/2015 5:09:56 AM | ConnectionMonitorTimer Last Received=2/4/2015 5:07:56 AM, MinuteInterval=3
                        2/4/2015 5:10:56 AM | ConnectionMonitorTimer Last Received=2/4/2015 5:07:56 AM, MinuteInterval=3
                        2/4/2015 5:11:56 AM | ConnectionMonitorTimer Last Received=2/4/2015 5:07:56 AM, MinuteInterval=3
                        2/4/2015 5:12:56 AM | ConnectionMonitorTimer Last Received=2/4/2015 5:07:56 AM, MinuteInterval=3
                        2/4/2015 5:13:56 AM | ConnectionMonitorTimer Last Received=2/4/2015 5:07:56 AM, MinuteInterval=3
                        2/4/2015 5:14:56 AM | Temp05 Comm Port ttyUSB0 Opened
                        2/4/2015 5:14:56 AM | ConnectionMonitorTimer Last Received=2/4/2015 5:07:56 AM, MinuteInterval=3
                        2/4/2015 5:14:56 AM | Temp05 Comm Port ttyUSB0 Opened
                        I have the polling set in the webgui at every 1 minute.
                        Last edited by Pete; February 4th, 2015, 05:10 PM.
                        - Pete

                        Auto mator
                        Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                        Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                        X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                        Comment


                        • #13
                          Do you have debug enabled on both Linux and Wintel instances? The connection message should only occur as part of debug and every minute.

                          The monitor is looking for no data from Temp08 in 3 times the defined polling rate. When it happens it tries to reopen the port. This was primarily intended to restore an TCP/IP connection for the IP/Serial case.

                          What you need to do is be certain the data rate set in the Temp08 for reporting is the same as the polling interval defined in the browser GUI. There is actually no polling, but only wait for Temp08 to deliver data. Polling is only for monitoring.

                          With the attached I changed the recovery action from closing/opening the port to destroying and creating the RS232 interface object. This object also contains the timer that is used only in Linux to poll the port to see if characters have been received. This polling is built into the windows version of the serial port handler. What looks to be happening is this port polling for characters has stopped for whatever reason and xapmcsTemp0x can no longer hear the Temp08.

                          Even though there are no changed in data from Temp08 reporting you should still get the heartbeat from xapmcsTemp0x over the LAN. A design choice could be to only send the heartbeat when data is being received from Temp08, but as currently implemented the heartbeat is only indicates that xapmcsTemp0x is still running.
                          Attached Files

                          Comment


                          • #14
                            Thank you Michael.

                            Do you have debug enabled on both Linux and Wintel instances? The connection message should only occur as part of debug and every minute.
                            I did for a bit yesterday and day before.

                            Yup yesterday changed the Temp08 polling rate such that it didn't keep saying zero to one minute via a console terminal to the Temp08. It seemed to have stayed. Left the GUI polling rate at 1 minute. It worked for a bit then went deef. I did also add a hub to the Zee running HS3 lite. I am using the xAP plugin on the HS3 Ubuntu 64 bit box and its getting data fine from 3 instances of xAP running on Wintel boxes. (well the wintel 9097 xap plugin also quits working after a bit).

                            I am leaving the clock speed right now at 700Mhz as I do not think overclocking will help right now.

                            All in all currently running - HS3 lite, xapmcsTemp08console, xap hub, webmin on the RPi which is still sort of lite; eh? (IE: no z-wave right now).

                            Looking this morning:

                            1 - Temp0x GUI is not updating devices (stopped yesterday). It is not sending out xAP messages. See attached picture.

                            2 - Temp0x communications still shows the devices every minute:

                            2/5/2015 7:24:13 AM | Reading Sensors...
                            2/5/2015 7:24:14 AM | Humidity #01[5400000075150626]=21%
                            2/5/2015 7:24:15 AM | Voltage #01[BC0000004CE93526]=00.68V 05.09V 00mV
                            2/5/2015 7:24:16 AM | Rain #01[F900000009EA8F1D]=00.74 Inch
                            2/5/2015 7:24:17 AM | Temp #01[84000800E947A110]=67.10F
                            2/5/2015 7:24:18 AM | Temp #02[5400000075150626]=66.41F
                            2/5/2015 7:24:20 AM | Temp #03[BC0000004CE93526]=69.45F
                            3 - debug is currently off and temp0x messages continuously shows:

                            2/5/2015 7:10:05 AM | Temp05 Comm Port ttyUSB0 Opened
                            2/5/2015 7:17:05 AM | Temp05 Comm Port ttyUSB0 Opened
                            2/5/2015 7:17:05 AM | Temp05 Comm Port ttyUSB0 Opened
                            2/5/2015 7:24:05 AM | Temp05 Comm Port ttyUSB0 Opened
                            2/5/2015 7:24:05 AM | Temp05 Comm Port ttyUSB0 Opened
                            4 - HS3 xAP plugin working fine (sort of). Following are status of variables running on HS3 pro Ubuntu 14.04 64bit.

                            This is from a Wintel instance of the new temp0x console plugin:

                            44.6F xap Garage Temp Today 7:27:50 AM


                            This is from the Zee running the new Temp0x console plugin:

                            66.3F xap mcs.Temp0X.ICS-HomeTrollerZEE:xapmcsTemp 0x_Basement-2-Temp.5 400000075150626.Temperature Yesterday 5:16:02 PM
                            This is from the wintel xap 9097 instance which is also going deef. (I have a bunch of 9097's that I use in addition to the Temp0x devices).

                            2/3/2015 8:21:03 PM
                            Will update today.
                            Last edited by Pete; February 5th, 2015, 10:18 AM.
                            - Pete

                            Auto mator
                            Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                            Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                            X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                            Comment


                            • #15
                              Testing update. Running fine after about 60 minutes.

                              Attached a JPG relating so some issues with GUI.

                              Testing with 1 combo humidity/temperature sensors, two temperature, one rain counter (an old Dallas Instruments rain tipping bucket).

                              Not seeing the tipping bucket on the gui right now. Keep refreshing it.

                              PM Update: still see the serial thread but quit xap chatting around 1000c this morning per GUI.

                              67.6F 5400000075150626 Today 2/5/2015 10:07:53 AM
                              Communications still show the devices but they are looking a bit messed up.

                              Morning look:

                              2/5/2015 10:06:13 AM | THU 09:22:26
                              2/5/2015 10:06:13 AM | Reading Sensors...
                              2/5/2015 10:06:13 AM | Humidity #01[5400000075150626]=21%
                              2/5/2015 10:06:15 AM | Voltage #01[BC0000004CE93526]=00.69V 05.09V 00mV
                              2/5/2015 10:06:16 AM | Rain #01[F900000009EA8F1D]=00.74 Inch
                              2/5/2015 10:06:17 AM | Temp #01[84000800E947A110]=67.65F
                              2/5/2015 10:06:18 AM | Temp #02[5400000075150626]=67.42F
                              2/5/2015 10:06:19 AM | Temp #03[BC0000004CE93526]=69.67F
                              PM Look:

                              2/5/2015 2:11:13 PM | THU 13:27:26
                              2/5/2015 2:11:13 PM | Reading Sensors...0000075150626]=25400000075150626]=21%
                              2/5/2015 2:20:19 PM | Temp #03[BC0000004CE93526]= 01.51V 01mV ???00800E947A110]=65.75FC0000004CE93526]=00.66V 05.09V 00mV
                              2/5/2015 2:22:19 PM | Temp #03[BC0000004CE93526]=67.55F
                              2/5/2015 2:23:13 PM | Humidity #01[5400000075150
                              2/5/2015 2:23:16 PM | Temp #0
                              2/5/2015 2:24:19 PM | >mp #03[BC000000p #01[84000800E.0626]=21%800E947A110]=65.62F1D]=00.74 Inch
                              2/5/2015 2:45:16 PM | Rain #
                              2/5/2015 2:46:15 PM | Rain #01[F900000009EA8F1D]=00.74 Inch1[BC0000004CE93526]=00.67V 05.1[84000800E947A110]=65.62F
                              2/5/2015 2:52:17 PM | Temp #01[84000800E94=00.68V 05.09V 00mV
                              2/5/2015 2:55:19 PM | Temp #03[BC0000004CE93526]=67.31F
                              2/5/2015 2:56:13 PM | Humidity #01[5400000075150626]=21%000009EA8F1D]=00.74 Inch #01[BC0000004CE93526]=00.67V 05.09V 00mV
                              2/5/2015 2:57:19 PM | Temp #03[BC0000004CE9352
                              Messages PM:

                              2/5/2015 2:40:53 PM | Temp05 Comm Port ttyUSB0 Opened
                              2/5/2015 2:40:54 PM | Temp05 Comm Port ttyUSB0 Opened
                              2/5/2015 2:47:53 PM | Temp05 Comm Port ttyUSB0 Opened
                              2/5/2015 2:47:54 PM | Temp05 Comm Port ttyUSB0 Opened
                              2/5/2015 2:54:53 PM | Temp05 Comm Port ttyUSB0 Opened
                              2/5/2015 2:54:54 PM | Temp05 Comm Port ttyUSB0 Opened
                              Attached Files
                              Last edited by Pete; February 5th, 2015, 03:57 PM.
                              - Pete

                              Auto mator
                              Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                              Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                              X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                              Comment

                              Working...
                              X