As it stands, I very much doubt it Pete. It may be possible to get it to control remote Windows clients from a Linux installation. The Network element however uses a number of Windows calls and would never work without significant modification.
Announcement
Collapse
No announcement yet.
Jon00 Remote Computer Control & Network Monitor (HS2, HS3 & HS4)
Collapse
This topic is closed.
X
This is a sticky topic.
X
X
-
Thank-you Jon.
I have been testing Homeseer 3 on Linux with additional Wine / VMs type of stuff. I currently have a W2003 VM running speaker dot exe talking to Homeseer 3 and it's currently working.
I have had issues running some windows networking(diagnostic) programs in Wine though.
I was going to try the NirCMD utilities to see how they do running on the W2003 VM instance.- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
-
My log is getting FLOODED with these messages:
Code:[COLOR=#FF0000]Error in updateVD subroutine Block 2: (Object reference not set to an instance of an object.) [/COLOR]
Originally posted by rpradeThere is no rhyme or reason to the anarchy a defective Z-Wave device can cause
Comment
-
It's hard to say exactly when I first saw this. I can look back through the logs to find out specifically if that's helpful. But I do know that I've been seeing it occasionally for quite a while. Just it's only been a few times a day max. Until this morning. It hasn't happened again since I restarted HS3 a few hours ago. I am on the latest HS3 beta.Originally posted by rpradeThere is no rhyme or reason to the anarchy a defective Z-Wave device can cause
Comment
-
@Jon,
Just noticed that the WOL isn't working any more on my two HS2 boxes.
Suspend works great.
I can manually wake up the devices with a WOL program call WakeMeOnLan just fine.
5/23/2015 4:55:21 PM Jon00_RCCNM Error: Check WOLPortNumber entry under [Settings]- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
-
Thank-you Jon.
Checked and both are set accordingly
5/23/2015 6:48:41 PM Jon00_RCCNM Error: Check WOLPortNumber entry under [Settings]- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
-
Originally posted by S-F View PostI have been seeing this error quite a bit but not like earlier today. I restarted HS3 last night and just did so again. I'll report back if it continues.
Comment
-
Copy the text of your existing Jon00RCCNM.ini file to Notepad and then save it over the existing file.
Done did the doo this morning and it worked great. Thank you Jon.Last edited by Pete; May 26, 2015, 11:52 AM.- Pete
Auto matorHomeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant
Comment
-
Client Not Communicating on Schedule Task Start Up
I'm just at the start of setting this up, and I have seem to run into a problem.
1) I have the Jon00RCC.exe starting with a windows scheduled task on Start Up
2) Task is delays for 2 Min on Start up
3) I think I've tried every combination of settings but still no joy.
Problem:
Even though Jon00RCC.exe starts and is running, I get no coms to server. (there is also no system try icon, which I think is to be expected).
If I rip Jon00RCC.exe out of memory, and start normally everything functions.
No error text created..
Machines involved are a mix of Win 7 and Win 8.
Any idea how I can get around this??
Comment
Comment