"platform": "WizSmarthome",
            "name": "WizSmarthome"
        }
    ]
}

Environment:

Node.js Version: v14.15.4
NPM Version: v6.14.11
Homebridge Version: v1.2.5
Operating System: Raspbian
Process Supervisor: hb-service

I have now just realised the only accessories that are 'broken' are my Fan and all of my Switch accessories; and what they all have in common is no polling config as per your config.json example. Any tips for what I may need to do here to fix them? Could have saved myself a very lengthy issue creation above if I had realised that sooner -_- ah night shift brain on my days off...

I have now just realised the only accessories that are 'broken' are my Fan and all of my Switch accessories; and what they all have in common is no polling config as per your config.json example. Any tips for what I may need to do here to fix them? Could have saved myself a very lengthy issue creation above if I had realised that sooner -_- ah night shift brain on my days off...

Thanks Mitch,
I'll look at in when I wake up
TTFN,
John
On Wed, Jan 13, 2021 at 4:42 AM Mitch Williams<EMAIL_ADDRESS>wrote:

I have now just realised the only accessories that are 'broken' are my Fan
and all of my Switch accessories; and what they all have in common is no
polling config as per your config.json example. Any tips for what I may
need to do here to fix them? Could have saved myself a very lengthy issue
creation above if I had realised that sooner -_- ah night shift brain on my
days off...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-759330846,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX4I4HKSX5IOROAA75DSZVTJXANCNFSM4WAQJ7YQ
.

Thanks Mitch,
I'll look at in when I wake up
TTFN,
John
On Wed, Jan 13, 2021 at 4:42 AM Mitch Williams<EMAIL_ADDRESS>wrote:

I have now just realised the only accessories that are 'broken' are my Fan
and all of my Switch accessories; and what they all have in common is no
polling config as per your config.json example. Any tips for what I may
need to do here to fix them? Could have saved myself a very lengthy issue
creation above if I had realised that sooner -_- ah night shift brain on my
days off...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-759330846,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX4I4HKSX5IOROAA75DSZVTJXANCNFSM4WAQJ7YQ
.

I tried adding 'polling' to these devices in my config.json like the other accessories that require polling and that did not make any difference.

I tried adding 'polling' to these devices in my config.json like the other accessories that require polling and that did not make any difference.

Hey Mitch,
I'll assume you did the rm -rf of thé .homebridge/accessories and persist
as I mentioned before each attempt.  It's the best way to start out fresh
each time.
I'm still not up yet. Breakfast has yet to be served. Your my #1 priority
today.
Ttyl,
John
On Wed, Jan 13, 2021 at 8:19 AM Mitch Williams<EMAIL_ADDRESS>wrote:

I tried adding 'polling' to these devices in my config.json like the
other accessories that require polling and that did not make any difference.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-759443108,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX4DQYQFNSIROSAAJ53SZWMX5ANCNFSM4WAQJ7YQ
.

Hey Mitch,
I'll assume you did the rm -rf of thé .homebridge/accessories and persist
as I mentioned before each attempt.  It's the best way to start out fresh
each time.
I'm still not up yet. Breakfast has yet to be served. Your my #1 priority
today.
Ttyl,
John
On Wed, Jan 13, 2021 at 8:19 AM Mitch Williams<EMAIL_ADDRESS>wrote:

I tried adding 'polling' to these devices in my config.json like the
other accessories that require polling and that did not make any difference.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-759443108,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX4DQYQFNSIROSAAJ53SZWMX5ANCNFSM4WAQJ7YQ
.

I did not try that method yet; I used the "restartRecover": false instead. I can still give that a go if you think it will make a difference?

I did not try that method yet; I used the "restartRecover": false instead. I can still give that a go if you think it will make a difference?

I did not see any Gets in your log and looked at your config.json and noticed the polling missing and can now understand what could have gone wrong.  Reading further, you seem to have noticed too.  The cache thing would have bit you after adding polling back in.
breakfast is about ready,
Ttyl
John

I did not see any Gets in your log and looked at your config.json and noticed the polling missing and can now understand what could have gone wrong.  Reading further, you seem to have noticed too.  The cache thing would have bit you after adding polling back in.
breakfast is about ready,
Ttyl
John

Awesome work John :) now a question for my config. Are fans and switches supposed to have a polling section in them? I always assumed no as the config.json example does not have it.

Awesome work John :) now a question for my config. Are fans and switches supposed to have a polling section in them? I always assumed no as the config.json example does not have it.

There are two types of polling.  Accessory polling "polling": true   and
characteristic polling  polling:{ characteristic:,
"timeout": < value > }
If no polling is provided at all, no polling is done. With "fetch":
"Always", the default, then again no polling is done. However if HomeKit
wants the value then Get is called. Get is the same mechanism polling uses,
but it is not polling, which is a background task.
Your fix is in GitHub, not in NPM.  I'm trying to resolve the caching of
Cmd4 directives before publishing the fix.
Ttyl,
John
On Wed, Jan 13, 2021 at 9:09 PM Mitch Williams<EMAIL_ADDRESS>wrote:

Awesome work John :) now a question for my config. Are fans and switches
supposed to have a polling section in them? I always assumed no as the
config.json example does not have it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-759877445,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX7D2ULUNSKHXONTVZLSZZG6FANCNFSM4WAQJ7YQ
.

There are two types of polling.  Accessory polling "polling": true   and
characteristic polling  polling:{ characteristic:,
"timeout": < value > }
If no polling is provided at all, no polling is done. With "fetch":
"Always", the default, then again no polling is done. However if HomeKit
wants the value then Get is called. Get is the same mechanism polling uses,
but it is not polling, which is a background task.
Your fix is in GitHub, not in NPM.  I'm trying to resolve the caching of
Cmd4 directives before publishing the fix.
Ttyl,
John
On Wed, Jan 13, 2021 at 9:09 PM Mitch Williams<EMAIL_ADDRESS>wrote:

Awesome work John :) now a question for my config. Are fans and switches
supposed to have a polling section in them? I always assumed no as the
config.json example does not have it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-759877445,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX7D2ULUNSKHXONTVZLSZZG6FANCNFSM4WAQJ7YQ
.

Thanks for the explanation John :) and no rush, I can still use the main app for my air con in the mean time.

Thanks for the explanation John :) and no rush, I can still use the main app for my air con in the mean time.

Just published 3.0.4 that addresses this issue and some caching issues as well.
Sorry for the inconvenience,
John

Just published 3.0.4 that addresses this issue and some caching issues as well.
Sorry for the inconvenience,
John

John unfortunately this has not fixed the issue for me with those accessories; I have made sure they were not cached by setting ”restartRecover”: true.
Do I need to do something different with my config with this update? Perhaps the way I use my shell script is no longer relevant? Would I expect to have to change how that is set up?

John unfortunately this has not fixed the issue for me with those accessories; I have made sure they were not cached by setting ”restartRecover”: true.
Do I need to do something different with my config with this update? Perhaps the way I use my shell script is no longer relevant? Would I expect to have to change how that is set up?

Ignoring my TV switch for now and focusing on the fan and switches; here is where my code is for these:
mitch7391/cmd4-E-Zone-MyAir

Ignoring my TV switch for now and focusing on the fan and switches; here is where my code is for these:
mitch7391/cmd4-E-Zone-MyAir

Hey Mitch,
Cool!,
I need to reference these in my documentation. I see a GitHub commit in the
near future :-)
if you have any more issues, please let me know.
I tried to work on a tool that would generate the config.schema.json file
for config-ui-x based on the Cmd4 tables. It is my next task.  It was to
difficult and would have delayed 3.0 to much.  I will go back and have
another look.
If you think of other features that would help you, I'd like to help. I had
thought of a scripting language. There are some undocumented features like
constants within the state_cmd that does work. The variable one does not do
anything more than the constant does.  I had a private branch that would do
http instead of shell, but there are just so many options, I never finished
it.
Keep stuff like that in mind.  It's winter and Covid.  Can't do much
anything else.
TTFN,
John
On Fri, Jan 15, 2021 at 8:38 AM Mitch Williams<EMAIL_ADDRESS>wrote:

Ignoring my TV switch for now and focusing on the fan and switches; here
is where my code is for these:
mitch7391/cmd4-E-Zone-MyAir
https://github.com/mitch7391/cmd4-E-Zone-MyAir/tree/master/One Constant Zone
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-760946917,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX2L5SNAI7IDL2ETRKLS2BAO3ANCNFSM4WAQJ7YQ
.

Hey Mitch,
Cool!,
I need to reference these in my documentation. I see a GitHub commit in the
near future :-)
if you have any more issues, please let me know.
I tried to work on a tool that would generate the config.schema.json file
for config-ui-x based on the Cmd4 tables. It is my next task.  It was to
difficult and would have delayed 3.0 to much.  I will go back and have
another look.
If you think of other features that would help you, I'd like to help. I had
thought of a scripting language. There are some undocumented features like
constants within the state_cmd that does work. The variable one does not do
anything more than the constant does.  I had a private branch that would do
http instead of shell, but there are just so many options, I never finished
it.
Keep stuff like that in mind.  It's winter and Covid.  Can't do much
anything else.
TTFN,
John
On Fri, Jan 15, 2021 at 8:38 AM Mitch Williams<EMAIL_ADDRESS>wrote:

Ignoring my TV switch for now and focusing on the fan and switches; here
is where my code is for these:
mitch7391/cmd4-E-Zone-MyAir
https://github.com/mitch7391/cmd4-E-Zone-MyAir/tree/master/One Constant Zone
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-760946917,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX2L5SNAI7IDL2ETRKLS2BAO3ANCNFSM4WAQJ7YQ
.

You are more than welcome to; it was actually developer TimofeyK who originally helped me put these together as I was learning as I went. I have since created a more complicated version on my page for people with different setups of the same air con and has now been helping me with the TV one I am working on.
That is exciting that you have been working on the config.scema.json for cmd4! I will definitely have a think of some other features and let you know :)
With my current issue however, should we open this back up and leave it with you? Or is there anything I can still provide that may help?

You are more than welcome to; it was actually developer TimofeyK who originally helped me put these together as I was learning as I went. I have since created a more complicated version on my page for people with different setups of the same air con and has now been helping me with the TV one I am working on.
That is exciting that you have been working on the config.scema.json for cmd4! I will definitely have a think of some other features and let you know :)
With my current issue however, should we open this back up and leave it with you? Or is there anything I can still provide that may help?

I submitted 3.04, does that not address everything?
On Fri, Jan 15, 2021 at 9:31 PM Mitch Williams<EMAIL_ADDRESS>wrote:

You are more than welcome to; it was actually developer TimofeyK who
originally helped me put these together as I was learning as I went. I have
since created a more complicated version on my page for people with
different setups of the same air con and has now been helping me with the
TV one I am working on.
That is exciting that you have been working on the config.scema.json for
cmd4! I will definitely have a think of some other features and let you
know :)
With my current issue however, should we open this back up and leave it
with you? Or is there anything I can still provide that may help?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761297042,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3HCFY5DGTS4HJKEG3S2D3A3ANCNFSM4WAQJ7YQ
.

I submitted 3.04, does that not address everything?
On Fri, Jan 15, 2021 at 9:31 PM Mitch Williams<EMAIL_ADDRESS>wrote:

You are more than welcome to; it was actually developer TimofeyK who
originally helped me put these together as I was learning as I went. I have
since created a more complicated version on my page for people with
different setups of the same air con and has now been helping me with the
TV one I am working on.
That is exciting that you have been working on the config.scema.json for
cmd4! I will definitely have a think of some other features and let you
know :)
With my current issue however, should we open this back up and leave it
with you? Or is there anything I can still provide that may help?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761297042,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3HCFY5DGTS4HJKEG3S2D3A3ANCNFSM4WAQJ7YQ
.

No it did not it seems John, sorry haha that was what my comment was about after you closed the issue :)

No it did not it seems John, sorry haha that was what my comment was about after you closed the issue :)

