Domoticz

Hello Jumbotroll,


I'm quite new in your excellent forum and I`m using Domoticz in a DS115J.
Unfortunately I cannot use a blocker to install deConz package to get the possibility to use my usb stick conbee II

Do you attend to release a package version including deConz to be able to use the conbee II usb stick for Zigbee ?


Thanks

Zizougold wrote: ↑Tuesday 04 June 2019 13:55 Hello Jumbotroll,


I'm quite new in your excellent forum and I`m using Domoticz in a DS115J.
Unfortunately I cannot use a blocker to install deConz package to get the possibility to use my usb stick conbee II

Do you attend to release a package version including deConz to be able to use the conbee II usb stick for Zigbee ?


Thanks

I don't write domoticz source code, just build the synology packages from the source.
Maybe if you use the domoticz python version and install the deConz plugin, check this:
https://github.com/Smanar/Domoticz-deCONZ

Hello, Jumbotroll!

Have an interesting question. My synology 918+ install has a uname -r of "4.4.59+". it seems the SETLOCALCONFIG has appended a "+" to the name, and because of this, I get a version magic error for usbserial in the Dmesg log, as your 6.2 Apollolake drivers are compiled for "4.4.59" (no plus sign). Is there an easy way to change the uname of my synology install to remove the "+"? I've spent several hours (and lost a lot of sleep) trying to chase this down, and short of learning to compile these kernel modules myself (5 hours of trying in CHROOT environment yielded no real progress), I'm fairly stuck without the ability to load these serial drivers as kernel modules.

Thanks for any help or tips that can be offered.

Jay

Hhavoc wrote: ↑Monday 10 June 2019 20:36 Hello, Jumbotroll!

Have an interesting question. My synology 918+ install has a uname -r of "4.4.59+". it seems the SETLOCALCONFIG has appended a "+" to the name, and because of this, I get a version magic error for usbserial in the Dmesg log, as your 6.2 Apollolake drivers are compiled for "4.4.59" (no plus sign). Is there an easy way to change the uname of my synology install to remove the "+"? I've spent several hours (and lost a lot of sleep) trying to chase this down, and short of learning to compile these kernel modules myself (5 hours of trying in CHROOT environment yielded no real progress), I'm fairly stuck without the ability to load these serial drivers as kernel modules.

Thanks for any help or tips that can be offered.

Jay

This should be fixed in my latest build if you have installed my DSM 6.2 package...
What domoticz version do you tested?
I recompiled the usbserial package for apollolake just in case you can try : http://www.jadahl.com/drivers_6.2/?arch=apollolake
And I checked that this is compiled with 4.4.59+ for sure.
If this not work, you have to check if you have some old drivers installed on your NAS.
Delete all old drivers and reinstall.

Thanks so much for your help. I went ahead and searched my entire Synology system for other older drivers, only found zusb folder in /lib/modules, which I removed, and a version of /usbserial.ko in usr/lib/modules/, which I deleted. Nothing showed in lsmod. Took out the HUSBZB-1 USB module, rebooted for good measure, then installed the version 6.2-6.5.

Unfortunately, still showing error in DMESG:
usbserial: version magic '4.4.59 SMP preempt mod_unload ' should be '4.4.59+ SMP preempt mod_unload '

I tried forcing with modprobe -f usbserial.ko, using the /usr/local/UsbSerialDrivers/modules versions of the drivers installed by your package, but nothing ever showed up in lsmod. tried plugging / unplugging / rebooting / reinstalling the spk package, but usbserial.ko still failed to load. "Insmod usbserial.ko" still gives back a "invalid module format" error.

Maybe my system is hopelessly janked, and I need a new install.
If you have any other ideas, thanks in advance.
Jay

jumbotroll wrote: ↑Monday 10 June 2019 20:55

Hhavoc wrote: ↑Monday 10 June 2019 20:36 Hello, Jumbotroll!

Have an interesting question. My synology 918+ install has a uname -r of "4.4.59+". it seems the SETLOCALCONFIG has appended a "+" to the name, and because of this, I get a version magic error for usbserial in the Dmesg log, as your 6.2 Apollolake drivers are compiled for "4.4.59" (no plus sign). Is there an easy way to change the uname of my synology install to remove the "+"? I've spent several hours (and lost a lot of sleep) trying to chase this down, and short of learning to compile these kernel modules myself (5 hours of trying in CHROOT environment yielded no real progress), I'm fairly stuck without the ability to load these serial drivers as kernel modules.

Thanks for any help or tips that can be offered.

Jay

This should be fixed in my latest build if you have installed my DSM 6.2 package...
What domoticz version do you tested?
I recompiled the usbserial package for apollolake just in case you can try : http://www.jadahl.com/drivers_6.2/?arch=apollolake
And I checked that this is compiled with 4.4.59+ for sure.
If this not work, you have to check if you have some old drivers installed on your NAS.
Delete all old drivers and reinstall.

