EUROtronic Stella-Z

Posted on
Fri Oct 11, 2013 8:14 am
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: EUROtronic Stella-Z

matt (support) wrote:
wysinawyg wrote:
Is that actually a monitorable "state" that I can trigger off?

Yes, that is the Heater Equipment State that you can access from a Device State Change type of Trigger.

Oops -- I was wrong. As autolog mentioned above, it doesn't support equipment state (just mode).

Image

Posted on
Fri Oct 11, 2013 8:16 am
wysinawyg offline
Posts: 45
Joined: Oct 11, 2013

Re: EUROtronic Stella-Z

Thanks both.

So if I'm following what you're saying right Autolog the setpoint is completely independent of the flame symbol. So if I have the Stella "Off", setpoint at 20c and its only 18c, there isn't any way to automatically switch on the Stella. Equally if the setpoint is 10c and its actually 20c, if the Stella is in Heat mode the flame will show up regardless of the fact that the valve is closed.

Bit of a nuisance, but I think the Horstman thermostat might be different; I'll have to have a play this evening. Is there a similar page for the HRT4?

Posted on
Fri Oct 11, 2013 8:31 am
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: EUROtronic Stella-Z

wysinawyg wrote:
Is there a similar page for the HRT4?

Not yet. It will be linked to from this page once we have it up. We've been adding support for new Z-Wave hardware faster than we can keep up with the documentation. At least that is the excuse I'm using. :-)

Image

Posted on
Fri Oct 11, 2013 8:51 am
autolog offline
Posts: 3988
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT aka UTC]

Re: EUROtronic Stella-Z

wysinawyg wrote:
Thanks both.

So if I'm following what you're saying right Autolog the setpoint is completely independent of the flame symbol. So if I have the Stella "Off", setpoint at 20c and its only 18c, there isn't any way to automatically switch on the Stella. Equally if the setpoint is 10c and its actually 20c, if the Stella is in Heat mode the flame will show up regardless of the fact that the valve is closed.

Bit of a nuisance, but I think the Horstman thermostat might be different; I'll have to have a play this evening. Is there a similar page for the HRT4?

If the Stella is "off", it sets the setpoint to 6 Deg C (Frost Protection) and in this mode the setpoint can't be altered AFAIK. In "Comfort" mode (Indigo "Heat" setting) the setpoint is defaulted to 22 deg C. However in this mode the setpoint can be changed from 0 deg C to 50 deg C. So in fact you can achieve the "off" state by being in "Comfort" mode and setting the Setpoint to 6 deg C. I haven't conclusively proved it but I suspect the the valve may still be open when the setpoint and temperature match. Unfortunately there isn't much info available on the algorithm it uses (I haven't been able to find any). My script addresses these issues by maintaining an independant user setpoint in a variable and forcing the stella setpoint to 6 deg C when temperature exceeds the user setpoint.

Posted on
Fri Oct 11, 2013 9:24 am
autolog offline
Posts: 3988
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT aka UTC]

Re: EUROtronic Stella-Z

I am having difficulty syncing one of my Stella-Zs.

I have successfully included it on the Z-Stick and Indigo can see it in the new device list.
When I go to sync it - the sync times out.