Hi Mitch,
I just published Cmd4 v3.0.5.   Another person was seeing a backward compatibility issue and I resolved theirs which might trip yours up as well.
I added some Kudos your way as well in the documentation ;-)
ttfn,
John

Hi Mitch,
I just published Cmd4 v3.0.5.   Another person was seeing a backward compatibility issue and I resolved theirs which might trip yours up as well.
I added some Kudos your way as well in the documentation ;-)
ttfn,
John

I do appreciate the special thanks :)
It would seem that patch v3.0.5 still does not fix the issue. Looking further things these two types of accessories have in common other than the no polling in the config, is both of these use the characteristic on. I have also further noted that the accessories always reflect an 'inverted' state on Homekit; if the device is actually 'off', it reflects as 'on' in Homekit. If then use its manufacturers app to turn it 'on', it will then report as 'off' in Homekit. Has anything changed with the characteristic on at all or in how it is supposed to be used?

I do appreciate the special thanks :)
It would seem that patch v3.0.5 still does not fix the issue. Looking further things these two types of accessories have in common other than the no polling in the config, is both of these use the characteristic on. I have also further noted that the accessories always reflect an 'inverted' state on Homekit; if the device is actually 'off', it reflects as 'on' in Homekit. If then use its manufacturers app to turn it 'on', it will then report as 'off' in Homekit. Has anything changed with the characteristic on at all or in how it is supposed to be used?

Hey Mitch,
Nothing should have changed.   Can you send me your config.json and I'll
play with it here.
I accidentally published a config.schéma.  I'll publish 3.0.6, but there is
nothing in it except removing this file. Just to give you a heads up.
ttfn,
John
On Sat, Jan 16, 2021 at 9:25 PM Mitch Williams<EMAIL_ADDRESS>wrote:

I do appreciate the special thanks :)
It would seem that patch v3.0.5 still does not fix the issue. Looking
further things these two types of accessories have in common other than the
no polling in the config, is both of these use the characteristic on. I
have also further noted that the accessories always reflect an 'inverted'
state on Homekit; if the device is actually 'off', it reflects as 'on' in
Homekit. If then use its manufacturers app to turn it 'on', it will then
report as 'off' in Homekit. Has anything changed with the characteristic
on at all or in how it is supposed to be used?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761717781,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3PUOXWCTUZ3TH4SK3S2JDBDANCNFSM4WAQJ7YQ
.

Hey Mitch,
Nothing should have changed.   Can you send me your config.json and I'll
play with it here.
I accidentally published a config.schéma.  I'll publish 3.0.6, but there is
nothing in it except removing this file. Just to give you a heads up.
ttfn,
John
On Sat, Jan 16, 2021 at 9:25 PM Mitch Williams<EMAIL_ADDRESS>wrote:

I do appreciate the special thanks :)
It would seem that patch v3.0.5 still does not fix the issue. Looking
further things these two types of accessories have in common other than the
no polling in the config, is both of these use the characteristic on. I
have also further noted that the accessories always reflect an 'inverted'
state on Homekit; if the device is actually 'off', it reflects as 'on' in
Homekit. If then use its manufacturers app to turn it 'on', it will then
report as 'off' in Homekit. Has anything changed with the characteristic
on at all or in how it is supposed to be used?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761717781,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3PUOXWCTUZ3TH4SK3S2JDBDANCNFSM4WAQJ7YQ
.

Interesting... Here is just my cmd4 config, if you want m y entire config.json it is in my original post:
{
            "platform": "Cmd4",
            "name": "Cmd4",
            "outputConstants": false,
            "restartRecover": false,
            "accessories": [
                {
                    "type": "Switch",
                    "displayName": "My_Switch",
                    "on": "FALSE",
                    "name": "Hisense",
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/HisenseSwitch.sh"
                },
                {
                    "type": "Television",
                    "displayName": "TV_Combo",
                    "publishExternally": true,
                    "category": "TELEVISION",
                    "active": "ACTIVE",
                    "activeIdentifier": 1,
                    "configuredName": "TV_Combo",
                    "sleepDiscoveryMode": "ALWAYS_DISCOVERABLE",
                    "linkedTypes": [
                        {
                            "type": "InputSource",
                            "displayName": "TV",
                            "configuredName": "TV",
                            "currentVisibilityState": "SHOWN",
                            "inputSourceType": "TUNER",
                            "inputDeviceType": "TV",
                            "isConfigured": "CONFIGURED",
                            "identifier": 0,
                            "targetVisibilityState": "SHOWN",
                            "name": "TV"
                        },
                        {
                            "type": "InputSource",
                            "displayName": "HDMI1",
                            "configuredName": "HDMI1",
                            "currentVisibilityState": "SHOWN",
                            "inputSourceType": "HDMI",
                            "isConfigured": "CONFIGURED",
                            "identifier": 2,
                            "targetVisibilityState": "SHOWN",
                            "name": "HDMI1"
                        }
                    ],
                    "polling": [
                        {
                            "characteristic": "active",
                            "interval": 50,
                            "timeout": 5000
                        },
                        {
                            "characteristic": "activeIdentifier",
                            "interval": 50,
                            "timeout": 5000
                        }
                    ],
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/HisenseTV.sh"
                },
                {
                    "type": "TemperatureSensor",
                    "displayName": "My_TemperatureSensor",
                    "currentTemperature": 50,
                    "statusFault": "NO_FAULT",
                    "name": "Living_Room",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "polling": [
                        {
                            "characteristic": "currentTemperature",
                            "interval": 50,
                            "timeout": 8000
                        }
                    ],
                    "stateChangeResponseTime": 3,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z01"
                },
                {
                    "type": "TemperatureSensor",
                    "displayName": "My_TemperatureSensor",
                    "currentTemperature": 50,
                    "statusFault": "NO_FAULT",
                    "name": "Theatre_Room",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "polling": [
                        {
                            "characteristic": "currentTemperature",
                            "interval": 50,
                            "timeout": 8000
                        }
                    ],
                    "stateChangeResponseTime": 3,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z02"
                },
                {
                    "type": "TemperatureSensor",
                    "displayName": "My_TemperatureSensor",
                    "currentTemperature": 50,
                    "statusFault": "NO_FAULT",
                    "name": "Master_Room",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "polling": [
                        {
                            "characteristic": "currentTemperature",
                            "interval": 50,
                            "timeout": 8000
                        }
                    ],
                    "stateChangeResponseTime": 3,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z03"
                },
                {
                    "type": "TemperatureSensor",
                    "displayName": "My_TemperatureSensor",
                    "currentTemperature": 50,
                    "statusFault": "NO_FAULT",
                    "name": "Craft_Room",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "polling": [
                        {
                            "characteristic": "currentTemperature",
                            "interval": 50,
                            "timeout": 8000
                        }
                    ],
                    "stateChangeResponseTime": 3,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z04"
                },
                {
                    "type": "TemperatureSensor",
                    "displayName": "My_TemperatureSensor",
                    "currentTemperature": 50,
                    "statusFault": "NO_FAULT",
                    "name": "Spare_Room",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "polling": [
                        {
                            "characteristic": "currentTemperature",
                            "interval": 50,
                            "timeout": 8000
                        }
                    ],
                    "stateChangeResponseTime": 3,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z05"
                },
                {
                    "type": "TemperatureSensor",
                    "displayName": "My_TemperatureSensor",
                    "currentTemperature": 50,
                    "statusFault": "NO_FAULT",
                    "name": "Guest_Room",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "polling": [
                        {
                            "characteristic": "currentTemperature",
                            "interval": 50,
                            "timeout": 8000
                        }
                    ],
                    "stateChangeResponseTime": 3,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z06"
                },
                {
                    "type": "Switch",
                    "displayName": "My_Switch",
                    "on": "FALSE",
                    "name": "Theatre",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z02"
                },
                {
                    "type": "Switch",
                    "displayName": "My_Switch",
                    "on": "FALSE",
                    "name": "Bedroom",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z03"
                },
                {
                    "type": "Switch",
                    "displayName": "My_Switch",
                    "on": "FALSE",
                    "name": "Craft",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z04"
                },
                {
                    "type": "Switch",
                    "displayName": "My_Switch",
                    "on": "FALSE",
                    "name": "Spare",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z05"
                },
                {
                    "type": "Switch",
                    "displayName": "My_Switch",
                    "on": "FALSE",
                    "name": "Guest",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z06"
                },
                {
                    "type": "Fan",
                    "on": "FALSE",
                    "name": "Fan",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/ezone.sh"
                },
                {
                    "type": "Thermostat",
                    "displayName": "My_Thermostat",
                    "currentHeatingCoolingState": "OFF",
                    "targetHeatingCoolingState": "OFF",
                    "currentTemperature": 50,
                    "targetTemperature": 37,
                    "temperatureDisplayUnits": "CELCIUS",
                    "name": "My_Thermostat",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "polling": [
                        {
                            "characteristic": "currentHeatingCoolingState",
                            "interval": 60,
                            "timeout": 8000
                        },
                        {
                            "characteristic": "currentTemperature",
                            "interval": 60,
                            "timeout": 8000
                        },
                        {
                            "characteristic": "targetTemperature",
                            "interval": 60,
                            "timeout": 8000
                        }
                    ],
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/ezone.sh"
                }
            ]
        },

All of my switches in this config and the fan are the only ones affected. My shell scripts are linked in above comments except for the first switch referencing HisenseSwitch.sh (let's ignore that one now so you aren't looking at too many shell scripts). Please let me know if you need anything else!