Hhavoc wrote: ↑Monday 10 June 2019 22:33 Thanks so much for your help. I went ahead and searched my entire Synology system for other older drivers, only found zusb folder in /lib/modules, which I removed, and a version of /usbserial.ko in usr/lib/modules/, which I deleted. Nothing showed in lsmod. Took out the HUSBZB-1 USB module, rebooted for good measure, then installed the version 6.2-6.5.

Unfortunately, still showing error in DMESG:
usbserial: version magic '4.4.59 SMP preempt mod_unload ' should be '4.4.59+ SMP preempt mod_unload '

I tried forcing with modprobe -f usbserial.ko, using the /usr/local/UsbSerialDrivers/modules versions of the drivers installed by your package, but nothing ever showed up in lsmod. tried plugging / unplugging / rebooting / reinstalling the spk package, but usbserial.ko still failed to load. "Insmod usbserial.ko" still gives back a "invalid module format" error.

Maybe my system is hopelessly janked, and I need a new install.
If you have any other ideas, thanks in advance.
Jay

If it's not working with modprobe –force I think the problem is elswhere, No another users have reported this problem with my drivers for Apollolake
Is it only the usbserial.ko that give "should be '4.4.59+ SMP preempt mod_unload" ?

Yes. None of the others generate that message. The other drivers never load, I'm assuming simply because usbserial.ko fails to load first. Here's an example from DMESG (following the version magic error):

cp210x: Unknown symbol usb_serial_generic_open (err 0).

jumbotroll wrote: ↑Monday 10 June 2019 22:44

Hhavoc wrote: ↑Monday 10 June 2019 22:33 Thanks so much for your help. I went ahead and searched my entire Synology system for other older drivers, only found zusb folder in /lib/modules, which I removed, and a version of /usbserial.ko in usr/lib/modules/, which I deleted. Nothing showed in lsmod. Took out the HUSBZB-1 USB module, rebooted for good measure, then installed the version 6.2-6.5.

Unfortunately, still showing error in DMESG:
usbserial: version magic '4.4.59 SMP preempt mod_unload ' should be '4.4.59+ SMP preempt mod_unload '

I tried forcing with modprobe -f usbserial.ko, using the /usr/local/UsbSerialDrivers/modules versions of the drivers installed by your package, but nothing ever showed up in lsmod. tried plugging / unplugging / rebooting / reinstalling the spk package, but usbserial.ko still failed to load. "Insmod usbserial.ko" still gives back a "invalid module format" error.

Maybe my system is hopelessly janked, and I need a new install.
If you have any other ideas, thanks in advance.
Jay

Is it only the usbserial.ko that give "should be '4.4.59+ SMP preempt mod_unload" ?

Hhavoc wrote: ↑Monday 10 June 2019 22:54 Yes. None of the others generate that message. The other drivers never load, I'm assuming simply because usbserial.ko fails to load first. Here's an example from DMESG (following the version magic error):

cp210x: Unknown symbol usb_serial_generic_open (err 0).

Very strange!
I have modified the utsrelease.h in the kernel to 4.4.59+ before i compiled the drivers, so it should work.
I am sorry, but I have no idea why it's not working on you NAS.
And I think you have to reboot you NAS after update the drivers..

This driver is extracted from synolgy apollolake DSM6.2.2.
Delete all another usbserial.ko drivers and replace with this driver:
http://jadahl.com/usbserial.ko
Copy this driver to /usr/lib/modules and chmod 777

jumbotroll wrote: ↑Monday 10 June 2019 23:14 This driver is extracted from synolgy apollolake DSM6.2.2.
Delete all another usbserial.ko drivers and replace with this driver:
http://jadahl.com/usbserial.ko
Copy this driver to /usr/lib/modules and chmod 777

That WORKED! You are the man.

jumbotroll wrote: ↑Monday 10 June 2019 20:55

Hhavoc wrote: ↑Monday 10 June 2019 20:36 Hello, Jumbotroll!

Have an interesting question. My synology 918+ install has a uname -r of "4.4.59+". it seems the SETLOCALCONFIG has appended a "+" to the name, and because of this, I get a version magic error for usbserial in the Dmesg log, as your 6.2 Apollolake drivers are compiled for "4.4.59" (no plus sign). Is there an easy way to change the uname of my synology install to remove the "+"? I've spent several hours (and lost a lot of sleep) trying to chase this down, and short of learning to compile these kernel modules myself (5 hours of trying in CHROOT environment yielded no real progress), I'm fairly stuck without the ability to load these serial drivers as kernel modules.

Thanks for any help or tips that can be offered.

Jay

This should be fixed in my latest build if you have installed my DSM 6.2 package...
What domoticz version do you tested?
I recompiled the usbserial package for apollolake just in case you can try : http://www.jadahl.com/drivers_6.2/?arch=apollolake
And I checked that this is compiled with 4.4.59+ for sure.
If this not work, you have to check if you have some old drivers installed on your NAS.
Delete all old drivers and reinstall.

