Announcement

**Rupp** · October 16, 2020, 09:22 PM

To remove the CMD box you will want to uncheck the Developer Mode found in Setup > General > Other Settings

**rebel3** · October 19, 2020, 10:30 AM

Thanks Rupp for pointing me to the Developer Mode - I found it on the Installed Plug-Ins Page. ( That solved the CMD boxes.)

Any idea on the Error Message that shows in the log?

And more importantly why none of my X10 devices transferred with the CM15A tab ? ( and they no longer work on X10 )

Any idea hope I can just get the CM15A tab back ? or rebuild the device ?

Thanks for any help.

**mfisher** · October 19, 2020, 05:58 PM

rebel3 Sorry that you're having these issues. First you should know that the CM15a plugin for Linux is a COMPLETELY different plugin than the Windows version and the internal data structures are very likely different. I have never tested moving a HS data file between Linux and Windows or vise versa.

Just so I'm clear: you were using HS3-Pi on a Zee S2 (R-Pi) and you've moved that HS data file to a Win 10 machine running HS3 - correct?

What version of the CM15a plugin was used on your Zee S2?

From the log snip you provided it appears that the Windows CM15a v12 plugin is initializing but either it or HS3 is not able to read the CM15a device data in the HS file stored by the Linux version; hence the de-serializing error in your log.

As a quick test, backup your current HS3 data file and and create a brand new blank HS file. Then enable the CM15a plugin, try creating a new CM15a device and test if you can control the device from HS. If this is all working then the issue is an incompatibility between the Linux and Windows versions of the plugin and it will require some effort on my part to evaluate what the issue is and whether there is a way to fix it.

If you zip up your troublesome HS3 data file and post it (or send it via a PM) I will load it up and investigate what's going on.

Please note that I inherited the X10 & CM15a plugins from HST (I'm not the original author) and have been supporting these since HST decided to discontinue support for this aging technology. I do this on a voluntary basis when I'm able. Unfortunately I'm completely swamped with my business (http://www.solidterrainmodelng.com) so I cannot promise a quick turn solution but will take a look at it when I am able.

**rebel3** · October 20, 2020, 11:21 AM

Mark,

Yes, running HS3-pi on the Zee S2 and the version is 3.0.0.5
When I first tried the HS3 on Windows 10 I was also using the legacy X15 version and have upgraded to 3.0.0.12 just to try it. (nothing different)

Thanks for the information on the plugins being completely different.

I ordered another CM15A (ebay) yesterday so I can work on the Windows Version without continually switching the CM15A back and forth. (probably a week away)
My plan is to get on Windows 10 HS3 so I can convert to HS4 .. I tried to move directly to HS4 and that was a disaster. (mostly Zwave .. and I backed off)

The main reason for the move was the problems with the X10 devices not providing event triggers when they change, and I was hoping this was solved on the Windows version or the HS4 version. Initial testing on windows 10 stills shows that that has not changed. Note: .. even on the Linux Zee S2 if a CMD is received from the CM15A (by wireless remote or another wired sender) the event triggers work fine (always have) .. event triggers do not work if you make a change directly on the device under home or by the HS Touch or if the device change comes in from MQTT. ( Event triggers work well with all Z Wave devices whenever or however their state changes. )

If I create a new X15 device on Window 10 HS3 Pro software ... the CM15 tab shows and the device works. (However, still no event signaling).

Where would I look to be able to see the CM15 stored configuration in the database ? I can see the devices, I can't seem to find the table with the detail.
I'd like to see what is or isn't stored there for my devices.

Thanks again for you help,
and keep up the great work on these plugins!

Kris

**mfisher** · October 20, 2020, 02:54 PM

Hi Kris,

Thanks for confirming you were using the older v.5 version of the plugin under Linux. Please note that there is a v.6 version that adds support for HS4 under Linux and you can get this from the BETA page here in the forum.

The main reason for the move was the problems with the X10 devices not providing event triggers when they change... event triggers do not work if you make a change directly on the device under home or by the HS Touch or if the device change comes in from MQTT.

Can you give me an example or two of a trigger that does not work? Please note that the plugin is only involved for X10 data received triggers and is not involved for device related triggers, such as "When Device XYZ changes to ON" and then the device is changed either by the user on the devices page or by another plugin.

The data for CM15a devices is stored within each device in the HS database (in PlugExtraData) as a serialized byte stream and this data is managed by the plugin. Unfortunately there is no way for you to view this info but there's nothing special in there, here's a list of what is stored:
Housecode, DeviceCode, CurrentValue, LastCommand, LastData1, LastData2, DeviceType, DimType.

If I create a new X15 device on Window 10 HS3 Pro software ... the CM15 tab shows and the device works. (However, still no event signaling).

Just to confirm, are you saying that the plugin is working under Win10 with HS3 and that you can send and receive X10 data on the powerline?

Will you be providing a copy of your HS file (from your Zee) for me to evaluate on my test system so I can try to see where this issue is occurring?

Announcement

Connected, waiting to be initialized...

Connected, waiting to be initialized...

Comment

Comment

Comment

Comment

Comment