Interesting... Here is just my cmd4 config, if you want m y entire config.json it is in my original post:
{
            "platform": "Cmd4",
            "name": "Cmd4",
            "outputConstants": false,
            "restartRecover": false,
            "accessories": [
                {
                    "type": "Switch",
                    "displayName": "My_Switch",
                    "on": "FALSE",
                    "name": "Hisense",
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/HisenseSwitch.sh"
                },
                {
                    "type": "Television",
                    "displayName": "TV_Combo",
                    "publishExternally": true,
                    "category": "TELEVISION",
                    "active": "ACTIVE",
                    "activeIdentifier": 1,
                    "configuredName": "TV_Combo",
                    "sleepDiscoveryMode": "ALWAYS_DISCOVERABLE",
                    "linkedTypes": [
                        {
                            "type": "InputSource",
                            "displayName": "TV",
                            "configuredName": "TV",
                            "currentVisibilityState": "SHOWN",
                            "inputSourceType": "TUNER",
                            "inputDeviceType": "TV",
                            "isConfigured": "CONFIGURED",
                            "identifier": 0,
                            "targetVisibilityState": "SHOWN",
                            "name": "TV"
                        },
                        {
                            "type": "InputSource",
                            "displayName": "HDMI1",
                            "configuredName": "HDMI1",
                            "currentVisibilityState": "SHOWN",
                            "inputSourceType": "HDMI",
                            "isConfigured": "CONFIGURED",
                            "identifier": 2,
                            "targetVisibilityState": "SHOWN",
                            "name": "HDMI1"
                        }
                    ],
                    "polling": [
                        {
                            "characteristic": "active",
                            "interval": 50,
                            "timeout": 5000
                        },
                        {
                            "characteristic": "activeIdentifier",
                            "interval": 50,
                            "timeout": 5000
                        }
                    ],
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/HisenseTV.sh"
                },
                {
                    "type": "TemperatureSensor",
                    "displayName": "My_TemperatureSensor",
                    "currentTemperature": 50,
                    "statusFault": "NO_FAULT",
                    "name": "Living_Room",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "polling": [
                        {
                            "characteristic": "currentTemperature",
                            "interval": 50,
                            "timeout": 8000
                        }
                    ],
                    "stateChangeResponseTime": 3,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z01"
                },
                {
                    "type": "TemperatureSensor",
                    "displayName": "My_TemperatureSensor",
                    "currentTemperature": 50,
                    "statusFault": "NO_FAULT",
                    "name": "Theatre_Room",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "polling": [
                        {
                            "characteristic": "currentTemperature",
                            "interval": 50,
                            "timeout": 8000
                        }
                    ],
                    "stateChangeResponseTime": 3,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z02"
                },
                {
                    "type": "TemperatureSensor",
                    "displayName": "My_TemperatureSensor",
                    "currentTemperature": 50,
                    "statusFault": "NO_FAULT",
                    "name": "Master_Room",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "polling": [
                        {
                            "characteristic": "currentTemperature",
                            "interval": 50,
                            "timeout": 8000
                        }
                    ],
                    "stateChangeResponseTime": 3,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z03"
                },
                {
                    "type": "TemperatureSensor",
                    "displayName": "My_TemperatureSensor",
                    "currentTemperature": 50,
                    "statusFault": "NO_FAULT",
                    "name": "Craft_Room",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "polling": [
                        {
                            "characteristic": "currentTemperature",
                            "interval": 50,
                            "timeout": 8000
                        }
                    ],
                    "stateChangeResponseTime": 3,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z04"
                },
                {
                    "type": "TemperatureSensor",
                    "displayName": "My_TemperatureSensor",
                    "currentTemperature": 50,
                    "statusFault": "NO_FAULT",
                    "name": "Spare_Room",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "polling": [
                        {
                            "characteristic": "currentTemperature",
                            "interval": 50,
                            "timeout": 8000
                        }
                    ],
                    "stateChangeResponseTime": 3,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z05"
                },
                {
                    "type": "TemperatureSensor",
                    "displayName": "My_TemperatureSensor",
                    "currentTemperature": 50,
                    "statusFault": "NO_FAULT",
                    "name": "Guest_Room",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "polling": [
                        {
                            "characteristic": "currentTemperature",
                            "interval": 50,
                            "timeout": 8000
                        }
                    ],
                    "stateChangeResponseTime": 3,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z06"
                },
                {
                    "type": "Switch",
                    "displayName": "My_Switch",
                    "on": "FALSE",
                    "name": "Theatre",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z02"
                },
                {
                    "type": "Switch",
                    "displayName": "My_Switch",
                    "on": "FALSE",
                    "name": "Bedroom",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z03"
                },
                {
                    "type": "Switch",
                    "displayName": "My_Switch",
                    "on": "FALSE",
                    "name": "Craft",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z04"
                },
                {
                    "type": "Switch",
                    "displayName": "My_Switch",
                    "on": "FALSE",
                    "name": "Spare",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z05"
                },
                {
                    "type": "Switch",
                    "displayName": "My_Switch",
                    "on": "FALSE",
                    "name": "Guest",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/zones.sh",
                    "state_cmd_suffix": "z06"
                },
                {
                    "type": "Fan",
                    "on": "FALSE",
                    "name": "Fan",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/ezone.sh"
                },
                {
                    "type": "Thermostat",
                    "displayName": "My_Thermostat",
                    "currentHeatingCoolingState": "OFF",
                    "targetHeatingCoolingState": "OFF",
                    "currentTemperature": 50,
                    "targetTemperature": 37,
                    "temperatureDisplayUnits": "CELCIUS",
                    "name": "My_Thermostat",
                    "Manufacturer": "Advantage Air Australia",
                    "Model": "e-zone",
                    "SerialNumber": "Fujitsu e-zone2",
                    "polling": [
                        {
                            "characteristic": "currentHeatingCoolingState",
                            "interval": 60,
                            "timeout": 8000
                        },
                        {
                            "characteristic": "currentTemperature",
                            "interval": 60,
                            "timeout": 8000
                        },
                        {
                            "characteristic": "targetTemperature",
                            "interval": 60,
                            "timeout": 8000
                        }
                    ],
                    "stateChangeResponseTime": 1,
                    "state_cmd": "bash /home/pi/ezone.sh"
                }
            ]
        },

All of my switches in this config and the fan are the only ones affected. My shell scripts are linked in above comments except for the first switch referencing HisenseSwitch.sh (let's ignore that one now so you aren't looking at too many shell scripts). Please let me know if you need anything else!

Sorry about that, it's getting late.  Lights out.  I will look at it first
chance I get.  I might have a thought, we shall see.
Night,
John
On Sat, Jan 16, 2021 at 9:54 PM Mitch Williams<EMAIL_ADDRESS>wrote:

Interesting... Here is just my cmd4 config, if you want m y entire
config.json it is in my original post:
{
"platform": "Cmd4",
"name": "Cmd4",
"outputConstants": false,
"restartRecover": false,
"accessories": [
{
"type": "Switch",
"displayName": "My_Switch",
"on": "FALSE",
"name": "Hisense",
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/HisenseSwitch.sh"
},
{
"type": "Television",
"displayName": "TV_Combo",
"publishExternally": true,
"category": "TELEVISION",
"active": "ACTIVE",
"activeIdentifier": 1,
"configuredName": "TV_Combo",
"sleepDiscoveryMode": "ALWAYS_DISCOVERABLE",
"linkedTypes": [
{
"type": "InputSource",
"displayName": "TV",
"configuredName": "TV",
"currentVisibilityState": "SHOWN",
"inputSourceType": "TUNER",
"inputDeviceType": "TV",
"isConfigured": "CONFIGURED",
"identifier": 0,
"targetVisibilityState": "SHOWN",
"name": "TV"
},
{
"type": "InputSource",
"displayName": "HDMI1",
"configuredName": "HDMI1",
"currentVisibilityState": "SHOWN",
"inputSourceType": "HDMI",
"isConfigured": "CONFIGURED",
"identifier": 2,
"targetVisibilityState": "SHOWN",
"name": "HDMI1"
}
],
"polling": [
{
"characteristic": "active",
"interval": 50,
"timeout": 5000
},
{
"characteristic": "activeIdentifier",
"interval": 50,
"timeout": 5000
}
],
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/HisenseTV.sh"
},
{
"type": "TemperatureSensor",
"displayName": "My_TemperatureSensor",
"currentTemperature": 50,
"statusFault": "NO_FAULT",
"name": "Living_Room",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"polling": [
{
"characteristic": "currentTemperature",
"interval": 50,
"timeout": 8000
}
],
"stateChangeResponseTime": 3,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z01"
},
{
"type": "TemperatureSensor",
"displayName": "My_TemperatureSensor",
"currentTemperature": 50,
"statusFault": "NO_FAULT",
"name": "Theatre_Room",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"polling": [
{
"characteristic": "currentTemperature",
"interval": 50,
"timeout": 8000
}
],
"stateChangeResponseTime": 3,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z02"
},
{
"type": "TemperatureSensor",
"displayName": "My_TemperatureSensor",
"currentTemperature": 50,
"statusFault": "NO_FAULT",
"name": "Master_Room",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"polling": [
{
"characteristic": "currentTemperature",
"interval": 50,
"timeout": 8000
}
],
"stateChangeResponseTime": 3,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z03"
},
{
"type": "TemperatureSensor",
"displayName": "My_TemperatureSensor",
"currentTemperature": 50,
"statusFault": "NO_FAULT",
"name": "Craft_Room",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"polling": [
{
"characteristic": "currentTemperature",
"interval": 50,
"timeout": 8000
}
],
"stateChangeResponseTime": 3,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z04"
},
{
"type": "TemperatureSensor",
"displayName": "My_TemperatureSensor",
"currentTemperature": 50,
"statusFault": "NO_FAULT",
"name": "Spare_Room",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"polling": [
{
"characteristic": "currentTemperature",
"interval": 50,
"timeout": 8000
}
],
"stateChangeResponseTime": 3,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z05"
},
{
"type": "TemperatureSensor",
"displayName": "My_TemperatureSensor",
"currentTemperature": 50,
"statusFault": "NO_FAULT",
"name": "Guest_Room",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"polling": [
{
"characteristic": "currentTemperature",
"interval": 50,
"timeout": 8000
}
],
"stateChangeResponseTime": 3,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z06"
},
{
"type": "Switch",
"displayName": "My_Switch",
"on": "FALSE",
"name": "Theatre",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z02"
},
{
"type": "Switch",
"displayName": "My_Switch",
"on": "FALSE",
"name": "Bedroom",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z03"
},
{
"type": "Switch",
"displayName": "My_Switch",
"on": "FALSE",
"name": "Craft",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z04"
},
{
"type": "Switch",
"displayName": "My_Switch",
"on": "FALSE",
"name": "Spare",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z05"
},
{
"type": "Switch",
"displayName": "My_Switch",
"on": "FALSE",
"name": "Guest",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z06"
},
{
"type": "Fan",
"on": "FALSE",
"name": "Fan",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/ezone.sh"
},
{
"type": "Thermostat",
"displayName": "My_Thermostat",
"currentHeatingCoolingState": "OFF",
"targetHeatingCoolingState": "OFF",
"currentTemperature": 50,
"targetTemperature": 37,
"temperatureDisplayUnits": "CELCIUS",
"name": "My_Thermostat",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"polling": [
{
"characteristic": "currentHeatingCoolingState",
"interval": 60,
"timeout": 8000
},
{
"characteristic": "currentTemperature",
"interval": 60,
"timeout": 8000
},
{
"characteristic": "targetTemperature",
"interval": 60,
"timeout": 8000
}
],
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/ezone.sh"
}
]
},
All of my switches in this config and the fan are the only ones affected.
My shell scripts are linked in above comments except for the first switch
referencing HisenseSwitch.sh (let's ignore that one now so you aren't
looking at too many shell scripts). Please let me know if you need anything
else!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761721178,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX6DYVNCIDC5IQONFFDS2JGPTANCNFSM4WAQJ7YQ
.

Sorry about that, it's getting late.  Lights out.  I will look at it first
chance I get.  I might have a thought, we shall see.
Night,
John
On Sat, Jan 16, 2021 at 9:54 PM Mitch Williams<EMAIL_ADDRESS>wrote:

Interesting... Here is just my cmd4 config, if you want m y entire
config.json it is in my original post:
{
"platform": "Cmd4",
"name": "Cmd4",
"outputConstants": false,
"restartRecover": false,
"accessories": [
{
"type": "Switch",
"displayName": "My_Switch",
"on": "FALSE",
"name": "Hisense",
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/HisenseSwitch.sh"
},
{
"type": "Television",
"displayName": "TV_Combo",
"publishExternally": true,
"category": "TELEVISION",
"active": "ACTIVE",
"activeIdentifier": 1,
"configuredName": "TV_Combo",
"sleepDiscoveryMode": "ALWAYS_DISCOVERABLE",
"linkedTypes": [
{
"type": "InputSource",
"displayName": "TV",
"configuredName": "TV",
"currentVisibilityState": "SHOWN",
"inputSourceType": "TUNER",
"inputDeviceType": "TV",
"isConfigured": "CONFIGURED",
"identifier": 0,
"targetVisibilityState": "SHOWN",
"name": "TV"
},
{
"type": "InputSource",
"displayName": "HDMI1",
"configuredName": "HDMI1",
"currentVisibilityState": "SHOWN",
"inputSourceType": "HDMI",
"isConfigured": "CONFIGURED",
"identifier": 2,
"targetVisibilityState": "SHOWN",
"name": "HDMI1"
}
],
"polling": [
{
"characteristic": "active",
"interval": 50,
"timeout": 5000
},
{
"characteristic": "activeIdentifier",
"interval": 50,
"timeout": 5000
}
],
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/HisenseTV.sh"
},
{
"type": "TemperatureSensor",
"displayName": "My_TemperatureSensor",
"currentTemperature": 50,
"statusFault": "NO_FAULT",
"name": "Living_Room",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"polling": [
{
"characteristic": "currentTemperature",
"interval": 50,
"timeout": 8000
}
],
"stateChangeResponseTime": 3,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z01"
},
{
"type": "TemperatureSensor",
"displayName": "My_TemperatureSensor",
"currentTemperature": 50,
"statusFault": "NO_FAULT",
"name": "Theatre_Room",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"polling": [
{
"characteristic": "currentTemperature",
"interval": 50,
"timeout": 8000
}
],
"stateChangeResponseTime": 3,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z02"
},
{
"type": "TemperatureSensor",
"displayName": "My_TemperatureSensor",
"currentTemperature": 50,
"statusFault": "NO_FAULT",
"name": "Master_Room",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"polling": [
{
"characteristic": "currentTemperature",
"interval": 50,
"timeout": 8000
}
],
"stateChangeResponseTime": 3,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z03"
},
{
"type": "TemperatureSensor",
"displayName": "My_TemperatureSensor",
"currentTemperature": 50,
"statusFault": "NO_FAULT",
"name": "Craft_Room",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"polling": [
{
"characteristic": "currentTemperature",
"interval": 50,
"timeout": 8000
}
],
"stateChangeResponseTime": 3,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z04"
},
{
"type": "TemperatureSensor",
"displayName": "My_TemperatureSensor",
"currentTemperature": 50,
"statusFault": "NO_FAULT",
"name": "Spare_Room",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"polling": [
{
"characteristic": "currentTemperature",
"interval": 50,
"timeout": 8000
}
],
"stateChangeResponseTime": 3,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z05"
},
{
"type": "TemperatureSensor",
"displayName": "My_TemperatureSensor",
"currentTemperature": 50,
"statusFault": "NO_FAULT",
"name": "Guest_Room",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"polling": [
{
"characteristic": "currentTemperature",
"interval": 50,
"timeout": 8000
}
],
"stateChangeResponseTime": 3,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z06"
},
{
"type": "Switch",
"displayName": "My_Switch",
"on": "FALSE",
"name": "Theatre",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z02"
},
{
"type": "Switch",
"displayName": "My_Switch",
"on": "FALSE",
"name": "Bedroom",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z03"
},
{
"type": "Switch",
"displayName": "My_Switch",
"on": "FALSE",
"name": "Craft",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z04"
},
{
"type": "Switch",
"displayName": "My_Switch",
"on": "FALSE",
"name": "Spare",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z05"
},
{
"type": "Switch",
"displayName": "My_Switch",
"on": "FALSE",
"name": "Guest",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/zones.sh",
"state_cmd_suffix": "z06"
},
{
"type": "Fan",
"on": "FALSE",
"name": "Fan",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/ezone.sh"
},
{
"type": "Thermostat",
"displayName": "My_Thermostat",
"currentHeatingCoolingState": "OFF",
"targetHeatingCoolingState": "OFF",
"currentTemperature": 50,
"targetTemperature": 37,
"temperatureDisplayUnits": "CELCIUS",
"name": "My_Thermostat",
"Manufacturer": "Advantage Air Australia",
"Model": "e-zone",
"SerialNumber": "Fujitsu e-zone2",
"polling": [
{
"characteristic": "currentHeatingCoolingState",
"interval": 60,
"timeout": 8000
},
{
"characteristic": "currentTemperature",
"interval": 60,
"timeout": 8000
},
{
"characteristic": "targetTemperature",
"interval": 60,
"timeout": 8000
}
],
"stateChangeResponseTime": 1,
"state_cmd": "bash /home/pi/ezone.sh"
}
]
},
All of my switches in this config and the fan are the only ones affected.
My shell scripts are linked in above comments except for the first switch
referencing HisenseSwitch.sh (let's ignore that one now so you aren't
looking at too many shell scripts). Please let me know if you need anything
else!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761721178,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX6DYVNCIDC5IQONFFDS2JGPTANCNFSM4WAQJ7YQ
.

Oh and as a warning if/when you have rolled out the config.schema.json; using the config.schema.json will wipe your current manually made config for the accessory when you update and save the config.schema.json. You might want to put a warning label on that seen as people might have more complicated configs on this plug-in.

Oh and as a warning if/when you have rolled out the config.schema.json; using the config.schema.json will wipe your current manually made config for the accessory when you update and save the config.schema.json. You might want to put a warning label on that seen as people might have more complicated configs on this plug-in.

Hi,
I think config UI-x has a backup policy now.
Night
On Sat, Jan 16, 2021 at 9:57 PM Mitch Williams<EMAIL_ADDRESS>wrote:

Oh and as a warning if/when you have rolled out the config.schema.json;
using the config.schema.json will wipe your current manually made config
for the accessory when you update and save the config.schema.json. You
might want to put a warning label on that seen as people might have more
complicated configs on this plug-in.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761721635,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX4BEGVNVX6WBKEREJDS2JG2DANCNFSM4WAQJ7YQ
.

Hi,
I think config UI-x has a backup policy now.
Night
On Sat, Jan 16, 2021 at 9:57 PM Mitch Williams<EMAIL_ADDRESS>wrote:

Oh and as a warning if/when you have rolled out the config.schema.json;
using the config.schema.json will wipe your current manually made config
for the accessory when you update and save the config.schema.json. You
might want to put a warning label on that seen as people might have more
complicated configs on this plug-in.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761721635,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX4BEGVNVX6WBKEREJDS2JG2DANCNFSM4WAQJ7YQ
.

Hmmmm, I think your right or my mind has lost it.
For Switch characteristic On
echo false > Status_My_Switch_On     -> light went  off
echo FALSE > Status_My_Switch_On     -> light went off
echo 1 > Status_My_Switch_On      -> light went off
echo true > Status_My_Switch_On  -> light went on
echo 0 > Status_My_Switch_On        -> light went on
echo 0 > Status_My_Switch_On            -> light went on
echo TrUe > Status_My_Switch_On      -. Light went on
I'll fix it shortly,
Night
On Sat, Jan 16, 2021 at 9:58 PM John Talbot<EMAIL_ADDRESS>wrote:

Hi,
I think config UI-x has a backup policy now.
Night
On Sat, Jan 16, 2021 at 9:57 PM Mitch Williams<EMAIL_ADDRESS>wrote:

Oh and as a warning if/when you have rolled out the config.schema.json;
using the config.schema.json will wipe your current manually made config
for the accessory when you update and save the config.schema.json. You
might want to put a warning label on that seen as people might have more
complicated configs on this plug-in.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761721635,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX4BEGVNVX6WBKEREJDS2JG2DANCNFSM4WAQJ7YQ
.

Hmmmm, I think your right or my mind has lost it.
For Switch characteristic On
echo false > Status_My_Switch_On     -> light went  off
echo FALSE > Status_My_Switch_On     -> light went off
echo 1 > Status_My_Switch_On      -> light went off
echo true > Status_My_Switch_On  -> light went on
echo 0 > Status_My_Switch_On        -> light went on
echo 0 > Status_My_Switch_On            -> light went on
echo TrUe > Status_My_Switch_On      -. Light went on
I'll fix it shortly,
Night
On Sat, Jan 16, 2021 at 9:58 PM John Talbot<EMAIL_ADDRESS>wrote:

Hi,
I think config UI-x has a backup policy now.
Night
On Sat, Jan 16, 2021 at 9:57 PM Mitch Williams<EMAIL_ADDRESS>wrote:

Oh and as a warning if/when you have rolled out the config.schema.json;
using the config.schema.json will wipe your current manually made config
for the accessory when you update and save the config.schema.json. You
might want to put a warning label on that seen as people might have more
complicated configs on this plug-in.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761721635,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX4BEGVNVX6WBKEREJDS2JG2DANCNFSM4WAQJ7YQ
.

Hopefully we both haven’t lost it lol sounds like you’re onto something!

Hopefully we both haven’t lost it lol sounds like you’re onto something!

Hi Mitch,
I'm up for a minute.  Just trying to figure out why there is no test case
that should have found this. I did find the bug though.
 I seem to see it like that. Some
times it clear and then it's not.
I will have an update in the morning.
John
On Sun, Jan 17, 2021 at 3:07 AM Mitch Williams<EMAIL_ADDRESS>wrote:

Hopefully we both haven’t lost it lol sounds like you’re onto something!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761751942,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX5QLFXPJPNZLT7LFCLS2KLE7ANCNFSM4WAQJ7YQ
.

Hi Mitch,
I'm up for a minute.  Just trying to figure out why there is no test case
that should have found this. I did find the bug though.
 I seem to see it like that. Some
times it clear and then it's not.
I will have an update in the morning.
John
On Sun, Jan 17, 2021 at 3:07 AM Mitch Williams<EMAIL_ADDRESS>wrote:

Hopefully we both haven’t lost it lol sounds like you’re onto something!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761751942,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX5QLFXPJPNZLT7LFCLS2KLE7ANCNFSM4WAQJ7YQ
.

It may have been one of the functions that were brought out into separate
utilities that could then be unit tested.  There were unit tests, but I
chose the characteristic "Mute" as the test case and the inside out box
shifted again to outside in.
Update still to come in the morning.
John
On Sun, Jan 17, 2021 at 3:17 AM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,
I'm up for a minute.  Just trying to figure out why there is no test case
that should have found this. I did find the bug though.
 I seem to see it like that. Some
times it clear and then it's not.
I will have an update in the morning.
John
On Sun, Jan 17, 2021 at 3:07 AM Mitch Williams<EMAIL_ADDRESS>wrote:

Hopefully we both haven’t lost it lol sounds like you’re onto something!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761751942,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX5QLFXPJPNZLT7LFCLS2KLE7ANCNFSM4WAQJ7YQ
.

It may have been one of the functions that were brought out into separate
utilities that could then be unit tested.  There were unit tests, but I
chose the characteristic "Mute" as the test case and the inside out box
shifted again to outside in.
Update still to come in the morning.
John
On Sun, Jan 17, 2021 at 3:17 AM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,
I'm up for a minute.  Just trying to figure out why there is no test case
that should have found this. I did find the bug though.
 I seem to see it like that. Some
times it clear and then it's not.
I will have an update in the morning.
John
On Sun, Jan 17, 2021 at 3:07 AM Mitch Williams<EMAIL_ADDRESS>wrote:

Hopefully we both haven’t lost it lol sounds like you’re onto something!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761751942,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX5QLFXPJPNZLT7LFCLS2KLE7ANCNFSM4WAQJ7YQ
.

Hey Mitch,
Just published 3.0.7 to fix the switch issue.  This was baaaaad, probably
caused by my situation.  No excuse really for this one.
John
On Sun, Jan 17, 2021 at 3:44 AM John Talbot<EMAIL_ADDRESS>wrote:

It may have been one of the functions that were brought out into separate
utilities that could then be unit tested.  There were unit tests, but I
chose the characteristic "Mute" as the test case and the inside out box
shifted again to outside in.
Update still to come in the morning.
John
On Sun, Jan 17, 2021 at 3:17 AM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,
I'm up for a minute.  Just trying to figure out why there is no test case
that should have found this. I did find the bug though.
 I seem to see it like that. Some
times it clear and then it's not.
I will have an update in the morning.
John
On Sun, Jan 17, 2021 at 3:07 AM Mitch Williams<EMAIL_ADDRESS>wrote:

Hopefully we both haven’t lost it lol sounds like you’re onto something!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761751942,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX5QLFXPJPNZLT7LFCLS2KLE7ANCNFSM4WAQJ7YQ
.

Hey Mitch,
Just published 3.0.7 to fix the switch issue.  This was baaaaad, probably
caused by my situation.  No excuse really for this one.
John
On Sun, Jan 17, 2021 at 3:44 AM John Talbot<EMAIL_ADDRESS>wrote:

It may have been one of the functions that were brought out into separate
utilities that could then be unit tested.  There were unit tests, but I
chose the characteristic "Mute" as the test case and the inside out box
shifted again to outside in.
Update still to come in the morning.
John
On Sun, Jan 17, 2021 at 3:17 AM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,
I'm up for a minute.  Just trying to figure out why there is no test case
that should have found this. I did find the bug though.
 I seem to see it like that. Some
times it clear and then it's not.
I will have an update in the morning.
John
On Sun, Jan 17, 2021 at 3:07 AM Mitch Williams<EMAIL_ADDRESS>wrote:

Hopefully we both haven’t lost it lol sounds like you’re onto something!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761751942,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX5QLFXPJPNZLT7LFCLS2KLE7ANCNFSM4WAQJ7YQ
.

 I seem to see it like that. Some
times it clear and then it's not.

I do feel that John haha just about every brine I try to learn more about this stuff!
 Don’t beat yourself up over it, everyone makes mistakes; and this was only a very minor one. Thanks again!

 I seem to see it like that. Some
times it clear and then it's not.

I do feel that John haha just about every brine I try to learn more about this stuff!
 Don’t beat yourself up over it, everyone makes mistakes; and this was only a very minor one. Thanks again!

hey Mitch,
I actually found one other bug.I removed fetch from one of the
accessories and the recent change to undo the Cmd4 directives kicked me
saying that it did not know how to handle a fetch of undefined, it must be
Always, Cached or Polled.  It is an easy fix, but still.
On the fun side of things, last week my new Mac Mini M1 came in.  It has
16Gb Ram and a 1TB SSD. It uncovered a bug in one of my testing scripts.
Everything there is asynchronous programming and things were now happening
faster and out of order causing issues.
I justified the purchase to my wife by saying I would be ticked if I woke
up dead and did not have one.  No need struggling with a very old computer.
Life is funny. In your thirties you find out that when you get an injury it
does not heal over night. In your forties, you accept that anything you do
will hurt. Now in my upper fifties, I can forget what I went upstairs to
get once I got there.
 I seem to see it like that. Some
times it clear and then it's not.
I do feel that John haha just about every brine I try to learn more about
this stuff!
 Don’t beat yourself up over it, everyone makes mistakes; and
this was only a very minor one. Thanks again!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761819487,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX5FOFUBYKH35AO6IG3S2LWLZANCNFSM4WAQJ7YQ
.

hey Mitch,
I actually found one other bug.I removed fetch from one of the
accessories and the recent change to undo the Cmd4 directives kicked me
saying that it did not know how to handle a fetch of undefined, it must be
Always, Cached or Polled.  It is an easy fix, but still.
On the fun side of things, last week my new Mac Mini M1 came in.  It has
16Gb Ram and a 1TB SSD. It uncovered a bug in one of my testing scripts.
Everything there is asynchronous programming and things were now happening
faster and out of order causing issues.
I justified the purchase to my wife by saying I would be ticked if I woke
up dead and did not have one.  No need struggling with a very old computer.
Life is funny. In your thirties you find out that when you get an injury it
does not heal over night. In your forties, you accept that anything you do
will hurt. Now in my upper fifties, I can forget what I went upstairs to
get once I got there.
 I seem to see it like that. Some
times it clear and then it's not.
I do feel that John haha just about every brine I try to learn more about
this stuff!
 Don’t beat yourself up over it, everyone makes mistakes; and
this was only a very minor one. Thanks again!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-761819487,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX5FOFUBYKH35AO6IG3S2LWLZANCNFSM4WAQJ7YQ
.

On the fun side of things, last week my new Mac Mini M1 came in.  It has
16Gb Ram and a 1TB SSD. It uncovered a bug in one of my testing scripts.
Everything there is asynchronous programming and things were now happening
faster and out of order causing issues.

I justified the purchase to my wife by saying I would be ticked if I woke
up dead and did not have one.  No need struggling with a very old computer.

Now that is exciting and also sounds like it is already paying off. I like how you justified it hahaha.

Life is funny. In your thirties you find out that when you get an injury it
does not heal over night. In your forties, you accept that anything you do
will hurt. Now in my upper fifties, I can forget what I went upstairs to
get once I got there.

Sounds like I am already in my 50's at the age of 30 hahaha.

On the fun side of things, last week my new Mac Mini M1 came in.  It has
16Gb Ram and a 1TB SSD. It uncovered a bug in one of my testing scripts.
Everything there is asynchronous programming and things were now happening
faster and out of order causing issues.

I justified the purchase to my wife by saying I would be ticked if I woke
up dead and did not have one.  No need struggling with a very old computer.

Now that is exciting and also sounds like it is already paying off. I like how you justified it hahaha.

Life is funny. In your thirties you find out that when you get an injury it
does not heal over night. In your forties, you accept that anything you do
will hurt. Now in my upper fifties, I can forget what I went upstairs to
get once I got there.

Sounds like I am already in my 50's at the age of 30 hahaha.

Hmm there actually still seems to be an issue John; I may have celebrated too early. Considering it was the day before I went back to work I had not tested as well as I should have. I looked at whether feedback was correct and left it at that, but I never tested controlling devices. Over the last few evenings I have asked Siri to set my air con to cool and it didn't work; after the third evening that I used the proper app and not Homekit, I finally got a bit suss.
I would set the thermostat (my air con) to cool from Homekit and it would not turn on or reflect in the manufacturer's app; when I would flick to Homekit again it would be set to off. I tried setting the thermostat to cool from config-ui-x and it would instantly change state back to off every time I set it to cool. I tried all the switches in these shell scripts and same thing.
Reverting back to cmd4 v2.42 and reverting to my config.json I had for that version fixes everything and it is all controllable again. It would still seem something between these versions is still breaking my cmd4 accessories... I will try and do some better digging on my day off tomorrow, to give you something more substantial to work with.

Hmm there actually still seems to be an issue John; I may have celebrated too early. Considering it was the day before I went back to work I had not tested as well as I should have. I looked at whether feedback was correct and left it at that, but I never tested controlling devices. Over the last few evenings I have asked Siri to set my air con to cool and it didn't work; after the third evening that I used the proper app and not Homekit, I finally got a bit suss.
I would set the thermostat (my air con) to cool from Homekit and it would not turn on or reflect in the manufacturer's app; when I would flick to Homekit again it would be set to off. I tried setting the thermostat to cool from config-ui-x and it would instantly change state back to off every time I set it to cool. I tried all the switches in these shell scripts and same thing.
Reverting back to cmd4 v2.42 and reverting to my config.json I had for that version fixes everything and it is all controllable again. It would still seem something between these versions is still breaking my cmd4 accessories... I will try and do some better digging on my day off tomorrow, to give you something more substantial to work with.

Hi Mitch.
I can poke too,
TTFN,
John
On Thu, Jan 21, 2021 at 8:17 AM Mitch Williams<EMAIL_ADDRESS>wrote:

Hmm there actually still seems to be an issue John; I may have celebrated
too early. Considering it was the day before I went back to work I had not
tested as well as I should have. I looked at whether feedback was correct
and left it at that, but I never tested controlling devices. Over the last
few evenings I have asked Siri to set my air con to cool and it didn't
work; after the third evening that I used the proper app and not Homekit, I
finally got a bit suss.
I would set the thermostat (my air con) to cool from Homekit and it would
not turn on or reflect in the manufacturer's app; when I would flick to
Homekit again it would be set to off. I tried setting the thermostat to
cool from config-ui-x and it would instantly change state back to off every
time I set it to cool. I tried all the switches in these shell scripts and
same thing.
Reverting back to cmd4 v2.42 and reverting to my config.json I had for
that version fixes everything and it is all controllable again. It would
still seem something between these versions is still breaking my cmd4
accessories... I will try and do some better digging on my day off
tomorrow, to give you something more substantial to work with.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-764636265,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCXY5WWTQ4BUMTILPGGLS3ASPDANCNFSM4WAQJ7YQ
.

Hi Mitch.
I can poke too,
TTFN,
John
On Thu, Jan 21, 2021 at 8:17 AM Mitch Williams<EMAIL_ADDRESS>wrote:

Hmm there actually still seems to be an issue John; I may have celebrated
too early. Considering it was the day before I went back to work I had not
tested as well as I should have. I looked at whether feedback was correct
and left it at that, but I never tested controlling devices. Over the last
few evenings I have asked Siri to set my air con to cool and it didn't
work; after the third evening that I used the proper app and not Homekit, I
finally got a bit suss.
I would set the thermostat (my air con) to cool from Homekit and it would
not turn on or reflect in the manufacturer's app; when I would flick to
Homekit again it would be set to off. I tried setting the thermostat to
cool from config-ui-x and it would instantly change state back to off every
time I set it to cool. I tried all the switches in these shell scripts and
same thing.
Reverting back to cmd4 v2.42 and reverting to my config.json I had for
that version fixes everything and it is all controllable again. It would
still seem something between these versions is still breaking my cmd4
accessories... I will try and do some better digging on my day off
tomorrow, to give you something more substantial to work with.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-764636265,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCXY5WWTQ4BUMTILPGGLS3ASPDANCNFSM4WAQJ7YQ
.

Hi Mitch,
I just started to look at this now.  I don't have Siri, But what I noticed
from the GUI was a little different than I remembered.  You used to be able
to torn the thermostat on just by selecting it.  It seems if it is off,
that is not true.  You would have to then set it to Heat/Cool or Auto, then
you can turn it on.
Otherwise, so far so good.  Please don't waste your day off.  Let me dig
some more.
I'm concerned that if the target temperature is not polled and fetch is not
"Always", then the cached version would be returned.  I'm totally not sure
here and have to retest to completely verify that statement.  I'm just
thinking of possibilities. Things that should not happen.
I have just been working from my tablet lately. This can be limiting. I was
only able to check in some automated documentation, but I got my shot today
$1800/14 days! Thank god for health insurance.  Anyway, I should be up for
more tomorrow.
TTFN,
John
On Thu, Jan 21, 2021 at 8:54 AM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch.
I can poke too,
TTFN,
John
On Thu, Jan 21, 2021 at 8:17 AM Mitch Williams<EMAIL_ADDRESS>wrote:

Hmm there actually still seems to be an issue John; I may have celebrated
too early. Considering it was the day before I went back to work I had not
tested as well as I should have. I looked at whether feedback was correct
and left it at that, but I never tested controlling devices. Over the last
few evenings I have asked Siri to set my air con to cool and it didn't
work; after the third evening that I used the proper app and not Homekit, I
finally got a bit suss.
I would set the thermostat (my air con) to cool from Homekit and it would
not turn on or reflect in the manufacturer's app; when I would flick to
Homekit again it would be set to off. I tried setting the thermostat to
cool from config-ui-x and it would instantly change state back to off every
time I set it to cool. I tried all the switches in these shell scripts and
same thing.
Reverting back to cmd4 v2.42 and reverting to my config.json I had for
that version fixes everything and it is all controllable again. It would
still seem something between these versions is still breaking my cmd4
accessories... I will try and do some better digging on my day off
tomorrow, to give you something more substantial to work with.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-764636265,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCXY5WWTQ4BUMTILPGGLS3ASPDANCNFSM4WAQJ7YQ
.

Hi Mitch,
I just started to look at this now.  I don't have Siri, But what I noticed
from the GUI was a little different than I remembered.  You used to be able
to torn the thermostat on just by selecting it.  It seems if it is off,
that is not true.  You would have to then set it to Heat/Cool or Auto, then
you can turn it on.
Otherwise, so far so good.  Please don't waste your day off.  Let me dig
some more.
I'm concerned that if the target temperature is not polled and fetch is not
"Always", then the cached version would be returned.  I'm totally not sure
here and have to retest to completely verify that statement.  I'm just
thinking of possibilities. Things that should not happen.
I have just been working from my tablet lately. This can be limiting. I was
only able to check in some automated documentation, but I got my shot today
$1800/14 days! Thank god for health insurance.  Anyway, I should be up for
more tomorrow.
TTFN,
John
On Thu, Jan 21, 2021 at 8:54 AM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch.
I can poke too,
TTFN,
John
On Thu, Jan 21, 2021 at 8:17 AM Mitch Williams<EMAIL_ADDRESS>wrote:

Hmm there actually still seems to be an issue John; I may have celebrated
too early. Considering it was the day before I went back to work I had not
tested as well as I should have. I looked at whether feedback was correct
and left it at that, but I never tested controlling devices. Over the last
few evenings I have asked Siri to set my air con to cool and it didn't
work; after the third evening that I used the proper app and not Homekit, I
finally got a bit suss.
I would set the thermostat (my air con) to cool from Homekit and it would
not turn on or reflect in the manufacturer's app; when I would flick to
Homekit again it would be set to off. I tried setting the thermostat to
cool from config-ui-x and it would instantly change state back to off every
time I set it to cool. I tried all the switches in these shell scripts and
same thing.
Reverting back to cmd4 v2.42 and reverting to my config.json I had for
that version fixes everything and it is all controllable again. It would
still seem something between these versions is still breaking my cmd4
accessories... I will try and do some better digging on my day off
tomorrow, to give you something more substantial to work with.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-764636265,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCXY5WWTQ4BUMTILPGGLS3ASPDANCNFSM4WAQJ7YQ
.

Hi Mitch,
That statement should have referred to fetch:Polled, as set to Cached,
everything returned cached.  The test is correct though.  If "fetch":
"Polled" is set then if you poll for currentTemperature, but not
TargetTemperature, then the cached value of ragerTemperature is returned.
Not a problem if you understand restartRecover and how it works.
Still no issue found though, except for the different GUI behavior I noted
below.
ttfn,
John
On Thu, Jan 21, 2021 at 8:26 PM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,
I just started to look at this now.  I don't have Siri, But what I noticed
from the GUI was a little different than I remembered.  You used to be able
to torn the thermostat on just by selecting it.  It seems if it is off,
that is not true.  You would have to then set it to Heat/Cool or Auto, then
you can turn it on.
Otherwise, so far so good.  Please don't waste your day off.  Let me dig
some more.
I'm concerned that if the target temperature is not polled and fetch is
not "Always", then the cached version would be returned.  I'm totally not
sure here and have to retest to completely verify that statement.  I'm just
thinking of possibilities. Things that should not happen.
I have just been working from my tablet lately. This can be limiting. I
was only able to check in some automated documentation, but I got my shot
today $1800/14 days! Thank god for health insurance.  Anyway, I should be
up for more tomorrow.
TTFN,
John
On Thu, Jan 21, 2021 at 8:54 AM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch.
I can poke too,
TTFN,
John
On Thu, Jan 21, 2021 at 8:17 AM Mitch Williams<EMAIL_ADDRESS>wrote:

Hmm there actually still seems to be an issue John; I may have
celebrated too early. Considering it was the day before I went back to work
I had not tested as well as I should have. I looked at whether feedback was
correct and left it at that, but I never tested controlling devices. Over
the last few evenings I have asked Siri to set my air con to cool and it
didn't work; after the third evening that I used the proper app and not
Homekit, I finally got a bit suss.
I would set the thermostat (my air con) to cool from Homekit and it
would not turn on or reflect in the manufacturer's app; when I would flick
to Homekit again it would be set to off. I tried setting the thermostat to
cool from config-ui-x and it would instantly change state back to off every
time I set it to cool. I tried all the switches in these shell scripts and
same thing.
Reverting back to cmd4 v2.42 and reverting to my config.json I had for
that version fixes everything and it is all controllable again. It would
still seem something between these versions is still breaking my cmd4
accessories... I will try and do some better digging on my day off
tomorrow, to give you something more substantial to work with.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-764636265,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCXY5WWTQ4BUMTILPGGLS3ASPDANCNFSM4WAQJ7YQ
.

Hi Mitch,
That statement should have referred to fetch:Polled, as set to Cached,
everything returned cached.  The test is correct though.  If "fetch":
"Polled" is set then if you poll for currentTemperature, but not
TargetTemperature, then the cached value of ragerTemperature is returned.
Not a problem if you understand restartRecover and how it works.
Still no issue found though, except for the different GUI behavior I noted
below.
ttfn,
John
On Thu, Jan 21, 2021 at 8:26 PM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,
I just started to look at this now.  I don't have Siri, But what I noticed
from the GUI was a little different than I remembered.  You used to be able
to torn the thermostat on just by selecting it.  It seems if it is off,
that is not true.  You would have to then set it to Heat/Cool or Auto, then
you can turn it on.
Otherwise, so far so good.  Please don't waste your day off.  Let me dig
some more.
I'm concerned that if the target temperature is not polled and fetch is
not "Always", then the cached version would be returned.  I'm totally not
sure here and have to retest to completely verify that statement.  I'm just
thinking of possibilities. Things that should not happen.
I have just been working from my tablet lately. This can be limiting. I
was only able to check in some automated documentation, but I got my shot
today $1800/14 days! Thank god for health insurance.  Anyway, I should be
up for more tomorrow.
TTFN,
John
On Thu, Jan 21, 2021 at 8:54 AM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch.
I can poke too,
TTFN,
John
On Thu, Jan 21, 2021 at 8:17 AM Mitch Williams<EMAIL_ADDRESS>wrote:

Hmm there actually still seems to be an issue John; I may have
celebrated too early. Considering it was the day before I went back to work
I had not tested as well as I should have. I looked at whether feedback was
correct and left it at that, but I never tested controlling devices. Over
the last few evenings I have asked Siri to set my air con to cool and it
didn't work; after the third evening that I used the proper app and not
Homekit, I finally got a bit suss.
I would set the thermostat (my air con) to cool from Homekit and it
would not turn on or reflect in the manufacturer's app; when I would flick
to Homekit again it would be set to off. I tried setting the thermostat to
cool from config-ui-x and it would instantly change state back to off every
time I set it to cool. I tried all the switches in these shell scripts and
same thing.
Reverting back to cmd4 v2.42 and reverting to my config.json I had for
that version fixes everything and it is all controllable again. It would
still seem something between these versions is still breaking my cmd4
accessories... I will try and do some better digging on my day off
tomorrow, to give you something more substantial to work with.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-764636265,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCXY5WWTQ4BUMTILPGGLS3ASPDANCNFSM4WAQJ7YQ
.

Sorry I may have mislead you in a few ways with how I worded all that! By ‘turn on’ I do mean ‘set to cool’ which does end up turning it on at the same time. The GUI definitely doesn’t look different to me :)
I also don’t think Siri is of relevance, I was creating the story by explaining how I first noticed haha it also does not work from the HomeKit tile in the app or through the accessory created on config-ui-x; so overall through I cannot issues ‘set’ commands it would seem.
I enjoy working on this stuff and my wife is on night shifts so I can’t do anything too loud in the house today haha
Do I need to be setting anything in my config.json for this ”fetch”: property?
Glad to hear about your health insurance, every time I hear a story about Americans and healthy insurance; I am so glad I am an Australian!

Sorry I may have mislead you in a few ways with how I worded all that! By ‘turn on’ I do mean ‘set to cool’ which does end up turning it on at the same time. The GUI definitely doesn’t look different to me :)
I also don’t think Siri is of relevance, I was creating the story by explaining how I first noticed haha it also does not work from the HomeKit tile in the app or through the accessory created on config-ui-x; so overall through I cannot issues ‘set’ commands it would seem.
I enjoy working on this stuff and my wife is on night shifts so I can’t do anything too loud in the house today haha
Do I need to be setting anything in my config.json for this ”fetch”: property?
Glad to hear about your health insurance, every time I hear a story about Americans and healthy insurance; I am so glad I am an Australian!

Also I had a user submitted an issue on my repo and they were having trouble getting it all installed. I was off to bed last night so as one thing I mentioned was how cmd4 v2.4.0 seems to be working better for me at this stage and they reported that reverting to back to that actually got them started. Not sure if it was due to using the old config.json on my repo with v3.0.7 or if their errors present something more to help you piece together the puzzle over here.
https://github.com/mitch7391/cmd4-E-Zone-MyAir/issues/5#issuecomment-764766573

Also I had a user submitted an issue on my repo and they were having trouble getting it all installed. I was off to bed last night so as one thing I mentioned was how cmd4 v2.4.0 seems to be working better for me at this stage and they reported that reverting to back to that actually got them started. Not sure if it was due to using the old config.json on my repo with v3.0.7 or if their errors present something more to help you piece together the puzzle over here.
https://github.com/mitch7391/cmd4-E-Zone-MyAir/issues/5#issuecomment-764766573

Hi Mitch,
By default, fetch is "Always" and I don't have it in my config.json that I
was testing with.
I just published 3.0.8.  I wanted to make sure we are working on the same
base, even though 3.0.8 should not affect what we are doing.  There were
two issues with translating constants, but I don't have outputConstants in
my config.json, so the default is false.
I'll poke some more tomorrow.
TTFN,
John
On Thu, Jan 21, 2021 at 9:59 PM Mitch Williams<EMAIL_ADDRESS>wrote:

Also I had a user submitted an issue on my repo and they were having
trouble getting it all installed. I was off to bed last night so as one
thing I mentioned was how cmd4 v2.4.0 seems to be working better for me
at this stage and they reported that reverting to back to that actually got
them started. Not sure if it was due to using the old config.json on my
repo with v3.0.7 or if their errors present something more to help you
piece together the puzzle over here.
mitch7391/cmd4-E-Zone-MyAir#5 (comment)
https://github.com/mitch7391/cmd4-E-Zone-MyAir/issues/5#issuecomment-764766573
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-765086609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX7LX75CKRI65UIJ3XDS3DSXZANCNFSM4WAQJ7YQ
.

Hi Mitch,
By default, fetch is "Always" and I don't have it in my config.json that I
was testing with.
I just published 3.0.8.  I wanted to make sure we are working on the same
base, even though 3.0.8 should not affect what we are doing.  There were
two issues with translating constants, but I don't have outputConstants in
my config.json, so the default is false.
I'll poke some more tomorrow.
TTFN,
John
On Thu, Jan 21, 2021 at 9:59 PM Mitch Williams<EMAIL_ADDRESS>wrote:

Also I had a user submitted an issue on my repo and they were having
trouble getting it all installed. I was off to bed last night so as one
thing I mentioned was how cmd4 v2.4.0 seems to be working better for me
at this stage and they reported that reverting to back to that actually got
them started. Not sure if it was due to using the old config.json on my
repo with v3.0.7 or if their errors present something more to help you
piece together the puzzle over here.
mitch7391/cmd4-E-Zone-MyAir#5 (comment)
https://github.com/mitch7391/cmd4-E-Zone-MyAir/issues/5#issuecomment-764766573
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-765086609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX7LX75CKRI65UIJ3XDS3DSXZANCNFSM4WAQJ7YQ
.

No worries, would you like me to test out v3.0.8 and see that I have the same issue still? Do you need me to collect any logs?
I spent a fair bit of time today tidying up my own repo; so I have put a known bug on the README for any users of my shell scripts to stay on v2.4.2 for the time being until we have this one sorted. Although I have noticed that no one has raised an issue on my repo or yours for this yet; which is a good sign haha.

No worries, would you like me to test out v3.0.8 and see that I have the same issue still? Do you need me to collect any logs?
I spent a fair bit of time today tidying up my own repo; so I have put a known bug on the README for any users of my shell scripts to stay on v2.4.2 for the time being until we have this one sorted. Although I have noticed that no one has raised an issue on my repo or yours for this yet; which is a good sign haha.

If you could, just delete the cache, install 3.0.8 and see if it occurs
again.  I'll be trying again later.  Just got my morning meds and going
back to bed.
Ttyl,
John
On Fri, Jan 22, 2021 at 6:13 AM Mitch Williams<EMAIL_ADDRESS>wrote:

No worries, would you like me to test out v3.0.8 and see that I have the
same issue still? Do you need me to collect any logs?
I spent a fair bit of time today tidying up my own repo; so I have put a
known bug on the README for any users of my shell scripts to stay on
v2.4.2 for the time being until we have this one sorted. Although I have
noticed that no one has raised an issue on my repo or yours for this yet;
which is a good sign haha.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-765330211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3MXPQQECLZRQFATWDS3FMWXANCNFSM4WAQJ7YQ
.