I signed up to contact you about issues with the driver package and my Synology 918, but I see you have a new driver package now, I'll give that a go.

But the issue I had was that my HUSBZB wasn't coming up in the tty list. After some digging I found that in /lib/modules the drivers weren't listed in there.

I'll see how it goes after the new package tonight

Thanks jumbotroll, the updated package worked for me. Appreciate all your work mate, I'll send you some money as appreciation.

When it comes to DSM updates, should we wait until you have released a driver package for that version?

eatoff wrote: ↑Thursday 13 June 2019 3:33 Thanks jumbotroll, the updated package worked for me. Appreciate all your work mate, I'll send you some money as appreciation.

When it comes to DSM updates, should we wait until you have released a driver package for that version?

Q: When it comes to DSM updates, should we wait until you have released a driver package for that version?
A: That I don't know because that depends on if synology update the linux kernel or not..

Running build 891 now

everything seems to run smooth.
have the following devices

FGD-212 (scene functionality working)
FGWPF gen5
Qubino ZMNHADX (need to mod config file but then working)
Hue bridge gen2
RFXCOM-XL
zstick Gen5

Gravityz wrote: ↑Friday 14 June 2019 11:42 Running build 891 now

everything seems to run smooth.
have the following devices

FGD-212 (scene functionality working)
FGWPF gen5
Qubino ZMNHADX (need to mod config file but then working)
Hue bridge gen2
RFXCOM-XL
zstick Gen5

Great!
Running this version on my DS712+ to, and seems to be very stable..

It may take a while for the next beta update to synology. I have problems with the latest beta version of openzwave 1.6.764 killing domoticz and I have not quite been able to analyze/debug what is the cause, as I have very limited time to work on this ..

ok,

they have changed something regarding the commandclasses so this might be the cause.
i do not see any other people complaining about the new build so maybee it is realted to the synology build only.

i am glad that this one is running stable also. now i do not need to go back to the 1.4 versions

Gravityz wrote: ↑Friday 14 June 2019 15:01 ok,

they have changed something regarding the commandclasses so this might be the cause.
i do not see any other people complaining about the new build so maybee it is realted to the synology build only.

i am glad that this one is running stable also. now i do not need to go back to the 1.4 versions

Testing latest domoticz beta with latest openzwave beta now, and seems to run stable.
I think the problem was that I was crosscompiling with an outdated sql version..
Building new domoticz beta tonight..

Domoticz V4.10902 (c)2012-2019 GizMoCuz
Build Hash: 5b6ad6d-modified, Date: 2019-06-12 20:36:26
OpenZWave: Version: 1.6-764-g210c300b-dirty

Sjaakios wrote: ↑Monday 03 June 2019 10:02

schumi2004 wrote: ↑Sunday 21 April 2019 12:06

jumbotroll wrote: ↑Friday 19 April 2019 16:07

Nothing changed in the package only updated domoticz from latest source.
Maybe something went wrong when you updated?
I have build the latest domoticz 4.10603 Alpine you can test or if that not work, maybe try to reinstall the plugin.

My apologies for my late reply but just installed version 4.10603 and the error message regarding SSH client is gone, script is working fine now.
It looks like something was wrong in version 10602 regarding SSH client then.

Hi schumi, did you ever experience this issue again? I have the exact same error message, i'm running on version 4.10717, build hash b38b49e-modified. Any idea's how to get this resolved?

Hi jumbotroll, i'm facing this exact same issue as schumi had befor. I have exactly no idea how this building these packages works, but could there be something in the qoric build regarding inclusion of the SSH client?
This plugin worked on your latest build, tried reinstalling the plugin, reinstalling domoticz with a new version of the plugin, keep getting the same issue... pullig out my hair here!

Sjaakios wrote: ↑Friday 14 June 2019 20:45

Sjaakios wrote: ↑Monday 03 June 2019 10:02

schumi2004 wrote: ↑Sunday 21 April 2019 12:06
My apologies for my late reply but just installed version 4.10603 and the error message regarding SSH client is gone, script is working fine now.
It looks like something was wrong in version 10602 regarding SSH client then.

Hi schumi, did you ever experience this issue again? I have the exact same error message, i'm running on version 4.10717, build hash b38b49e-modified. Any idea's how to get this resolved?

Hi jumbotroll, i'm facing this exact same issue as schumi had befor. I have exactly no idea how this building these packages works, but could there be something in the qoric build regarding inclusion of the SSH client?
This plugin worked on your latest build, tried reinstalling the plugin, reinstalling domoticz with a new version of the plugin, keep getting the same issue... pullig out my hair here!

I don't know why you got this error.
Have you tested latest beta build..
I'm building domoticz with python plugin version V4.10902 tonight. check latest python version here: http://www.jadahl.com/domoticz_beta_6.2_python/

Is there any way the package can be run under a different user than root?

My Syno was infected with a worm this week (see other part of this forum) and I would like to prevent that in the future...