I have turned on z-wave debugging and get the following log entries:
Code: Select all
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 23 02 84 07 51 (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 05 00 13 02 01 EA (node NAK)
  Z-Wave Debug                    RCVD nodeAwake: 01 08 00 04 00 23 02 84 07 51
  Z-Wave Debug                    . .  nodeAwake: node 035
  Z-Wave Debug                    SENT goToSleep: 01 09 00 13 23 02 84 08 05 03 4E
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 28 02 84 07 5A (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 38 02 84 07 4A (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 05 00 13 03 01 EB (node NAK)
  Z-Wave Error                    send "035 - General Thermostat (v2)" goToSleep command failed (module might be asleep, or is unreachable)
  Z-Wave Debug                    RCVD nodeAwake: 01 08 00 04 00 28 02 84 07 5A
  Z-Wave Debug                    . .  nodeAwake: node 040
  Z-Wave Debug                    SENT goToSleep: 01 09 00 13 28 02 84 08 05 04 42
  Z-Wave Debug                    RCVD goToSleep: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD (unsolicited2 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 38 02 84 07 4A (unsolicited2 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 38 02 84 07 4A (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 05 00 13 04 01 EC (node NAK)
  Z-Wave Error                    send "040 - General Thermostat (v2)" goToSleep command failed (module might be asleep, or is unreachable)
  Z-Wave Debug                    RCVD requestNodeInfo: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD
  Z-Wave Debug                    RCVD nodeAwake: 01 08 00 04 00 38 02 84 07 4A
  Z-Wave Debug                    . .  nodeAwake: node 056
  Z-Wave Debug                    SENT goToSleep: 01 09 00 13 38 02 84 08 05 05 53
  Z-Wave Debug                    SENT goToSleep: 01 09 00 13 1F 02 84 08 05 06 77
  Z-Wave Debug                    RCVD goToSleep: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 38 02 84 07 4A (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 38 02 84 07 4A (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 38 02 84 07 4A (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 05 00 13 06 01 EE (node NAK)
  Z-Wave Debug                    RCVD requestNodeInfo: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD
  Z-Wave Debug                    RCVD nodeAwake: 01 08 00 04 00 38 02 84 07 4A
  Z-Wave Debug                    . .  nodeAwake: node 056
  Z-Wave Debug                    SENT goToSleep: 01 09 00 13 38 02 84 08 05 07 51
  Z-Wave Debug                    RCVD goToSleep: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD (unsolicited2 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 38 02 84 07 4A (unsolicited2 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD (unsolicited2 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 38 02 84 07 4A (unsolicited2 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 38 02 84 07 4A (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 38 02 84 07 4A (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD requestNodeInfo: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD
  Z-Wave Debug                    RCVD nodeAwake: 01 08 00 04 00 38 02 84 07 4A
  Z-Wave Debug                    . .  nodeAwake: node 056
  Z-Wave Debug                    SENT goToSleep: 01 09 00 13 38 02 84 08 05 08 5E
  Z-Wave Debug                    RCVD goToSleep: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD (unsolicited2 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 38 02 84 07 4A (unsolicited2 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 38 02 84 07 4A (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD requestNodeInfo: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD
  Z-Wave Debug                    RCVD nodeAwake: 01 08 00 04 00 38 02 84 07 4A
  Z-Wave Debug                    . .  nodeAwake: node 056
  Z-Wave Debug                    SENT goToSleep: 01 09 00 13 38 02 84 08 05 09 5F
  Z-Wave Debug                    SENT goToSleep: 01 09 00 13 1F 02 84 08 05 0A 7B
  Z-Wave Debug                    RCVD goToSleep: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 08 00 04 00 38 02 84 07 4A (unsolicited3 -- requeuing)
  Z-Wave Debug                    RCVD goToSleep: 01 05 00 13 0A 01 E2 (node NAK)
  Z-Wave Debug                    RCVD requestNodeInfo: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD
  Z-Wave Debug                    RCVD nodeAwake: 01 08 00 04 00 38 02 84 07 4A
  Z-Wave Debug                    . .  nodeAwake: node 056
  Z-Wave Debug                    SENT goToSleep: 01 09 00 13 38 02 84 08 05 0B 5D
  Z-Wave Debug                    RCVD requestNodeInfo: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD
  Z-Wave Debug                    RCVD nodeAwake: 01 08 00 04 00 38 02 84 07 4A
  Z-Wave Debug                    . .  nodeAwake: node 056
  Z-Wave Debug                    SENT goToSleep: 01 09 00 13 38 02 84 08 05 0C 5A
  Z-Wave Debug                    RCVD requestNodeInfo: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD
  Z-Wave Debug                    RCVD nodeAwake: 01 08 00 04 00 38 02 84 07 4A
  Z-Wave Debug                    . .  nodeAwake: node 056
  Z-Wave Debug                    SENT goToSleep: 01 09 00 13 38 02 84 08 05 0D 5B
  Z-Wave Debug                    RCVD requestNodeInfo: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD
  Z-Wave Debug                    RCVD nodeAwake: 01 08 00 04 00 38 02 84 07 4A
  Z-Wave Debug                    . .  nodeAwake: node 056
  Z-Wave Debug                    SENT goToSleep: 01 09 00 13 38 02 84 08 05 0E 58

11 Oct 2013 16:10:18
  Z-Wave Debug                    intiatingSyncUI (timeout in 300 seconds)
  Z-Wave                          Syncing - started for device "056 - General Thermostat (v2)"
  Z-Wave Debug                    SENT getNodeNeighbors: 01 06 00 80 38 01 01 41
  Z-Wave Debug                    RCVD getNodeNeighbors: 01 20 01 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5E
  Z-Wave Debug                    . .  getNodeNeighbors: nodeId 056, neighbors: - none -
  Z-Wave                          Syncing - retrieved module neighbors list: - none -
  Z-Wave                          Syncing - requesting neighbor list update of "056 - General Thermostat (v2)"
  Z-Wave Debug                    SENT requestNeighborUpdate: 01 04 00 48 38 8B
  Z-Wave Debug                    RCVD requestNeighborUpdate: 06 (ACK)
  Z-Wave Debug                    RCVD requestNeighborUpdate: 01 05 00 48 01 21 92
  Z-Wave Debug                    . .  requestNeighborUpdate: node 056, update starting
  Z-Wave Debug                    RCVD nodeAwake: 01 08 00 04 00 38 02 84 07 4A
  Z-Wave Debug                    . .  nodeAwake: node 056 (queued awake processing because sync in progress)
  Z-Wave Debug                    RCVD nodeAwake: 01 08 00 04 00 21 02 84 07 53
  Z-Wave Debug                    . .  nodeAwake: node 033 (queued awake processing because sync in progress)
  Z-Wave Debug                    RCVD nodeAwake: 01 08 00 04 00 38 02 84 07 4A
  Z-Wave Debug                    . .  nodeAwake: node 056 (queued awake processing because sync in progress)
  Z-Wave Debug                    RCVD requestNeighborUpdate: 01 05 00 48 01 22 91
  Z-Wave Debug                    . .  requestNeighborUpdate: node 056, update finished
  Z-Wave Debug                    SENT getNodeNeighbors: 01 06 00 80 38 01 01 41
  Z-Wave Debug                    RCVD getNodeNeighbors: 01 20 01 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5E
  Z-Wave Debug                    . .  getNodeNeighbors: nodeId 056, neighbors: - none -
  Z-Wave                          Syncing - neighbor list update complete (no change)
  Z-Wave                          Syncing - assigning return route to "056 - General Thermostat (v2)"
  Z-Wave Debug                    SENT assignReturnRoute: 01 05 00 46 38 01 85
  Z-Wave Debug                    RCVD assignReturnRoute: 01 04 01 46 01 BD
  Z-Wave Debug                    RCVD assignReturnRoute: 01 05 00 46 01 00 BD
  Z-Wave Debug                    . .  assignReturnRoute: node 056, success 1
  Z-Wave                          Syncing - assigned return route
  Z-Wave Debug                    SENT requestNodeInfo: 01 06 00 60 38 04 0F AA
  Z-Wave Debug                    RCVD requestNodeInfo: 01 13 00 49 84 38 0D 04 08 06 20 26 31 40 43 77 80 84 72 86 AD
  Z-Wave Debug                    . .  requestNodeInfo: node 056, combined class list: 20v1 40v1 43v1 84v1 26v1 86v1 80v1 31v1 72v1 77v1
  Z-Wave Debug                    SENT requestManufactureInfo: 01 09 00 13 38 02 72 04 05 10 BC
  Z-Wave Debug                    RCVD requestManufactureInfo: 01 0E 00 04 00 38 08 72 05 01 48 00 01 00 01 FB
  Z-Wave Debug                    . .  requestManufactureInfo: node 056, manufacturerId 0148, productId 00010001
  Z-Wave Debug                    . .  requestManufactureInfo: EUROtronic, Thermostat (Stella Z)
  Z-Wave                          Syncing - retrieved manufacture and model names: EUROtronic - 0148, Thermostat (Stella Z) - 00010001
  Z-Wave Debug                    SENT requestVersInfoGen: 01 09 00 13 38 02 86 11 05 11 5C
  Z-Wave Debug                    RCVD requestVersInfoGen: 01 0D 00 04 00 38 07 86 12 03 03 2A 00 04 73
  Z-Wave Debug                    . .  requestVersInfoGen: node 056, protoVers 3.42, appVers 0.04
  Z-Wave                          Syncing - retrieved protocol version 3.42, app version 0.04
  Z-Wave Debug                    SENT requestVersInfoCmdClass: 01 0A 00 13 38 03 86 13 84 05 12 DB
  Z-Wave Debug                    RCVD requestVersInfoCmdClass: 01 0A 00 04 00 38 04 86 14 84 02 D9
  Z-Wave Debug                    . .  requestVersInfoCmdClass: node 056, class command 84 using version 2
  Z-Wave Debug                    . .  requestVersInfoCmdClass: node 056, combined class list: 20v1 40v1 43v1 84v2 26v1 86v1 80v1 31v1 72v1 77v1
  Z-Wave Debug                    SENT requestVersInfoCmdClass: 01 0A 00 13 38 03 86 13 26 05 13 78
  Z-Wave Debug                    RCVD requestVersInfoCmdClass: 01 0A 00 04 00 38 04 86 14 26 03 7A
  Z-Wave Debug                    . .  requestVersInfoCmdClass: node 056, class command 26 using version 3
  Z-Wave Debug                    . .  requestVersInfoCmdClass: node 056, combined class list: 20v1 40v1 43v1 84v2 26v3 86v1 80v1 31v1 72v1 77v1
  Z-Wave Debug                    SENT requestVersInfoCmdClass: 01 0A 00 13 38 03 86 13 31 05 14 68
  Z-Wave Debug                    RCVD requestVersInfoCmdClass: 01 0A 00 04 00 38 04 86 14 31 04 6A
  Z-Wave Debug                    . .  requestVersInfoCmdClass: node 056, class command 31 using version 4
  Z-Wave Debug                    . .  requestVersInfoCmdClass: node 056, combined class list: 20v1 40v1 43v1 84v2 26v3 86v1 80v1 31v4 72v1 77v1
  Z-Wave                          Syncing - retrieved class hierarchy: Routing Slave : Thermostat : General Thermostat (v2) (04 : 08 : 06, base 40)
  Z-Wave                          Syncing - retrieved command classes: 20v1 40v1 43v1 84v2 26v3 86v1 80v1 31v4 72v1 77v1
  Z-Wave Debug                    SENT requestWakeInterval: 01 09 00 13 38 02 84 05 05 15 4E
  Z-Wave Debug                    RCVD requestWakeInterval: 01 0C 00 04 00 38 06 84 06 00 0E 10 01 54
  Z-Wave Debug                    . .  requestWakeInterval: node 056, interval 60 minutes, wakeTarget 001
  Z-Wave                          Syncing - retrieved wake interval of 60 minutes
  Z-Wave Debug                    SENT requestBatteryLevel: 01 09 00 13 38 02 80 02 05 16 4E

11 Oct 2013 16:10:58
  Z-Wave Error                    Timeout waiting for "056 - General Thermostat (v2)". Module might be asleep, or is unreachable.


Before I start the sync, I can press the button on the Stella-Z and the Led lights up for a short while and unsolicited entries appear in the log. I do this button pressing a number of times to prove (to myself) that there is communication happening. I then start the sync and press the button (a number of times) on the Stella-Z. This would normally complete the sync. In this case it doesn't. The sync times out and the Stella-Z appears to be "asleep" and pressing the button which would normally wake it up - doesn't. The LED remains off. the only way to restart the process is to remove and then reinstall the batteries.

I am not sure if I have yet another defective Stella-Z or the issue is sync related?

I have excluded it and included it a number of times to test it out. Any thoughts appreciated :)

Posted on
Sat Oct 12, 2013 9:13 am
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: EUROtronic Stella-Z

I'm not sure. It sure sounds like it is going to sleep too quickly and causing the sync to fail. But I'm not sure why your attempts at keeping it awake aren't helping.

Image

Posted on
Sat Oct 12, 2013 10:03 am
sgbirch offline
Posts: 99
Joined: Sep 11, 2013

Re: EUROtronic Stella-Z

autolog wrote:
In case anyone is interested, I am developing a script to handle these thermostat actuators more effectively in a multi-radiator scenario.


Oh YES. I have a three zone house with quite a few radiators and would like to improve the boiler utilisation using zwave and indigo.

Like you, I would guess, I have been very disappointed by the Danfoss and delighted by the Stella. If it does what they claim it is perfect for both rad control AND boiler control.

I am also hoping the guys at indigo will add an action which will permit us to change the wakeup interval dynamically so the units can sleep for long periods at night but wake up frequently when a set point change is likely. I would think that being able to set the wakeup interval in an action would be useful for many battery devices.

Steve

Posted on
Sat Oct 12, 2013 11:00 am
sgbirch offline
Posts: 99
Joined: Sep 11, 2013

Re: EUROtronic Stella-Z

autolog wrote:
The current status is that the MK 1 set of scripts is working. I am in the process of reworking this so that it is all contained in one script (the MK 2). Once I have got that working and tested, I will try to turn it into a plug-in which as I haven't done one before will be more of a challenge :wink:

That would be brilliant, are you programming in python or applescript?
autolog wrote:
The system as currently implemented enables you to set the following target Heat Setpoints:
    An 'off' temperature e.g. 6 deg C
    A morning 'on' temperature e.g. 20 deg C
    An evening 'on' temperature e.g. 21 deg C
I only allow for two "on" periods in a day as I don't need any more. This wouldn't be too difficult to extend if necessary.

My need has a further complication. I am hoping to have a 15 deg setback, when a room is ready for use but currently unused. The idea is that the room can be brought to full heat when my daughter's iPhone is spotted in the house.
autolog wrote:
The system also has a "boost" feature. Basically this looks at the current temperature and sets a Heat Setpoint a user specified number of degrees higher (e.g. 1 deg C) than the existing temperature being recorded by the Stella-Z thereby forcing it on. The "boost" lasts for a user specified amount of time (e.g. 15 minutes). It handles the situation where a "boost" is done just before a scheduled Am or PM heating period.

I'm not sure I understand the logic behind the boost, is it the result of observing the system?
autolog wrote:
This all links to a common "boiler connect" relay (Secure SSR303) to turn on the boiler when any Stella-Z is calling for heat. I have just replaced the master thermostat with this device as that was the easiest way to interface into the original heating system. The Secure SSR303 has to be kept alive - it goes to default 'off' mode if it isn't given an 'on' or 'off' command at least once an hour. The system handles this.

I am hoping to use Fibaro relays but I am not sure if they can stand the inductive load of the zone control valves, I have three zones plus water, so I need four switches.
autolog wrote:
One aspect of the Stella-z that is interesting to me is how the temperature is read. When the radiator is 'off' it seems reasonable. Once the radiator starts heating up the temperature goes up higher than I think it actually is. This is probably because the temperature sensor is located in the radiator valve. I might have to put an "allowance factor" in for this. Another possibility is to associate the thermostat in some way with another temperature sensor (e.g. on the wall) and use this to control the Stella-Z. I will probably put this feature into the script.

I have only done radiator-off testing so far, but was worried about that. I notice the stella has a gap low down on the front face, if that is the temperature sensor we may get better readings by pointing it away from the rad. I am hoping that a second sensor is not required to keep the cost down. Although, I have been using a second z-wave temp sensor while debugging, to make sure the stella is accurate. As you say, it looks ok with the radiator off. I suspect you are correct and calibration will be required.

We may also find we need to apply some control theory to this problem to prevent overshoot. The Stella spec said that we can directly control the water flow through the valve so a simple PID would be possible.

http://en.wikipedia.org/wiki/PID_controller

This is for an oven, but a good read:

http://newton.ex.ac.uk/teaching/CDHW/Feedback/ControlTypes.html

autolog wrote:
If the script was to fail there are a number of fall back scenarios. Operate the Stella-Zs from the Indigo Devices list or schedules list to set the heat setpoints and control the boiler switch the same way. As a last resort, remove the Stella-Zs, refit the TRVs and use the physical buttons on the boiler connect relay to turn the boiler on and off. :)


Yeah .. my fallback position will be openzwave. I am *VERY* happy with indigo, but not being able to open the lid and tweak (which I fully understand) is a bit frustrating.

Posted on
Sat Oct 12, 2013 2:08 pm
autolog offline
Posts: 3988
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT aka UTC]

Re: EUROtronic Stella-Z

sgbirch wrote:
autolog wrote:
The current status is that the MK 1 set of scripts is working. I am in the process of reworking this so that it is all contained in one script (the MK 2). Once I have got that working and tested, I will try to turn it into a plug-in which as I haven't done one before will be more of a challenge :wink:

That would be brilliant, are you programming in python or applescript?

I am coding in Python.
sgbirch wrote:
autolog wrote:
The system as currently implemented enables you to set the following target Heat Setpoints:
    An 'off' temperature e.g. 6 deg C
    A morning 'on' temperature e.g. 20 deg C
    An evening 'on' temperature e.g. 21 deg C
I only allow for two "on" periods in a day as I don't need any more. This wouldn't be too difficult to extend if necessary.

My need has a further complication. I am hoping to have a 15 deg setback, when a room is ready for use but currently unused. The idea is that the room can be brought to full heat when my daughter's iPhone is spotted in the house.

Not sure what you mean by a setback? Do you mean if the normal occupied temperature is 21, then the setback temperature is 21-15 = 6? The off, morning and evening temperatures are all configurable. You can also advance to the next scheduled time (on or off). Do you need a setting that is basically always 'on' if the iphone is in the house (regardless of any timers set)? It should be easy enough to add something like that in.
sgbirch wrote:
autolog wrote:
The system also has a "boost" feature. Basically this looks at the current temperature and sets a Heat Setpoint a user specified number of degrees higher (e.g. 1 deg C) than the existing temperature being recorded by the Stella-Z thereby forcing it on. The "boost" lasts for a user specified amount of time (e.g. 15 minutes). It handles the situation where a "boost" is done just before a scheduled Am or PM heating period.

I'm not sure I understand the logic behind the boost, is it the result of observing the system?

A "boost" is just a facility to give instant heat on a radiator without worrying about a) any AM or PM timers set and b) what the existing temperature is as it will automatically provide some heat.
sgbirch wrote:
autolog wrote:
This all links to a common "boiler connect" relay (Secure SSR303) to turn on the boiler when any Stella-Z is calling for heat. I have just replaced the master thermostat with this device as that was the easiest way to interface into the original heating system. The Secure SSR303 has to be kept alive - it goes to default 'off' mode if it isn't given an 'on' or 'off' command at least once an hour. The system handles this.

I am hoping to use Fibaro relays but I am not sure if they can stand the inductive load of the zone control valves, I have three zones plus water, so I need four switches.

How are the zones switched on at the moment? As I mentioned, I effectively replaced my standard thermostat with the SSR303 which controlled just my single zone. It meant I didn't have to worry about the wiring too much. The SSR303 has buttons on the front so it can be manually turned 'on' and 'off' which is an advantage in a fall-back scenario. Of course with the new set-up I effectively have 12 zones as each radiator is an effective zone.
sgbirch wrote:
autolog wrote:
One aspect of the Stella-z that is interesting to me is how the temperature is read. When the radiator is 'off' it seems reasonable. Once the radiator starts heating up the temperature goes up higher than I think it actually is. This is probably because the temperature sensor is located in the radiator valve. I might have to put an "allowance factor" in for this. Another possibility is to associate the thermostat in some way with another temperature sensor (e.g. on the wall) and use this to control the Stella-Z. I will probably put this feature into the script.

I have only done radiator-off testing so far, but was worried about that. I notice the stella has a gap low down on the front face, if that is the temperature sensor we may get better readings by pointing it away from the rad. I am hoping that a second sensor is not required to keep the cost down. Although, I have been using a second z-wave temp sensor while debugging, to make sure the stella is accurate. As you say, it looks ok with the radiator off. I suspect you are correct and calibration will be required.

We may also find we need to apply some control theory to this problem to prevent overshoot. The Stella spec said that we can directly control the water flow through the valve so a simple PID would be possible.

http://en.wikipedia.org/wiki/PID_controller

This is for an oven, but a good read:

http://newton.ex.ac.uk/teaching/CDHW/Feedback/ControlTypes.html

Thanks for the links. At the moment Indigo can't directly control the radiator valves but hopefully this will happen in due course, in which case I think this is the way to go and your links will come into play :)
sgbirch wrote:

autolog wrote:
If the script was to fail there are a number of fall back scenarios. Operate the Stella-Zs from the Indigo Devices list or schedules list to set the heat setpoints and control the boiler switch the same way. As a last resort, remove the Stella-Zs, refit the TRVs and use the physical buttons on the boiler connect relay to turn the boiler on and off. :)


Yeah .. my fallback position will be openzwave. I am *VERY* happy with indigo, but not being able to open the lid and tweak (which I fully understand) is a bit frustrating.
I suspect their major focus has been to get z-wave incorporated into Indigo. It has already been stated that they intend to allow low-level z-wave commands to be issued from Indigo, so I am hopeful that this will happen before too long. :)

Posted on
Sat Oct 12, 2013 2:18 pm
autolog offline
Posts: 3988
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT aka UTC]

Re: EUROtronic Stella-Z

matt (support) wrote:
I'm not sure. It sure sounds like it is going to sleep too quickly and causing the sync to fail. But I'm not sure why your attempts at keeping it awake aren't helping.
Is there a way to tell it stay awake before the sync completes? Is the sync an Indigo software feature or is it something that the Stella-Z has to store within it so that it knows it is attached to Indigo. Could I backup and then edit the database and replicate an existing definition but change the device address? I am still trying to learn about all of this stuff :wink:

Posted on
Sun Oct 13, 2013 9:21 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: EUROtronic Stella-Z

autolog wrote:
matt (support) wrote:
I'm not sure. It sure sounds like it is going to sleep too quickly and causing the sync to fail. But I'm not sure why your attempts at keeping it awake aren't helping.
Is there a way to tell it stay awake before the sync completes? Is the sync an Indigo software feature or is it something that the Stella-Z has to store within it so that it knows it is attached to Indigo. Could I backup and then edit the database and replicate an existing definition but change the device address? I am still trying to learn about all of this stuff :wink:


There isn't a way for Indigo to tell the module to stay awake. All it can do is not send the module a "go to sleep" command once it receives the "I'm Awake" command from the module. Based on the Event Log snipped you posted above Indigo is doing this correctly (it stops telling the module to go back to sleep once it starts the sync, thus the module should be staying awake).

Indigo's sync is just the name we give to the process of: 1) getting all of the information and settings from the module Indigo needs to be able to communicate and define the Indigo devices, 2) automatically adding associations from modules back to the Z-Stick, and writing configuration settings to the module. So basically it is the process of discovering the capabilities/settings of the module, and preparing the module for use with Indigo.

For the case of the Stella, there isn't a lot Indigo needs to do. So if the only problem is the module won't sync for some reason, then you could try hacking the database XML (after a backup!). I'm not positive it will work, but it might be worth a shot. Once you duplicate an existing Stella device that has been sync'd, you'll want to change the following in the duplicate <Device>: The <ID> integer (just pick a random number, which isn't used elsewhere in the database file), <Name> (change to the UI name you want to give the device), and <address> (the Z-Wave node ID for the module).

Image

Posted on
Mon Oct 14, 2013 5:11 am
autolog offline
Posts: 3988
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT aka UTC]

Re: EUROtronic Stella-Z

matt (support) wrote:
autolog wrote:
matt (support) wrote:
I'm not sure. It sure sounds like it is going to sleep too quickly and causing the sync to fail. But I'm not sure why your attempts at keeping it awake aren't helping.
Is there a way to tell it stay awake before the sync completes? Is the sync an Indigo software feature or is it something that the Stella-Z has to store within it so that it knows it is attached to Indigo. Could I backup and then edit the database and replicate an existing definition but change the device address? I am still trying to learn about all of this stuff :wink:


There isn't a way for Indigo to tell the module to stay awake. All it can do is not send the module a "go to sleep" command once it receives the "I'm Awake" command from the module. Based on the Event Log snipped you posted above Indigo is doing this correctly (it stops telling the module to go back to sleep once it starts the sync, thus the module should be staying awake).

Indigo's sync is just the name we give to the process of: 1) getting all of the information and settings from the module Indigo needs to be able to communicate and define the Indigo devices, 2) automatically adding associations from modules back to the Z-Stick, and writing configuration settings to the module. So basically it is the process of discovering the capabilities/settings of the module, and preparing the module for use with Indigo.

For the case of the Stella, there isn't a lot Indigo needs to do. So if the only problem is the module won't sync for some reason, then you could try hacking the database XML (after a backup!). I'm not positive it will work, but it might be worth a shot. Once you duplicate an existing Stella device that has been sync'd, you'll want to change the following in the duplicate <Device>: The <ID> integer (just pick a random number, which isn't used elsewhere in the database file), <Name> (change to the UI name you want to give the device), and <address> (the Z-Wave node ID for the module).


Thanks for the help on how to proceed with this :)

I excluded the device from the z-stick and then checked in Indigo that there was no device present. I then included the device and added it to Indigo. As expected the sync failed. So I hacked the database as you advised by duplicating an existing device and using the id from the newly added (but unsuccessfully sync'd device) which I then removed. Restarted Indigo and the device was present in the list. I initiated communications by pressing the button on the front of the Stella and then the z-wave in Indigo locked out and the led on the front of the device stayed solidly on.

I am coming to the conclusion that there is a problem with the Stella-Z as when I press the button for 2.5 seconds, it is meant to initialize and find the extent of the valve movement - it isn't doing this :(

Posted on
Tue Oct 15, 2013 1:31 pm
autolog offline
Posts: 3988
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT aka UTC]

Re: EUROtronic Stella-Z

autolog wrote:
... I am coming to the conclusion that there is a problem with the Stella-Z as when I press the button for 2.5 seconds, it is meant to initialize and find the extent of the valve movement - it isn't doing this :(

Actually, I got the detail wrong - you have to do continuous pushing of the button to start the calibration process - not that that makes any difference as it still doesn't do it.

I have a wider problem in that the thermostats lose connection with Indigo and the status goes to "no ack" (no acknowledgement). I have implemented a recovery system that works - so at least it keeps the heating going. However, I am trying to find the route cause of the issue - is it hardware, software or a combination of the both.

When looking at the Z-Stick, most of the time the LED blue light circle is lit. It flashes off and on when the the thermostats wake up and Z-Wave commands are transmitted (and the z-wave indicator in the main dialogue indicates activity). When contact is lost, the blue led light goes out and stays out for long periods of time maybe having an occasional blue led flash but effectively seeming stuck in the non-illuminated state. The log then fills up with errors as one thermostat after another goes to a 'no ack' status. My logic detects this state and reloads the Z-stick, checks what state the thermostats should be in and resets the system so that everything is as it was before the reload. The system then proceeds as normal until the next time connection is lost.

There seems to be no particular event that causes the issue. It can happen randomly with different thermostats losing connection first.

The good news is that the flexibility of the Indigo system has allowed me to program in a recovery system :)

A day or so back, I did detect a couple of z-wave plugin errors (which may be related) but normally there is nothing.

Here is one of the plugin errors:
Code: Select all
2013-10-13 09:06:58   Z-Wave   sent "T07_Thermostat" mode status request
2013-10-13 09:06:58   Z-Wave   sent "T07_Thermostat" temperature status request
2013-10-13 09:06:58   Z-Wave   sent "T07_Thermostat" heat setpoint status request
2013-10-13 09:06:58   Z-Wave   received "T07_Thermostat" mode is heat
2013-10-13 09:06:58   Z-Wave   received "T07_Thermostat" temperature update to 20.0 °C
2013-10-13 09:06:58   Z-Wave   received "T07_Thermostat" heat setpoint is 6.0 °C
2013-10-13 09:07:24   Z-Wave   sent "T12_Thermostat" mode status request
2013-10-13 09:07:24   Z-Wave   sent "T12_Thermostat" temperature status request
2013-10-13 09:07:24   Z-Wave   sent "T12_Thermostat" heat setpoint status request
2013-10-13 09:07:24   Z-Wave   received "T12_Thermostat" mode is heat
2013-10-13 09:07:24   Z-Wave Error   Error in plugin execution:

Traceback (most recent call last):
  File "/Library/Application Support/Perceptive Automation/Indigo 6/IndigoPluginHost.app/Contents/PlugIns/serialinterface.py", line 433, in startCommThread
    self.processCommThread()
  File "/Library/Application Support/Perceptive Automation/Indigo 6/IndigoPluginHost.app/Contents/PlugIns/serialinterface.py", line 607, in processCommThread
    self.processQueueInPacket(packet)         # Subclass is required to define.
  File "zwaveinterface.py", line 1382, in processQueueInPacket
  File "zwaveinterface.py", line 1356, in _processFuncCall
  File "zwaveinterface.py", line 1407, in _processCommandReply
  File "zwaveinterface.py", line 1354, in _processFuncCall
  File "actionthermostat.py", line 197, in _processHvacModeReply
  File "zwavetriggers.py", line 103, in executeTriggersFromParms
StandardError: ServerCommunicationError -- timeout waiting for response

2013-10-13 09:07:24   Z-Wave Error   exc type is <type 'exceptions.StandardError'>
2013-10-13 09:07:24   Z-Wave Error   restarting serial connection in 5.0 seconds
2013-10-13 09:07:25   Z-Wave   connected to Z-Stick S2 interface on /dev/cu.SLAB_USBtoUART (firmware 3.07)
2013-10-13 09:07:25   Z-Wave   found module included in controller with no matching device (missing or disabled): 056 - General Thermostat (v2)
2013-10-13 09:07:25   Z-Wave   received "T12_Thermostat" temperature update to 18.5 °C
2013-10-13 09:07:25   Z-Wave   received "T12_Thermostat" heat setpoint is 6.0 °C
2013-10-13 09:07:25   Interface Failure   lost connection with interface
2013-10-13 09:07:33   Z-Wave   sent "T09_Thermostat" mode status request
2013-10-13 09:07:33   Z-Wave   sent "T09_Thermostat" temperature status request
2013-10-13 09:07:33   Z-Wave   sent "T09_Thermostat" heat setpoint status request


and here is another:
Code: Select all
2013-10-13 13:13:48   Z-Wave Debug   RCVD nodeAwake: 01 08 00 04 00 27 02 84 07 55
2013-10-13 13:13:48   Z-Wave Debug   . .  nodeAwake: node 039
2013-10-13 13:13:48   Z-Wave Debug   SENT requestHvacMode: 01 09 00 13 27 02 40 02 05 D3 54
2013-10-13 13:13:49   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 1
2013-10-13 13:13:49   Z-Wave   sent "T12_Thermostat" mode status request
2013-10-13 13:13:49   Z-Wave Debug   SENT requestTempStatus: 01 09 00 13 27 02 31 04 05 D4 24
2013-10-13 13:13:49   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 27 03 40 03 01 94 (unsolicited2 -- requeuing)
2013-10-13 13:13:49   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 27 03 40 03 01 94 (unsolicited3 -- requeuing)
2013-10-13 13:13:49   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 2
2013-10-13 13:13:49   Z-Wave   sent "T12_Thermostat" temperature status request
2013-10-13 13:13:49   Z-Wave Debug   SENT requestSetpointVal: 01 0A 00 13 27 03 43 02 01 05 D5 52
2013-10-13 13:13:49   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 27 03 40 03 01 94 (unsolicited2 -- requeuing)
2013-10-13 13:14:03   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 27 03 40 03 01 94 (unsolicited3 -- requeuing)
2013-10-13 13:14:03   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 27 06 31 05 01 22 00 B4 75 (unsolicited3 -- requeuing)
2013-10-13 13:14:03   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 3
2013-10-13 13:14:03   Z-Wave   sent "T12_Thermostat" heat setpoint status request
2013-10-13 13:14:03   Z-Wave Debug   . . . . . . . : skipping battery check (next check in 697 mins)
2013-10-13 13:14:03   Z-Wave Debug   . .  nodeAwake: started inhibit sleep timer
2013-10-13 13:14:03   Z-Wave Debug   RCVD setHvacMode: 01 09 00 04 00 27 03 40 03 01 94
2013-10-13 13:14:03   Z-Wave Debug   . .  setHvacMode: node 039, endpoint None, value 1
2013-10-13 13:14:03   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 2
2013-10-13 13:14:03   Z-Wave   received "T12_Thermostat" mode is heat
2013-10-13 13:14:03   Z-Wave Debug   stopping node status polling
2013-10-13 13:14:03   Z-Wave Debug   stopped zwave packet parser thread
2013-10-13 13:14:03   Z-Wave Error   Error in plugin execution:

Traceback (most recent call last):
  File "/Library/Application Support/Perceptive Automation/Indigo 6/IndigoPluginHost.app/Contents/PlugIns/serialinterface.py", line 433, in startCommThread
    self.processCommThread()
  File "/Library/Application Support/Perceptive Automation/Indigo 6/IndigoPluginHost.app/Contents/PlugIns/serialinterface.py", line 607, in processCommThread
    self.processQueueInPacket(packet)         # Subclass is required to define.
  File "zwaveinterface.py", line 1382, in processQueueInPacket
  File "zwaveinterface.py", line 1356, in _processFuncCall
  File "zwaveinterface.py", line 1407, in _processCommandReply
  File "zwaveinterface.py", line 1354, in _processFuncCall
  File "actionthermostat.py", line 197, in _processHvacModeReply
  File "zwavetriggers.py", line 103, in executeTriggersFromParms
StandardError: ServerCommunicationError -- timeout waiting for response

2013-10-13 13:14:03   Z-Wave Error   exc type is <type 'exceptions.StandardError'>
2013-10-13 13:14:03   Z-Wave Error   restarting serial connection in 5.0 seconds
2013-10-13 13:14:04   Z-Wave Debug   starting serial connection loop


Here is an example of a debug log with lost connections:
Code: Select all
2013-10-15 01:12:00   Schedule   T00 Thermostat Check
2013-10-15 01:12:07   Z-Wave Debug   RCVD nodeAwake: 01 08 00 04 00 2E 02 84 07 5C
2013-10-15 01:12:07   Z-Wave Debug   . .  nodeAwake: node 046
2013-10-15 01:12:07   Z-Wave Debug   SENT requestHvacMode: 01 09 00 13 2E 02 40 02 05 B8 36
2013-10-15 01:12:07   Z-Wave Debug   RCVD requestHvacMode: 01 08 00 04 00 27 02 84 07 55 (unsolicited2 -- requeuing)
2013-10-15 01:12:07   Z-Wave Debug   RCVD requestHvacMode: 01 08 00 04 00 27 02 84 07 55 (unsolicited3 -- requeuing)
2013-10-15 01:12:08   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 1
2013-10-15 01:12:08   Z-Wave   sent "T10_Thermostat" mode status request
2013-10-15 01:12:08   Z-Wave Debug   SENT requestTempStatus: 01 09 00 13 2E 02 31 04 05 B9 40
2013-10-15 01:12:08   Z-Wave Debug   RCVD requestTempStatus: 01 08 00 04 00 27 02 84 07 55 (unsolicited2 -- requeuing)
2013-10-15 01:12:08   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited2 -- requeuing)
2013-10-15 01:12:08   Z-Wave Debug   RCVD requestTempStatus: 01 08 00 04 00 27 02 84 07 55 (unsolicited3 -- requeuing)
2013-10-15 01:12:08   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited3 -- requeuing)
2013-10-15 01:12:08   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited3 -- requeuing)
2013-10-15 01:12:10   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 2
2013-10-15 01:12:10   Z-Wave   sent "T10_Thermostat" temperature status request
2013-10-15 01:12:10   Z-Wave Debug   SENT requestSetpointVal: 01 0A 00 13 2E 03 43 02 01 05 BA 34
2013-10-15 01:12:10   Z-Wave Debug   RCVD requestSetpointVal: 01 08 00 04 00 27 02 84 07 55 (unsolicited2 -- requeuing)
2013-10-15 01:12:10   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited2 -- requeuing)
2013-10-15 01:12:10   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited2 -- requeuing)
2013-10-15 01:12:10   Z-Wave Debug   RCVD requestSetpointVal: 01 08 00 04 00 27 02 84 07 55 (unsolicited3 -- requeuing)
2013-10-15 01:12:10   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited3 -- requeuing)
2013-10-15 01:12:10   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited3 -- requeuing)
2013-10-15 01:12:10   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 3
2013-10-15 01:12:10   Z-Wave   sent "T10_Thermostat" heat setpoint status request
2013-10-15 01:12:10   Z-Wave Debug   . . . . . . . : skipping battery check (next check in 584 mins)
2013-10-15 01:12:10   Z-Wave Debug   . .  nodeAwake: started inhibit sleep timer
2013-10-15 01:12:10   Z-Wave Debug   RCVD nodeAwake: 01 08 00 04 00 27 02 84 07 55
2013-10-15 01:12:10   Z-Wave Debug   . .  nodeAwake: node 039
2013-10-15 01:12:10   Z-Wave Debug   SENT requestHvacMode: 01 09 00 13 27 02 40 02 05 BB 3C
2013-10-15 01:12:10   Z-Wave Debug   RCVD requestHvacMode: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited2 -- requeuing)
2013-10-15 01:12:10   Z-Wave Debug   RCVD requestHvacMode: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited2 -- requeuing)
2013-10-15 01:12:10   Z-Wave Debug   RCVD requestHvacMode: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited3 -- requeuing)
2013-10-15 01:12:10   Z-Wave Debug   RCVD requestHvacMode: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited3 -- requeuing)
2013-10-15 01:12:13   Z-Wave Debug   RCVD requestHvacMode: 01 0C 00 04 00 2E 06 31 05 01 22 00 E6 2E (unsolicited3 -- requeuing)
2013-10-15 01:12:17   Z-Wave Debug   RCVD requestHvacMode: 01 05 00 13 BB 01 53 (node NAK)
2013-10-15 01:12:17   Z-Wave Error   send "T12_Thermostat" mode status request failed
2013-10-15 01:12:17   Z-Wave Debug   SENT requestTempStatus: 01 09 00 13 27 02 31 04 05 BC 4C
2013-10-15 01:12:17   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited2 -- requeuing)
2013-10-15 01:12:17   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited2 -- requeuing)
2013-10-15 01:12:17   Z-Wave Debug   RCVD requestTempStatus: 01 0C 00 04 00 2E 06 31 05 01 22 00 E6 2E (unsolicited2 -- requeuing)
2013-10-15 01:12:17   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited3 -- requeuing)
2013-10-15 01:12:17   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited3 -- requeuing)
2013-10-15 01:12:17   Z-Wave Debug   RCVD requestTempStatus: 01 0C 00 04 00 2E 06 31 05 01 22 00 E6 2E (unsolicited3 -- requeuing)
2013-10-15 01:12:25   Z-Wave Debug   RCVD requestTempStatus: 01 05 00 13 BC 01 54 (node NAK)
2013-10-15 01:12:25   Z-Wave Error   send "T12_Thermostat" temperature status request failed
2013-10-15 01:12:25   Z-Wave Debug   SENT requestSetpointVal: 01 0A 00 13 27 03 43 02 01 05 BD 3A
2013-10-15 01:12:25   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited2 -- requeuing)
2013-10-15 01:12:25   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited2 -- requeuing)
2013-10-15 01:12:25   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 2E 06 31 05 01 22 00 E6 2E (unsolicited2 -- requeuing)
2013-10-15 01:12:25   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited3 -- requeuing)
2013-10-15 01:12:25   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited3 -- requeuing)
2013-10-15 01:12:25   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 2E 06 31 05 01 22 00 E6 2E (unsolicited3 -- requeuing)
2013-10-15 01:12:27   Z-Wave Debug   RCVD requestSetpointVal: 01 08 00 04 00 29 02 84 07 5B (unsolicited3 -- requeuing)
2013-10-15 01:12:34   Z-Wave Debug   RCVD requestSetpointVal: 01 05 00 13 BD 01 55 (node NAK)
2013-10-15 01:12:34   Z-Wave Error   send "T12_Thermostat" heat setpoint status request failed
2013-10-15 01:12:34   Z-Wave Debug   . . . . . . . : skipping battery check (next check in 581 mins)
2013-10-15 01:12:34   Z-Wave Debug   SENT goToSleep: 01 09 00 13 27 02 84 08 05 BE F7
2013-10-15 01:12:34   Z-Wave Debug   RCVD goToSleep: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited2 -- requeuing)
2013-10-15 01:12:34   Z-Wave Debug   RCVD goToSleep: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited2 -- requeuing)
2013-10-15 01:12:34   Z-Wave Debug   RCVD goToSleep: 01 0C 00 04 00 2E 06 31 05 01 22 00 E6 2E (unsolicited2 -- requeuing)
2013-10-15 01:12:34   Z-Wave Debug   RCVD goToSleep: 01 08 00 04 00 29 02 84 07 5B (unsolicited2 -- requeuing)
2013-10-15 01:12:34   Z-Wave Debug   RCVD goToSleep: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited3 -- requeuing)
2013-10-15 01:12:34   Z-Wave Debug   RCVD goToSleep: 01 09 00 04 00 2E 03 40 03 01 9D (unsolicited3 -- requeuing)
2013-10-15 01:12:34   Z-Wave Debug   RCVD goToSleep: 01 0C 00 04 00 2E 06 31 05 01 22 00 E6 2E (unsolicited3 -- requeuing)
2013-10-15 01:12:34   Z-Wave Debug   RCVD goToSleep: 01 08 00 04 00 29 02 84 07 5B (unsolicited3 -- requeuing)
2013-10-15 01:12:35   Z-Wave Debug   RCVD goToSleep: 01 08 00 04 00 28 02 84 07 5A (unsolicited3 -- requeuing)
2013-10-15 01:12:40   Z-Wave Debug   . .  nodeAwake: stopping inhibit sleep timer
2013-10-15 01:12:42   Z-Wave Debug   RCVD goToSleep: 01 05 00 13 BE 01 56 (node NAK)
2013-10-15 01:12:42   Z-Wave Error   send "T12_Thermostat" goToSleep command failed (module might be asleep, or is unreachable)
2013-10-15 01:12:42   Z-Wave Debug   RCVD setHvacMode: 01 09 00 04 00 2E 03 40 03 01 9D
2013-10-15 01:12:42   Z-Wave Debug   . .  setHvacMode: node 046, endpoint None, value 1
2013-10-15 01:12:42   Z-Wave   received "T10_Thermostat" mode is heat
2013-10-15 01:12:42   Z-Wave Debug   RCVD setHvacMode: 01 09 00 04 00 2E 03 40 03 01 9D
2013-10-15 01:12:42   Z-Wave Debug   . .  setHvacMode: node 046, endpoint None, value 1
2013-10-15 01:12:42   Z-Wave   received "T10_Thermostat" mode is heat
2013-10-15 01:12:42   Z-Wave Debug   RCVD requestVarSensorStatus: 01 0C 00 04 00 2E 06 31 05 01 22 00 E6 2E
2013-10-15 01:12:42   Z-Wave Debug   . .  requestVarSensorStatus: node 046, endpoint None, type 1, raw value 2200...
2013-10-15 01:12:42   Z-Wave Debug   . .  requestVarSensorStatus: 23.0 °C (float: 23.000000)
2013-10-15 01:12:42   Z-Wave   received "T10_Thermostat" temperature update to 23.0 °C
2013-10-15 01:12:42   Z-Wave Debug   RCVD nodeAwake: 01 08 00 04 00 29 02 84 07 5B
2013-10-15 01:12:42   Z-Wave Debug   . .  nodeAwake: node 041
2013-10-15 01:12:42   Z-Wave Debug   SENT requestHvacMode: 01 09 00 13 29 02 40 02 05 BF 36
2013-10-15 01:12:42   Z-Wave Debug   RCVD requestHvacMode: 01 08 00 04 00 28 02 84 07 5A (unsolicited2 -- requeuing)
2013-10-15 01:12:42   Z-Wave Debug   RCVD requestHvacMode: 01 08 00 04 00 28 02 84 07 5A (unsolicited3 -- requeuing)
2013-10-15 01:12:51   Z-Wave Debug   RCVD requestHvacMode: 01 05 00 13 BF 01 57 (node NAK)
2013-10-15 01:12:51   Z-Wave Error   send "T03_Thermostat" mode status request failed
2013-10-15 01:12:51   Z-Wave Debug   SENT requestTempStatus: 01 09 00 13 29 02 31 04 05 C0 3E
2013-10-15 01:12:51   Z-Wave Debug   RCVD requestTempStatus: 01 08 00 04 00 28 02 84 07 5A (unsolicited2 -- requeuing)
2013-10-15 01:12:51   Z-Wave Debug   RCVD requestTempStatus: 01 08 00 04 00 28 02 84 07 5A (unsolicited3 -- requeuing)
2013-10-15 01:12:59   Z-Wave Debug   RCVD requestTempStatus: 01 05 00 13 C0 01 28 (node NAK)
2013-10-15 01:12:59   Z-Wave Error   send "T03_Thermostat" temperature status request failed
2013-10-15 01:12:59   Z-Wave Debug   SENT requestSetpointVal: 01 0A 00 13 29 03 43 02 01 05 C1 48
2013-10-15 01:12:59   Z-Wave Debug   RCVD requestSetpointVal: 01 08 00 04 00 28 02 84 07 5A (unsolicited2 -- requeuing)
2013-10-15 01:12:59   Z-Wave Debug   RCVD requestSetpointVal: 01 08 00 04 00 28 02 84 07 5A (unsolicited3 -- requeuing)
2013-10-15 01:13:00   Schedule   T00 Thermostat Check
2013-10-15 01:13:07   Z-Wave Debug   RCVD requestSetpointVal: 01 05 00 13 C1 01 29 (node NAK)
2013-10-15 01:13:07   Z-Wave Error   send "T03_Thermostat" heat setpoint status request failed
2013-10-15 01:13:07   Z-Wave Debug   . . . . . . . : skipping battery check (next check in 581 mins)
2013-10-15 01:13:07   Z-Wave Debug   SENT goToSleep: 01 09 00 13 29 02 84 08 05 C2 85
2013-10-15 01:13:07   Z-Wave Debug   RCVD goToSleep: 01 08 00 04 00 28 02 84 07 5A (unsolicited2 -- requeuing)
2013-10-15 01:13:07   Z-Wave Debug   RCVD goToSleep: 01 08 00 04 00 28 02 84 07 5A (unsolicited3 -- requeuing)
2013-10-15 01:13:17   Z-Wave Debug   RCVD goToSleep: 01 05 00 13 C2 01 2A (node NAK)
2013-10-15 01:13:17   Z-Wave Error   send "T03_Thermostat" goToSleep command failed (module might be asleep, or is unreachable)
2013-10-15 01:13:17   Z-Wave Debug   RCVD nodeAwake: 01 08 00 04 00 28 02 84 07 5A
2013-10-15 01:13:17   Z-Wave Debug   . .  nodeAwake: node 040
2013-10-15 01:13:17   Z-Wave Debug   SENT requestHvacMode: 01 09 00 13 28 02 40 02 05 C3 4B
2013-10-15 01:13:17   Z-Wave Debug   RCVD requestHvacMode: 01 05 00 13 C3 01 2B (node NAK)
2013-10-15 01:13:17   Z-Wave Error   send "T04_Thermostat" mode status request failed
2013-10-15 01:13:17   Z-Wave Debug   SENT requestTempStatus: 01 09 00 13 28 02 31 04 05 C4 3B
2013-10-15 01:13:17   Z-Wave Debug   RCVD requestTempStatus: 01 05 00 13 C4 01 2C (node NAK)
2013-10-15 01:13:17   Z-Wave Error   send "T04_Thermostat" temperature status request failed
2013-10-15 01:13:17   Z-Wave Debug   SENT requestSetpointVal: 01 0A 00 13 28 03 43 02 01 05 C5 4D
2013-10-15 01:13:17   Z-Wave Debug   RCVD requestSetpointVal: 01 05 00 13 C5 01 2D (node NAK)
2013-10-15 01:13:17   Z-Wave Error   send "T04_Thermostat" heat setpoint status request failed
2013-10-15 01:13:17   Z-Wave Debug   . . . . . . . : skipping battery check (next check in 581 mins)
2013-10-15 01:13:17   Z-Wave Debug   SENT goToSleep: 01 09 00 13 28 02 84 08 05 C6 80
2013-10-15 01:13:17   Z-Wave Debug   RCVD goToSleep: 01 05 00 13 C6 01 2E (node NAK)
2013-10-15 01:13:17   Z-Wave Error   send "T04_Thermostat" goToSleep command failed (module might be asleep, or is unreachable)
2013-10-15 01:13:17   Z-Wave Debug   SENT goToSleep: 01 09 00 13 2E 02 84 08 05 C7 87
2013-10-15 01:13:23   Z-Wave Debug   RCVD goToSleep: 01 05 00 13 C7 01 2F (node NAK)