If you could, just delete the cache, install 3.0.8 and see if it occurs
again.  I'll be trying again later.  Just got my morning meds and going
back to bed.
Ttyl,
John
On Fri, Jan 22, 2021 at 6:13 AM Mitch Williams<EMAIL_ADDRESS>wrote:

No worries, would you like me to test out v3.0.8 and see that I have the
same issue still? Do you need me to collect any logs?
I spent a fair bit of time today tidying up my own repo; so I have put a
known bug on the README for any users of my shell scripts to stay on
v2.4.2 for the time being until we have this one sorted. Although I have
noticed that no one has raised an issue on my repo or yours for this yet;
which is a good sign haha.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-765330211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3MXPQQECLZRQFATWDS3FMWXANCNFSM4WAQJ7YQ
.

Hi Mitch,
I have a few more minutes to dig.  I just looked at your config.json.
I'm impressed. !!
ttfn,
John
On Fri, Jan 22, 2021 at 8:18 AM John Talbot<EMAIL_ADDRESS>wrote:

If you could, just delete the cache, install 3.0.8 and see if it occurs
again.  I'll be trying again later.  Just got my morning meds and going
back to bed.
Ttyl,
John
On Fri, Jan 22, 2021 at 6:13 AM Mitch Williams<EMAIL_ADDRESS>wrote:

No worries, would you like me to test out v3.0.8 and see that I have the
same issue still? Do you need me to collect any logs?
I spent a fair bit of time today tidying up my own repo; so I have put a
known bug on the README for any users of my shell scripts to stay on
v2.4.2 for the time being until we have this one sorted. Although I have
noticed that no one has raised an issue on my repo or yours for this yet;
which is a good sign haha.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-765330211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3MXPQQECLZRQFATWDS3FMWXANCNFSM4WAQJ7YQ
.

Hi Mitch,
I have a few more minutes to dig.  I just looked at your config.json.
I'm impressed. !!
ttfn,
John
On Fri, Jan 22, 2021 at 8:18 AM John Talbot<EMAIL_ADDRESS>wrote:

If you could, just delete the cache, install 3.0.8 and see if it occurs
again.  I'll be trying again later.  Just got my morning meds and going
back to bed.
Ttyl,
John
On Fri, Jan 22, 2021 at 6:13 AM Mitch Williams<EMAIL_ADDRESS>wrote:

No worries, would you like me to test out v3.0.8 and see that I have the
same issue still? Do you need me to collect any logs?
I spent a fair bit of time today tidying up my own repo; so I have put a
known bug on the README for any users of my shell scripts to stay on
v2.4.2 for the time being until we have this one sorted. Although I have
noticed that no one has raised an issue on my repo or yours for this yet;
which is a good sign haha.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-765330211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3MXPQQECLZRQFATWDS3FMWXANCNFSM4WAQJ7YQ
.

I just published 3.0.9.
I don't think it will fix your issue.  It was a problem I noticed if
fetch was removed from the config.json, then it complained that it did not
know how to handle a fetch of undefined.  The fix applies to other
designations, but this should still not be your issue.
I'm going to take a break for tonight.
ttfn,
John
On Fri, Jan 22, 2021 at 1:08 PM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,
I have a few more minutes to dig.  I just looked at your config.json.
I'm impressed. !!
ttfn,
John
On Fri, Jan 22, 2021 at 8:18 AM John Talbot<EMAIL_ADDRESS>wrote:

If you could, just delete the cache, install 3.0.8 and see if it occurs
again.  I'll be trying again later.  Just got my morning meds and going
back to bed.
Ttyl,
John
On Fri, Jan 22, 2021 at 6:13 AM Mitch Williams<EMAIL_ADDRESS>wrote:

No worries, would you like me to test out v3.0.8 and see that I have
the same issue still? Do you need me to collect any logs?
I spent a fair bit of time today tidying up my own repo; so I have put a
known bug on the README for any users of my shell scripts to stay on
v2.4.2 for the time being until we have this one sorted. Although I
have noticed that no one has raised an issue on my repo or yours for this
yet; which is a good sign haha.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-765330211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3MXPQQECLZRQFATWDS3FMWXANCNFSM4WAQJ7YQ
.

I just published 3.0.9.
I don't think it will fix your issue.  It was a problem I noticed if
fetch was removed from the config.json, then it complained that it did not
know how to handle a fetch of undefined.  The fix applies to other
designations, but this should still not be your issue.
I'm going to take a break for tonight.
ttfn,
John
On Fri, Jan 22, 2021 at 1:08 PM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,
I have a few more minutes to dig.  I just looked at your config.json.
I'm impressed. !!
ttfn,
John
On Fri, Jan 22, 2021 at 8:18 AM John Talbot<EMAIL_ADDRESS>wrote:

If you could, just delete the cache, install 3.0.8 and see if it occurs
again.  I'll be trying again later.  Just got my morning meds and going
back to bed.
Ttyl,
John
On Fri, Jan 22, 2021 at 6:13 AM Mitch Williams<EMAIL_ADDRESS>wrote:

No worries, would you like me to test out v3.0.8 and see that I have
the same issue still? Do you need me to collect any logs?
I spent a fair bit of time today tidying up my own repo; so I have put a
known bug on the README for any users of my shell scripts to stay on
v2.4.2 for the time being until we have this one sorted. Although I
have noticed that no one has raised an issue on my repo or yours for this
yet; which is a good sign haha.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-765330211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3MXPQQECLZRQFATWDS3FMWXANCNFSM4WAQJ7YQ
.

Hey Mitch,
I might have a thought.  Can you try setting config.name,
config.displayName to be the same in each section of your config.json.
Specifically I noticed My_TemperatureSensor is the same in two different
sections, though config.name is not.
Stated another way, make sure config.name = config.displayName in each
section are the same, but of course the two are different from other
sections.
What I think I see is polling for two different accessories being addressed
by the same displayName.
ttfn,
John
On Fri, Jan 22, 2021 at 4:56 PM John Talbot<EMAIL_ADDRESS>wrote:

I just published 3.0.9.
I don't think it will fix your issue.  It was a problem I noticed if
fetch was removed from the config.json, then it complained that it did not
know how to handle a fetch of undefined.  The fix applies to other
designations, but this should still not be your issue.
I'm going to take a break for tonight.
ttfn,
John
On Fri, Jan 22, 2021 at 1:08 PM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,
I have a few more minutes to dig.  I just looked at your config.json.
I'm impressed. !!
ttfn,
John
On Fri, Jan 22, 2021 at 8:18 AM John Talbot<EMAIL_ADDRESS>wrote:

If you could, just delete the cache, install 3.0.8 and see if it occurs
again.  I'll be trying again later.  Just got my morning meds and going
back to bed.
Ttyl,
John
On Fri, Jan 22, 2021 at 6:13 AM Mitch Williams<EMAIL_ADDRESS>wrote:

No worries, would you like me to test out v3.0.8 and see that I have
the same issue still? Do you need me to collect any logs?
I spent a fair bit of time today tidying up my own repo; so I have put
a known bug on the README for any users of my shell scripts to stay on
v2.4.2 for the time being until we have this one sorted. Although I
have noticed that no one has raised an issue on my repo or yours for this
yet; which is a good sign haha.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-765330211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3MXPQQECLZRQFATWDS3FMWXANCNFSM4WAQJ7YQ
.

Hey Mitch,
I might have a thought.  Can you try setting config.name,
config.displayName to be the same in each section of your config.json.
Specifically I noticed My_TemperatureSensor is the same in two different
sections, though config.name is not.
Stated another way, make sure config.name = config.displayName in each
section are the same, but of course the two are different from other
sections.
What I think I see is polling for two different accessories being addressed
by the same displayName.
ttfn,
John
On Fri, Jan 22, 2021 at 4:56 PM John Talbot<EMAIL_ADDRESS>wrote:

I just published 3.0.9.
I don't think it will fix your issue.  It was a problem I noticed if
fetch was removed from the config.json, then it complained that it did not
know how to handle a fetch of undefined.  The fix applies to other
designations, but this should still not be your issue.
I'm going to take a break for tonight.
ttfn,
John
On Fri, Jan 22, 2021 at 1:08 PM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,
I have a few more minutes to dig.  I just looked at your config.json.
I'm impressed. !!
ttfn,
John
On Fri, Jan 22, 2021 at 8:18 AM John Talbot<EMAIL_ADDRESS>wrote:

If you could, just delete the cache, install 3.0.8 and see if it occurs
again.  I'll be trying again later.  Just got my morning meds and going
back to bed.
Ttyl,
John
On Fri, Jan 22, 2021 at 6:13 AM Mitch Williams<EMAIL_ADDRESS>wrote:

No worries, would you like me to test out v3.0.8 and see that I have
the same issue still? Do you need me to collect any logs?
I spent a fair bit of time today tidying up my own repo; so I have put
a known bug on the README for any users of my shell scripts to stay on
v2.4.2 for the time being until we have this one sorted. Although I
have noticed that no one has raised an issue on my repo or yours for this
yet; which is a good sign haha.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-765330211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3MXPQQECLZRQFATWDS3FMWXANCNFSM4WAQJ7YQ
.

That might be your answer.  The Homebridge API references use displayName.
I don think I changed getCmd to use displayName. I believe it always did.
However displayName might have previously been populated by name first.
Still digging.
I am also not 100% sure the difference between name, displayName and
configuredName.  I thought name is what gets changed when from the GUI you
change a devices name, while Display name never changes.  This all being
counter intuitive.  How configured name plays into it the documentation
does not say and I never use, except for adding it as a object property.
ttfn,
John
On Fri, Jan 22, 2021 at 6:02 PM John Talbot<EMAIL_ADDRESS>wrote:

Hey Mitch,
I might have a thought.  Can you try setting config.name,
config.displayName to be the same in each section of your config.json.
Specifically I noticed My_TemperatureSensor is the same in two different
sections, though config.name is not.
Stated another way, make sure config.name = config.displayName in each
section are the same, but of course the two are different from other
sections.
What I think I see is polling for two different accessories being
addressed by the same displayName.
ttfn,
John
On Fri, Jan 22, 2021 at 4:56 PM John Talbot<EMAIL_ADDRESS>wrote:

I just published 3.0.9.
I don't think it will fix your issue.  It was a problem I noticed if
fetch was removed from the config.json, then it complained that it did not
know how to handle a fetch of undefined.  The fix applies to other
designations, but this should still not be your issue.
I'm going to take a break for tonight.
ttfn,
John
On Fri, Jan 22, 2021 at 1:08 PM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,
I have a few more minutes to dig.  I just looked at your config.json.
I'm impressed. !!
ttfn,
John
On Fri, Jan 22, 2021 at 8:18 AM John Talbot<EMAIL_ADDRESS>wrote:

If you could, just delete the cache, install 3.0.8 and see if it occurs
again.  I'll be trying again later.  Just got my morning meds and going
back to bed.
Ttyl,
John
On Fri, Jan 22, 2021 at 6:13 AM Mitch Williams <
<EMAIL_ADDRESS>wrote:

No worries, would you like me to test out v3.0.8 and see that I have
the same issue still? Do you need me to collect any logs?
I spent a fair bit of time today tidying up my own repo; so I have put
a known bug on the README for any users of my shell scripts to stay on
v2.4.2 for the time being until we have this one sorted. Although I
have noticed that no one has raised an issue on my repo or yours for this
yet; which is a good sign haha.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-765330211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3MXPQQECLZRQFATWDS3FMWXANCNFSM4WAQJ7YQ
.

That might be your answer.  The Homebridge API references use displayName.
I don think I changed getCmd to use displayName. I believe it always did.
However displayName might have previously been populated by name first.
Still digging.
I am also not 100% sure the difference between name, displayName and
configuredName.  I thought name is what gets changed when from the GUI you
change a devices name, while Display name never changes.  This all being
counter intuitive.  How configured name plays into it the documentation
does not say and I never use, except for adding it as a object property.
ttfn,
John
On Fri, Jan 22, 2021 at 6:02 PM John Talbot<EMAIL_ADDRESS>wrote:

Hey Mitch,
I might have a thought.  Can you try setting config.name,
config.displayName to be the same in each section of your config.json.
Specifically I noticed My_TemperatureSensor is the same in two different
sections, though config.name is not.
Stated another way, make sure config.name = config.displayName in each
section are the same, but of course the two are different from other
sections.
What I think I see is polling for two different accessories being
addressed by the same displayName.
ttfn,
John
On Fri, Jan 22, 2021 at 4:56 PM John Talbot<EMAIL_ADDRESS>wrote:

I just published 3.0.9.
I don't think it will fix your issue.  It was a problem I noticed if
fetch was removed from the config.json, then it complained that it did not
know how to handle a fetch of undefined.  The fix applies to other
designations, but this should still not be your issue.
I'm going to take a break for tonight.
ttfn,
John
On Fri, Jan 22, 2021 at 1:08 PM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,
I have a few more minutes to dig.  I just looked at your config.json.
I'm impressed. !!
ttfn,
John
On Fri, Jan 22, 2021 at 8:18 AM John Talbot<EMAIL_ADDRESS>wrote:

If you could, just delete the cache, install 3.0.8 and see if it occurs
again.  I'll be trying again later.  Just got my morning meds and going
back to bed.
Ttyl,
John
On Fri, Jan 22, 2021 at 6:13 AM Mitch Williams <
<EMAIL_ADDRESS>wrote:

No worries, would you like me to test out v3.0.8 and see that I have
the same issue still? Do you need me to collect any logs?
I spent a fair bit of time today tidying up my own repo; so I have put
a known bug on the README for any users of my shell scripts to stay on
v2.4.2 for the time being until we have this one sorted. Although I
have noticed that no one has raised an issue on my repo or yours for this
yet; which is a good sign haha.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-765330211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3MXPQQECLZRQFATWDS3FMWXANCNFSM4WAQJ7YQ
.

Why I think this is your answer is that it fits the trace back I had seen
in the log you sent me, that behind something like unreferenced callback.
Two devices with the same name are competing for the same attention, or so
I believe.
TTFN,
John
On Fri, Jan 22, 2021 at 8:10 PM John Talbot<EMAIL_ADDRESS>wrote:

That might be your answer.  The Homebridge API references use displayName.
I don think I changed getCmd to use displayName. I believe it always did.
However displayName might have previously been populated by name first.
Still digging.
I am also not 100% sure the difference between name, displayName and
configuredName.  I thought name is what gets changed when from the GUI you
change a devices name, while Display name never changes.  This all being
counter intuitive.  How configured name plays into it the documentation
does not say and I never use, except for adding it as a object property.
ttfn,
John
On Fri, Jan 22, 2021 at 6:02 PM John Talbot<EMAIL_ADDRESS>wrote:

Hey Mitch,
I might have a thought.  Can you try setting config.name,
config.displayName to be the same in each section of your config.json.
Specifically I noticed My_TemperatureSensor is the same in two different
sections, though config.name is not.
Stated another way, make sure config.name = config.displayName in each
section are the same, but of course the two are different from other
sections.
What I think I see is polling for two different accessories being
addressed by the same displayName.
ttfn,
John
On Fri, Jan 22, 2021 at 4:56 PM John Talbot<EMAIL_ADDRESS>wrote:

I just published 3.0.9.
I don't think it will fix your issue.  It was a problem I noticed if
fetch was removed from the config.json, then it complained that it did not
know how to handle a fetch of undefined.  The fix applies to other
designations, but this should still not be your issue.
I'm going to take a break for tonight.
ttfn,
John
On Fri, Jan 22, 2021 at 1:08 PM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,
I have a few more minutes to dig.  I just looked at your
config.json.  I'm impressed. !!
ttfn,
John
On Fri, Jan 22, 2021 at 8:18 AM John Talbot<EMAIL_ADDRESS>wrote:

If you could, just delete the cache, install 3.0.8 and see if it
occurs again.  I'll be trying again later.  Just got my morning meds and
going back to bed.
Ttyl,
John
On Fri, Jan 22, 2021 at 6:13 AM Mitch Williams <
<EMAIL_ADDRESS>wrote:

No worries, would you like me to test out v3.0.8 and see that I have
the same issue still? Do you need me to collect any logs?
I spent a fair bit of time today tidying up my own repo; so I have
put a known bug on the README for any users of my shell scripts to stay on
v2.4.2 for the time being until we have this one sorted. Although I
have noticed that no one has raised an issue on my repo or yours for this
yet; which is a good sign haha.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-765330211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3MXPQQECLZRQFATWDS3FMWXANCNFSM4WAQJ7YQ
.

Why I think this is your answer is that it fits the trace back I had seen
in the log you sent me, that behind something like unreferenced callback.
Two devices with the same name are competing for the same attention, or so
I believe.
TTFN,
John
On Fri, Jan 22, 2021 at 8:10 PM John Talbot<EMAIL_ADDRESS>wrote:

That might be your answer.  The Homebridge API references use displayName.
I don think I changed getCmd to use displayName. I believe it always did.
However displayName might have previously been populated by name first.
Still digging.
I am also not 100% sure the difference between name, displayName and
configuredName.  I thought name is what gets changed when from the GUI you
change a devices name, while Display name never changes.  This all being
counter intuitive.  How configured name plays into it the documentation
does not say and I never use, except for adding it as a object property.
ttfn,
John
On Fri, Jan 22, 2021 at 6:02 PM John Talbot<EMAIL_ADDRESS>wrote:

Hey Mitch,
I might have a thought.  Can you try setting config.name,
config.displayName to be the same in each section of your config.json.
Specifically I noticed My_TemperatureSensor is the same in two different
sections, though config.name is not.
Stated another way, make sure config.name = config.displayName in each
section are the same, but of course the two are different from other
sections.
What I think I see is polling for two different accessories being
addressed by the same displayName.
ttfn,
John
On Fri, Jan 22, 2021 at 4:56 PM John Talbot<EMAIL_ADDRESS>wrote:

I just published 3.0.9.
I don't think it will fix your issue.  It was a problem I noticed if
fetch was removed from the config.json, then it complained that it did not
know how to handle a fetch of undefined.  The fix applies to other
designations, but this should still not be your issue.
I'm going to take a break for tonight.
ttfn,
John
On Fri, Jan 22, 2021 at 1:08 PM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,
I have a few more minutes to dig.  I just looked at your
config.json.  I'm impressed. !!
ttfn,
John
On Fri, Jan 22, 2021 at 8:18 AM John Talbot<EMAIL_ADDRESS>wrote:

If you could, just delete the cache, install 3.0.8 and see if it
occurs again.  I'll be trying again later.  Just got my morning meds and
going back to bed.
Ttyl,
John
On Fri, Jan 22, 2021 at 6:13 AM Mitch Williams <
<EMAIL_ADDRESS>wrote:

No worries, would you like me to test out v3.0.8 and see that I have
the same issue still? Do you need me to collect any logs?
I spent a fair bit of time today tidying up my own repo; so I have
put a known bug on the README for any users of my shell scripts to stay on
v2.4.2 for the time being until we have this one sorted. Although I
have noticed that no one has raised an issue on my repo or yours for this
yet; which is a good sign haha.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/76#issuecomment-765330211,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3MXPQQECLZRQFATWDS3FMWXANCNFSM4WAQJ7YQ
.

Hey John, sorry for the delay in getting back to you. Yeah my config.json is getting out of hand, my wife would agree that I have a bit of an obsession... It is mostly filled with broadlink RF and cmd4 accessories though!
Ok, so I have updated to cmd4 v3.0.9, I have made my problem accessories displayName and name equal and still am not seeing a difference. A little further fault finding I have found that for the switch accessories, I can turn them off from HomeKit if they are already on and there is no issue, but I cannot set them to on if they are already off. Setting on or off for a switch seems to generate the following log now check index:105. The thermostat accessory does not allow me to execute cool, heat or off and generates the following log check index:188 when commands are executed.
My shell script has logic for if the thermostat is on and then you turn the fan on it will write an off to the thermostat; in real life the thermostat and fan are the one device but different modes, but obviously in HomeKit these need to be represented as two devices, so turning on one turns the other off (if you are following me here). With the thermostat on, I then turned the fan on and it correctly turned off the thermostat but did not turn the fan on. This makes me believe the commands are being executed but then being overwritten in the same scan (potentially by the existing accessory state in the same scan?).

Hey John, sorry for the delay in getting back to you. Yeah my config.json is getting out of hand, my wife would agree that I have a bit of an obsession... It is mostly filled with broadlink RF and cmd4 accessories though!
Ok, so I have updated to cmd4 v3.0.9, I have made my problem accessories displayName and name equal and still am not seeing a difference. A little further fault finding I have found that for the switch accessories, I can turn them off from HomeKit if they are already on and there is no issue, but I cannot set them to on if they are already off. Setting on or off for a switch seems to generate the following log now check index:105. The thermostat accessory does not allow me to execute cool, heat or off and generates the following log check index:188 when commands are executed.
My shell script has logic for if the thermostat is on and then you turn the fan on it will write an off to the thermostat; in real life the thermostat and fan are the one device but different modes, but obviously in HomeKit these need to be represented as two devices, so turning on one turns the other off (if you are following me here). With the thermostat on, I then turned the fan on and it correctly turned off the thermostat but did not turn the fan on. This makes me believe the commands are being executed but then being overwritten in the same scan (potentially by the existing accessory state in the same scan?).

Hi Mitch,
My testing seems to conclude this.  Accessory's cannot have the same
displayName in the newer Cmd4. This was a bug in the previous version that
was not an issue because from the GUI you could not change the devices
name. Changing the name from the GUI sends a request to change config.name,
breaking any script you had that referenced the old name. The displayName
sends a request to change config.name or config.configuredName, as oddly as
that sounds.
When you make the change, you might need to clear the Homebridge cache. Not
sure on that one.
Back to bed for me,
John
On Fri, Jan 22, 2021 at 8:16 PM John Talbot<EMAIL_ADDRESS>wrote:

Why I think this is your answer is that it fits the trace back I had seen
in the log you sent me, that behind something like unreferenced callback.
Two devices with the same name are competing for the same attention, or so
I believe.
TTFN,
John
On Fri, Jan 22, 2021 at 8:10 PM John Talbot<EMAIL_ADDRESS>wrote:

That might be your answer.  The Homebridge API references use
displayName. I don think I changed getCmd to use displayName. I believe it
always did. However displayName might have previously been populated by
name first.  Still digging.
I am also not 100% sure the difference between name, displayName and
configuredName.  I thought name is what gets changed when from the GUI you
change a devices name, while Display name never changes.  This all being
counter intuitive.  How configured name plays into it the documentation
does not say and I never use, except for adding it as a object property.
ttfn,
John
On Fri, Jan 22, 2021 at 6:02 PM John Talbot<EMAIL_ADDRESS>wrote:

Hey Mitch,
I might have a thought.  Can you try setting config.name,
config.displayName to be the same in each section of your config.json.
Specifically I noticed My_TemperatureSensor is the same in two different
sections, though config.name is not.
Stated another way, make sure config.name = config.displayName in each
section are the same, but of course the two are different from other
sections.
What I think I see is polling for two different accessories being
addressed by the same displayName.
ttfn,
John
On Fri, Jan 22, 2021 at 4:56 PM John Talbot<EMAIL_ADDRESS>wrote:

I just published 3.0.9.
I don't think it will fix your issue.  It was a problem I noticed if
fetch was removed from the config.json, then it complained that it did not
know how to handle a fetch of undefined.  The fix applies to other
designations, but this should still not be your issue.
I'm going to take a break for tonight.
ttfn,
John
On Fri, Jan 22, 2021 at 1:08 PM John Talbot<EMAIL_ADDRESS>wrote:

Hi Mitch,