Is there any low level debugging that can be done to see what is happening between Indigo and the Z-Stick?

Potential next step is to reset the Z-Stick but I want to avoid this if possible.

Posted on
Tue Oct 15, 2013 5:30 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: EUROtronic Stella-Z

It looks like Indigo might be getting into a bad state, possibly caused by multiple modules waking up around the same time. Can you copy/paste for me the log snippets showing the following time stamps (I need a bit earlier log history from your last snippet above:

2013-10-15 01:08:00 to 01:12:00

Is there any low level debugging that can be done to see what is happening between Indigo and the Z-Stick?

The logging you have above, with debug logging on, is low level enough. It includes just about all the bytes that are being passed in both directions from Indigo and the Z-Stick. I just need to analyze it some more to try to see what is going wrong.

I think that the errors you showed in the first 2 snippets:

Code: Select all
   ...
  File "actionthermostat.py", line 197, in _processHvacModeReply
  File "zwavetriggers.py", line 103, in executeTriggersFromParms
StandardError: ServerCommunicationError -- timeout waiting for response

are unrelated to the problem. It appears in this case Indigo is trying to execute a Z-Wave trigger action event you have defined but it is timing out. What type of Z-Wave trigger actions do you have defined for your thermostats? Are any of them AppleScript actions, or are they all the scripts python?

Image

Posted on
Wed Oct 16, 2013 7:09 am
autolog offline
Posts: 3988
Joined: Sep 10, 2013
Location: West Sussex, UK [GMT aka UTC]

Re: EUROtronic Stella-Z

matt (support) wrote:
It looks like Indigo might be getting into a bad state, possibly caused by multiple modules waking up around the same time. Can you copy/paste for me the log snippets showing the following time stamps (I need a bit earlier log history from your last snippet above:

2013-10-15 01:08:00 to 01:12:00

Is there any low level debugging that can be done to see what is happening between Indigo and the Z-Stick?

The logging you have above, with debug logging on, is low level enough. It includes just about all the bytes that are being passed in both directions from Indigo and the Z-Stick. I just need to analyze it some more to try to see what is going wrong.

Here is the log :) :

Code: Select all
2013-10-15 01:07:35   Z-Wave Debug   SENT goToSleep: 01 09 00 13 28 02 84 08 05 9B DD
2013-10-15 01:08:00   Schedule   T00 Thermostat Check
2013-10-15 01:08:39   Z-Wave Debug   RCVD nodeAwake: 01 08 00 04 00 1F 02 84 07 6D
2013-10-15 01:08:39   Z-Wave Debug   . .  nodeAwake: node 031
2013-10-15 01:08:39   Z-Wave Debug   SENT requestHvacMode: 01 09 00 13 1F 02 40 02 05 9C 23
2013-10-15 01:08:39   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 1
2013-10-15 01:08:39   Z-Wave   sent "T01_Thermostat" mode status request
2013-10-15 01:08:39   Z-Wave Debug   SENT requestTempStatus: 01 09 00 13 1F 02 31 04 05 9D 55
2013-10-15 01:08:39   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 1F 03 40 03 01 AC (unsolicited2 -- requeuing)
2013-10-15 01:08:39   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 1F 03 40 03 01 AC (unsolicited3 -- requeuing)
2013-10-15 01:08:39   Z-Wave Debug   RCVD requestTempStatus: 01 0C 00 04 00 1F 06 31 05 01 22 00 C3 3A (unsolicited3 -- requeuing)
2013-10-15 01:08:39   Z-Wave Debug   RCVD requestTempStatus: 01 0C 00 04 00 1F 06 31 05 01 22 00 C3 3A (unsolicited3 -- requeuing)
2013-10-15 01:08:40   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 2
2013-10-15 01:08:40   Z-Wave   sent "T01_Thermostat" temperature status request
2013-10-15 01:08:40   Z-Wave Debug   SENT requestSetpointVal: 01 0A 00 13 1F 03 43 02 01 05 9E 21
2013-10-15 01:08:40   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 1F 03 40 03 01 AC (unsolicited2 -- requeuing)
2013-10-15 01:08:40   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 1F 06 31 05 01 22 00 C3 3A (unsolicited2 -- requeuing)
2013-10-15 01:08:40   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 1F 06 31 05 01 22 00 C3 3A (unsolicited2 -- requeuing)
2013-10-15 01:08:40   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 1F 06 31 05 01 22 00 C3 3A (unsolicited2 -- requeuing)
2013-10-15 01:08:40   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 1F 03 40 03 01 AC (unsolicited3 -- requeuing)
2013-10-15 01:08:40   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 1F 06 31 05 01 22 00 C3 3A (unsolicited3 -- requeuing)
2013-10-15 01:08:40   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 1F 06 31 05 01 22 00 C3 3A (unsolicited3 -- requeuing)
2013-10-15 01:08:40   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 1F 06 31 05 01 22 00 C3 3A (unsolicited3 -- requeuing)
2013-10-15 01:08:40   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 3
2013-10-15 01:08:40   Z-Wave   sent "T01_Thermostat" heat setpoint status request
2013-10-15 01:08:40   Z-Wave Debug   . . . . . . . : skipping battery check (next check in 587 mins)
2013-10-15 01:08:40   Z-Wave Debug   . .  nodeAwake: started inhibit sleep timer
2013-10-15 01:08:40   Z-Wave Debug   RCVD setHvacMode: 01 09 00 04 00 1F 03 40 03 01 AC
2013-10-15 01:08:40   Z-Wave Debug   . .  setHvacMode: node 031, endpoint None, value 1
2013-10-15 01:08:40   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 2
2013-10-15 01:08:40   Z-Wave   received "T01_Thermostat" mode is heat
2013-10-15 01:08:40   Z-Wave Debug   RCVD requestVarSensorStatus: 01 0C 00 04 00 1F 06 31 05 01 22 00 C3 3A
2013-10-15 01:08:40   Z-Wave Debug   . .  requestVarSensorStatus: node 031, endpoint None, type 1, raw value 2200...
2013-10-15 01:08:40   Z-Wave Debug   . .  requestVarSensorStatus: 19.5 °C (float: 19.500000)
2013-10-15 01:08:40   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 1
2013-10-15 01:08:40   Z-Wave   received "T01_Thermostat" temperature update to 19.5 °C
2013-10-15 01:08:40   Z-Wave Debug   RCVD requestVarSensorStatus: 01 0C 00 04 00 1F 06 31 05 01 22 00 C3 3A
2013-10-15 01:08:40   Z-Wave Debug   . .  requestVarSensorStatus: node 031, endpoint None, type 1, raw value 2200...
2013-10-15 01:08:40   Z-Wave Debug   . .  requestVarSensorStatus: 19.5 °C (float: 19.500000)
2013-10-15 01:08:40   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 0
2013-10-15 01:08:40   Z-Wave Debug   . .  nodeAwake: stopping inhibit sleep timer
2013-10-15 01:08:40   Z-Wave   received "T01_Thermostat" temperature update to 19.5 °C
2013-10-15 01:08:40   Z-Wave Debug   RCVD requestVarSensorStatus: 01 0C 00 04 00 1F 06 31 05 01 22 00 C3 3A
2013-10-15 01:08:40   Z-Wave Debug   . .  requestVarSensorStatus: node 031, endpoint None, type 1, raw value 2200...
2013-10-15 01:08:40   Z-Wave Debug   . .  requestVarSensorStatus: 19.5 °C (float: 19.500000)
2013-10-15 01:08:40   Z-Wave   received "T01_Thermostat" temperature update to 19.5 °C
2013-10-15 01:08:40   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 1F 06 43 03 01 22 00 3C B1
2013-10-15 01:08:40   Z-Wave Debug   . .  requestSetpointVal: node 031, endpoint None, type 1, raw value 2200...
2013-10-15 01:08:40   Z-Wave Debug   . .  requestSetpointVal: 6.0 °C (float: 6.000000)
2013-10-15 01:08:40   Z-Wave   received "T01_Thermostat" heat setpoint is 6.0 °C
2013-10-15 01:08:40   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 1F 06 43 03 01 22 00 3C B1
2013-10-15 01:08:40   Z-Wave Debug   . .  requestSetpointVal: node 031, endpoint None, type 1, raw value 2200...
2013-10-15 01:08:40   Z-Wave Debug   . .  requestSetpointVal: 6.0 °C (float: 6.000000)
2013-10-15 01:08:40   Z-Wave   received "T01_Thermostat" heat setpoint is 6.0 °C
2013-10-15 01:08:40   Z-Wave Debug   SENT goToSleep: 01 09 00 13 1F 02 84 08 05 9F EE
2013-10-15 01:08:48   Z-Wave Debug   RCVD goToSleep: 01 05 00 13 9F 01 77 (node NAK)
2013-10-15 01:08:57   Z-Wave Debug   RCVD nodeAwake: 01 08 00 04 00 31 02 84 07 43
2013-10-15 01:08:57   Z-Wave Debug   . .  nodeAwake: node 049
2013-10-15 01:08:57   Z-Wave Debug   SENT requestHvacMode: 01 09 00 13 31 02 40 02 05 A0 31
2013-10-15 01:08:57   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 1
2013-10-15 01:08:57   Z-Wave   sent "T06_Thermostat" mode status request
2013-10-15 01:08:57   Z-Wave Debug   SENT requestTempStatus: 01 09 00 13 31 02 31 04 05 A1 47
2013-10-15 01:08:57   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 31 03 40 03 01 82 (unsolicited2 -- requeuing)
2013-10-15 01:08:57   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 31 03 40 03 01 82 (unsolicited3 -- requeuing)
2013-10-15 01:08:57   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 2
2013-10-15 01:08:57   Z-Wave   sent "T06_Thermostat" temperature status request
2013-10-15 01:08:57   Z-Wave Debug   SENT requestSetpointVal: 01 0A 00 13 31 03 43 02 01 05 A2 33
2013-10-15 01:08:57   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 31 03 40 03 01 82 (unsolicited2 -- requeuing)
2013-10-15 01:08:57   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 31 06 31 05 01 22 00 AA 7D (unsolicited2 -- requeuing)
2013-10-15 01:08:57   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 31 03 40 03 01 82 (unsolicited3 -- requeuing)
2013-10-15 01:08:57   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 31 06 31 05 01 22 00 AA 7D (unsolicited3 -- requeuing)
2013-10-15 01:08:57   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 3
2013-10-15 01:08:57   Z-Wave   sent "T06_Thermostat" heat setpoint status request
2013-10-15 01:08:57   Z-Wave Debug   . . . . . . . : skipping battery check (next check in 587 mins)
2013-10-15 01:08:57   Z-Wave Debug   . .  nodeAwake: started inhibit sleep timer
2013-10-15 01:08:57   Z-Wave Debug   RCVD setHvacMode: 01 09 00 04 00 31 03 40 03 01 82
2013-10-15 01:08:57   Z-Wave Debug   . .  setHvacMode: node 049, endpoint None, value 1
2013-10-15 01:08:57   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 2
2013-10-15 01:08:57   Z-Wave   received "T06_Thermostat" mode is heat
2013-10-15 01:08:57   Z-Wave Debug   RCVD requestVarSensorStatus: 01 0C 00 04 00 31 06 31 05 01 22 00 AA 7D
2013-10-15 01:08:57   Z-Wave Debug   . .  requestVarSensorStatus: node 049, endpoint None, type 1, raw value 2200...
2013-10-15 01:08:57   Z-Wave Debug   . .  requestVarSensorStatus: 17.0 °C (float: 17.000000)
2013-10-15 01:08:57   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 1
2013-10-15 01:08:57   Z-Wave   received "T06_Thermostat" temperature update to 17.0 °C
2013-10-15 01:08:57   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 31 06 43 03 01 22 00 3C 9F
2013-10-15 01:08:57   Z-Wave Debug   . .  requestSetpointVal: node 049, endpoint None, type 1, raw value 2200...
2013-10-15 01:08:57   Z-Wave Debug   . .  requestSetpointVal: 6.0 °C (float: 6.000000)
2013-10-15 01:08:57   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 0
2013-10-15 01:08:57   Z-Wave Debug   . .  nodeAwake: stopping inhibit sleep timer
2013-10-15 01:08:57   Z-Wave   received "T06_Thermostat" heat setpoint is 6.0 °C
2013-10-15 01:08:57   Z-Wave Debug   SENT goToSleep: 01 09 00 13 31 02 84 08 05 A3 FC
2013-10-15 01:09:00   Schedule   T00 Thermostat Check
2013-10-15 01:09:02   Z-Wave Debug   RCVD nodeAwake: 01 08 00 04 00 22 02 84 07 50
2013-10-15 01:09:02   Z-Wave Debug   . .  nodeAwake: node 034
2013-10-15 01:09:02   Z-Wave Debug   SENT requestHvacMode: 01 09 00 13 22 02 40 02 05 A4 26
2013-10-15 01:09:02   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 1
2013-10-15 01:09:02   Z-Wave   sent "T09_Thermostat" mode status request
2013-10-15 01:09:02   Z-Wave Debug   SENT requestTempStatus: 01 09 00 13 22 02 31 04 05 A5 50
2013-10-15 01:09:02   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 22 03 40 03 01 91 (unsolicited2 -- requeuing)
2013-10-15 01:09:02   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 22 03 40 03 01 91 (unsolicited3 -- requeuing)
2013-10-15 01:09:02   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 2
2013-10-15 01:09:02   Z-Wave   sent "T09_Thermostat" temperature status request
2013-10-15 01:09:02   Z-Wave Debug   SENT requestSetpointVal: 01 0A 00 13 22 03 43 02 01 05 A6 24
2013-10-15 01:09:02   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 22 03 40 03 01 91 (unsolicited2 -- requeuing)
2013-10-15 01:09:02   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 22 06 31 05 01 22 00 CD 09 (unsolicited2 -- requeuing)
2013-10-15 01:09:02   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 22 03 40 03 01 91 (unsolicited3 -- requeuing)
2013-10-15 01:09:02   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 22 06 31 05 01 22 00 CD 09 (unsolicited3 -- requeuing)
2013-10-15 01:09:02   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 3
2013-10-15 01:09:02   Z-Wave   sent "T09_Thermostat" heat setpoint status request
2013-10-15 01:09:02   Z-Wave Debug   . . . . . . . : skipping battery check (next check in 587 mins)
2013-10-15 01:09:02   Z-Wave Debug   . .  nodeAwake: started inhibit sleep timer
2013-10-15 01:09:02   Z-Wave Debug   RCVD setHvacMode: 01 09 00 04 00 22 03 40 03 01 91
2013-10-15 01:09:02   Z-Wave Debug   . .  setHvacMode: node 034, endpoint None, value 1
2013-10-15 01:09:02   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 2
2013-10-15 01:09:02   Z-Wave   received "T09_Thermostat" mode is heat
2013-10-15 01:09:02   Z-Wave Debug   RCVD requestVarSensorStatus: 01 0C 00 04 00 22 06 31 05 01 22 00 CD 09
2013-10-15 01:09:02   Z-Wave Debug   . .  requestVarSensorStatus: node 034, endpoint None, type 1, raw value 2200...
2013-10-15 01:09:02   Z-Wave Debug   . .  requestVarSensorStatus: 20.5 °C (float: 20.500000)
2013-10-15 01:09:02   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 1
2013-10-15 01:09:02   Z-Wave   received "T09_Thermostat" temperature update to 20.5 °C
2013-10-15 01:09:02   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 22 06 43 03 01 22 00 3C 8C
2013-10-15 01:09:02   Z-Wave Debug   . .  requestSetpointVal: node 034, endpoint None, type 1, raw value 2200...
2013-10-15 01:09:02   Z-Wave Debug   . .  requestSetpointVal: 6.0 °C (float: 6.000000)
2013-10-15 01:09:02   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 0
2013-10-15 01:09:02   Z-Wave Debug   . .  nodeAwake: stopping inhibit sleep timer
2013-10-15 01:09:02   Z-Wave   received "T09_Thermostat" heat setpoint is 6.0 °C
2013-10-15 01:09:02   Z-Wave Debug   SENT goToSleep: 01 09 00 13 22 02 84 08 05 A7 EB
2013-10-15 01:10:00   Schedule   T00 Thermostat Check
2013-10-15 01:10:10   Z-Wave Debug   RCVD nodeAwake: 01 08 00 04 00 21 02 84 07 53
2013-10-15 01:10:10   Z-Wave Debug   . .  nodeAwake: node 033
2013-10-15 01:10:10   Z-Wave Debug   SENT requestHvacMode: 01 09 00 13 21 02 40 02 05 A8 29
2013-10-15 01:10:10   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 1
2013-10-15 01:10:10   Z-Wave   sent "T02_Thermostat" mode status request
2013-10-15 01:10:10   Z-Wave Debug   SENT requestTempStatus: 01 09 00 13 21 02 31 04 05 A9 5F
2013-10-15 01:10:10   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 21 03 40 03 01 92 (unsolicited2 -- requeuing)
2013-10-15 01:10:10   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 21 03 40 03 01 92 (unsolicited3 -- requeuing)
2013-10-15 01:10:10   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 2
2013-10-15 01:10:10   Z-Wave   sent "T02_Thermostat" temperature status request
2013-10-15 01:10:10   Z-Wave Debug   SENT requestSetpointVal: 01 0A 00 13 21 03 43 02 01 05 AA 2B
2013-10-15 01:10:10   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 21 03 40 03 01 92 (unsolicited2 -- requeuing)
2013-10-15 01:10:10   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 21 06 31 05 01 22 00 C3 04 (unsolicited2 -- requeuing)
2013-10-15 01:10:10   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 21 03 40 03 01 92 (unsolicited3 -- requeuing)
2013-10-15 01:10:10   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 21 06 31 05 01 22 00 C3 04 (unsolicited3 -- requeuing)
2013-10-15 01:10:11   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 3
2013-10-15 01:10:11   Z-Wave   sent "T02_Thermostat" heat setpoint status request
2013-10-15 01:10:11   Z-Wave Debug   . . . . . . . : skipping battery check (next check in 587 mins)
2013-10-15 01:10:11   Z-Wave Debug   . .  nodeAwake: started inhibit sleep timer
2013-10-15 01:10:11   Z-Wave Debug   RCVD setHvacMode: 01 09 00 04 00 21 03 40 03 01 92
2013-10-15 01:10:11   Z-Wave Debug   . .  setHvacMode: node 033, endpoint None, value 1
2013-10-15 01:10:11   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 2
2013-10-15 01:10:11   Z-Wave   received "T02_Thermostat" mode is heat
2013-10-15 01:10:11   Z-Wave Debug   RCVD requestVarSensorStatus: 01 0C 00 04 00 21 06 31 05 01 22 00 C3 04
2013-10-15 01:10:11   Z-Wave Debug   . .  requestVarSensorStatus: node 033, endpoint None, type 1, raw value 2200...
2013-10-15 01:10:11   Z-Wave Debug   . .  requestVarSensorStatus: 19.5 °C (float: 19.500000)
2013-10-15 01:10:11   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 1
2013-10-15 01:10:11   Z-Wave   received "T02_Thermostat" temperature update to 19.5 °C
2013-10-15 01:10:11   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 21 06 43 03 01 22 00 3C 8F
2013-10-15 01:10:11   Z-Wave Debug   . .  requestSetpointVal: node 033, endpoint None, type 1, raw value 2200...
2013-10-15 01:10:11   Z-Wave Debug   . .  requestSetpointVal: 6.0 °C (float: 6.000000)
2013-10-15 01:10:11   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 0
2013-10-15 01:10:11   Z-Wave Debug   . .  nodeAwake: stopping inhibit sleep timer
2013-10-15 01:10:11   Z-Wave   received "T02_Thermostat" heat setpoint is 6.0 °C
2013-10-15 01:10:11   Z-Wave Debug   SENT goToSleep: 01 09 00 13 21 02 84 08 05 AB E4
2013-10-15 01:10:20   Z-Wave Debug   RCVD nodeAwake: 01 08 00 04 00 24 02 84 07 56
2013-10-15 01:10:20   Z-Wave Debug   . .  nodeAwake: node 036
2013-10-15 01:10:20   Z-Wave Debug   SENT requestHvacMode: 01 09 00 13 24 02 40 02 05 AC 28
2013-10-15 01:10:20   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 1
2013-10-15 01:10:20   Z-Wave   sent "T08_Thermostat" mode status request
2013-10-15 01:10:20   Z-Wave Debug   SENT requestTempStatus: 01 09 00 13 24 02 31 04 05 AD 5E
2013-10-15 01:10:20   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 24 03 40 03 01 97 (unsolicited2 -- requeuing)
2013-10-15 01:10:20   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 24 03 40 03 01 97 (unsolicited3 -- requeuing)
2013-10-15 01:10:20   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 2
2013-10-15 01:10:20   Z-Wave   sent "T08_Thermostat" temperature status request
2013-10-15 01:10:20   Z-Wave Debug   SENT requestSetpointVal: 01 0A 00 13 24 03 43 02 01 05 AE 2A
2013-10-15 01:10:20   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 24 03 40 03 01 97 (unsolicited2 -- requeuing)
2013-10-15 01:10:20   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 24 06 31 05 01 22 00 C3 01 (unsolicited2 -- requeuing)
2013-10-15 01:10:20   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 24 03 40 03 01 97 (unsolicited3 -- requeuing)
2013-10-15 01:10:20   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 24 06 31 05 01 22 00 C3 01 (unsolicited3 -- requeuing)
2013-10-15 01:10:20   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 3
2013-10-15 01:10:20   Z-Wave   sent "T08_Thermostat" heat setpoint status request
2013-10-15 01:10:20   Z-Wave Debug   . . . . . . . : skipping battery check (next check in 587 mins)
2013-10-15 01:10:20   Z-Wave Debug   . .  nodeAwake: started inhibit sleep timer
2013-10-15 01:10:20   Z-Wave Debug   RCVD setHvacMode: 01 09 00 04 00 24 03 40 03 01 97
2013-10-15 01:10:20   Z-Wave Debug   . .  setHvacMode: node 036, endpoint None, value 1
2013-10-15 01:10:20   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 2
2013-10-15 01:10:20   Z-Wave   received "T08_Thermostat" mode is heat
2013-10-15 01:10:20   Z-Wave Debug   RCVD requestVarSensorStatus: 01 0C 00 04 00 24 06 31 05 01 22 00 C3 01
2013-10-15 01:10:20   Z-Wave Debug   . .  requestVarSensorStatus: node 036, endpoint None, type 1, raw value 2200...
2013-10-15 01:10:20   Z-Wave Debug   . .  requestVarSensorStatus: 19.5 °C (float: 19.500000)
2013-10-15 01:10:20   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 1
2013-10-15 01:10:20   Z-Wave   received "T08_Thermostat" temperature update to 19.5 °C
2013-10-15 01:10:20   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 24 06 43 03 01 22 00 3C 8A
2013-10-15 01:10:20   Z-Wave Debug   . .  requestSetpointVal: node 036, endpoint None, type 1, raw value 2200...
2013-10-15 01:10:20   Z-Wave Debug   . .  requestSetpointVal: 6.0 °C (float: 6.000000)
2013-10-15 01:10:20   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 0
2013-10-15 01:10:20   Z-Wave Debug   . .  nodeAwake: stopping inhibit sleep timer
2013-10-15 01:10:20   Z-Wave   received "T08_Thermostat" heat setpoint is 6.0 °C
2013-10-15 01:10:20   Z-Wave Debug   SENT goToSleep: 01 09 00 13 24 02 84 08 05 AF E5
2013-10-15 01:11:00   Schedule   T00 Thermostat Check
2013-10-15 01:11:36   Z-Wave Debug   RCVD nodeAwake: 01 08 00 04 00 26 02 84 07 54
2013-10-15 01:11:36   Z-Wave Debug   . .  nodeAwake: node 038
2013-10-15 01:11:36   Z-Wave Debug   SENT requestHvacMode: 01 09 00 13 26 02 40 02 05 B0 36
2013-10-15 01:11:36   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 1
2013-10-15 01:11:36   Z-Wave   sent "T07_Thermostat" mode status request
2013-10-15 01:11:36   Z-Wave Debug   SENT requestTempStatus: 01 09 00 13 26 02 31 04 05 B1 40
2013-10-15 01:11:36   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 26 03 40 03 01 95 (unsolicited2 -- requeuing)
2013-10-15 01:11:36   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 26 03 40 03 01 95 (unsolicited3 -- requeuing)
2013-10-15 01:11:36   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 2
2013-10-15 01:11:36   Z-Wave   sent "T07_Thermostat" temperature status request
2013-10-15 01:11:36   Z-Wave Debug   SENT requestSetpointVal: 01 0A 00 13 26 03 43 02 01 05 B2 34
2013-10-15 01:11:36   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 26 03 40 03 01 95 (unsolicited2 -- requeuing)
2013-10-15 01:11:36   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 26 06 31 05 01 22 00 D7 17 (unsolicited2 -- requeuing)
2013-10-15 01:11:36   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 26 03 40 03 01 95 (unsolicited3 -- requeuing)
2013-10-15 01:11:36   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 26 06 31 05 01 22 00 D7 17 (unsolicited3 -- requeuing)
2013-10-15 01:11:36   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 3
2013-10-15 01:11:36   Z-Wave   sent "T07_Thermostat" heat setpoint status request
2013-10-15 01:11:36   Z-Wave Debug   . . . . . . . : skipping battery check (next check in 587 mins)
2013-10-15 01:11:36   Z-Wave Debug   . .  nodeAwake: started inhibit sleep timer
2013-10-15 01:11:36   Z-Wave Debug   RCVD setHvacMode: 01 09 00 04 00 26 03 40 03 01 95
2013-10-15 01:11:36   Z-Wave Debug   . .  setHvacMode: node 038, endpoint None, value 1
2013-10-15 01:11:36   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 2
2013-10-15 01:11:36   Z-Wave   received "T07_Thermostat" mode is heat
2013-10-15 01:11:36   Z-Wave Debug   RCVD requestVarSensorStatus: 01 0C 00 04 00 26 06 31 05 01 22 00 D7 17
2013-10-15 01:11:36   Z-Wave Debug   . .  requestVarSensorStatus: node 038, endpoint None, type 1, raw value 2200...
2013-10-15 01:11:36   Z-Wave Debug   . .  requestVarSensorStatus: 21.5 °C (float: 21.500000)
2013-10-15 01:11:36   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 1
2013-10-15 01:11:36   Z-Wave   received "T07_Thermostat" temperature update to 21.5 °C
2013-10-15 01:11:36   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 26 06 43 03 01 22 00 3C 88
2013-10-15 01:11:36   Z-Wave Debug   . .  requestSetpointVal: node 038, endpoint None, type 1, raw value 2200...
2013-10-15 01:11:36   Z-Wave Debug   . .  requestSetpointVal: 6.0 °C (float: 6.000000)
2013-10-15 01:11:36   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 0
2013-10-15 01:11:36   Z-Wave Debug   . .  nodeAwake: stopping inhibit sleep timer
2013-10-15 01:11:36   Z-Wave   received "T07_Thermostat" heat setpoint is 6.0 °C
2013-10-15 01:11:36   Z-Wave Debug   SENT goToSleep: 01 09 00 13 26 02 84 08 05 B3 FB
2013-10-15 01:11:40   Z-Wave Debug   RCVD nodeAwake: 01 08 00 04 00 23 02 84 07 51
2013-10-15 01:11:40   Z-Wave Debug   . .  nodeAwake: node 035
2013-10-15 01:11:40   Z-Wave Debug   SENT requestHvacMode: 01 09 00 13 23 02 40 02 05 B4 37
2013-10-15 01:11:40   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 1
2013-10-15 01:11:40   Z-Wave   sent "T05_Thermostat" mode status request
2013-10-15 01:11:40   Z-Wave Debug   SENT requestTempStatus: 01 09 00 13 23 02 31 04 05 B5 41
2013-10-15 01:11:40   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 23 03 40 03 01 90 (unsolicited2 -- requeuing)
2013-10-15 01:11:40   Z-Wave Debug   RCVD requestTempStatus: 01 09 00 04 00 23 03 40 03 01 90 (unsolicited3 -- requeuing)
2013-10-15 01:11:41   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 2
2013-10-15 01:11:41   Z-Wave   sent "T05_Thermostat" temperature status request
2013-10-15 01:11:41   Z-Wave Debug   SENT requestSetpointVal: 01 0A 00 13 23 03 43 02 01 05 B6 35
2013-10-15 01:11:41   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 23 03 40 03 01 90 (unsolicited2 -- requeuing)
2013-10-15 01:11:41   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 23 06 31 05 01 22 00 BE 7B (unsolicited2 -- requeuing)
2013-10-15 01:11:41   Z-Wave Debug   RCVD requestSetpointVal: 01 09 00 04 00 23 03 40 03 01 90 (unsolicited3 -- requeuing)
2013-10-15 01:11:41   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 23 06 31 05 01 22 00 BE 7B (unsolicited3 -- requeuing)
2013-10-15 01:11:41   Z-Wave Debug   . .  nodeAwake: inhibit count++ to 3
2013-10-15 01:11:41   Z-Wave   sent "T05_Thermostat" heat setpoint status request
2013-10-15 01:11:41   Z-Wave Debug   . . . . . . . : skipping battery check (next check in 587 mins)
2013-10-15 01:11:41   Z-Wave Debug   . .  nodeAwake: started inhibit sleep timer
2013-10-15 01:11:41   Z-Wave Debug   RCVD setHvacMode: 01 09 00 04 00 23 03 40 03 01 90
2013-10-15 01:11:41   Z-Wave Debug   . .  setHvacMode: node 035, endpoint None, value 1
2013-10-15 01:11:41   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 2
2013-10-15 01:11:41   Z-Wave   received "T05_Thermostat" mode is heat
2013-10-15 01:11:41   Z-Wave Debug   RCVD requestVarSensorStatus: 01 0C 00 04 00 23 06 31 05 01 22 00 BE 7B
2013-10-15 01:11:41   Z-Wave Debug   . .  requestVarSensorStatus: node 035, endpoint None, type 1, raw value 2200...
2013-10-15 01:11:41   Z-Wave Debug   . .  requestVarSensorStatus: 19.0 °C (float: 19.000000)
2013-10-15 01:11:41   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 1
2013-10-15 01:11:41   Z-Wave   received "T05_Thermostat" temperature update to 19.0 °C
2013-10-15 01:11:41   Z-Wave Debug   RCVD requestSetpointVal: 01 0C 00 04 00 23 06 43 03 01 22 00 3C 8D
2013-10-15 01:11:41   Z-Wave Debug   . .  requestSetpointVal: node 035, endpoint None, type 1, raw value 2200...
2013-10-15 01:11:41   Z-Wave Debug   . .  requestSetpointVal: 6.0 °C (float: 6.000000)
2013-10-15 01:11:41   Z-Wave Debug   . .  nodeAwake: inhibit count-- to 0
2013-10-15 01:11:41   Z-Wave Debug   . .  nodeAwake: stopping inhibit sleep timer
2013-10-15 01:11:41   Z-Wave   received "T05_Thermostat" heat setpoint is 6.0 °C
2013-10-15 01:11:41   Z-Wave Debug   SENT goToSleep: 01 09 00 13 23 02 84 08 05 B7 FA
2013-10-15 01:12:00   Schedule   T00 Thermostat Check


matt (support) wrote:
I think that the errors you showed in the first 2 snippets:

Code: Select all
   ...
  File "actionthermostat.py", line 197, in _processHvacModeReply
  File "zwavetriggers.py", line 103, in executeTriggersFromParms
StandardError: ServerCommunicationError -- timeout waiting for response

are unrelated to the problem. It appears in this case Indigo is trying to execute a Z-Wave trigger action event you have defined but it is timing out. What type of Z-Wave trigger actions do you have defined for your thermostats? Are any of them AppleScript actions, or are they all the scripts python?


It is a python script executed when a Main Mode Update z-wave command is received - it invokes my shared script from python's site-packages folder , e.g.:
Code: Select all
import autolog
autolog.processThermostat("09","zwave")

It is quite a large script (700+ lines) but should execute quickly. If it helps, I can zip and email a copy of the full log, my database and the script (which is still under development and not yet suitable for publication :wink: ). btw, I am coming to the conclusion that the script needs to be moved into a plugin sooner rather than later. :)

Who is online

Users browsing this forum: No registered users and 2 guests

cron