Indigo Domotics

I've submitted a report from the latest version of indigo for the above. The model numbers are FGT-001 for the TRV and FGBRS-001 for the external sensor.

Thanks – added to our list to look at adding to the next feature release.

pnm wrote:

I've submitted a report from the latest version of indigo for the above. The model numbers are FGT-001 for the TRV and FGBRS-001 for the external sensor.

Interested to hear what you think of them, still looking for something more reliable than the Sprint ones.

siclark wrote:

Interested to hear what you think of them, still looking for something more reliable than the Sprint ones.

I have ditched all my Eurotronic Spirits and replaced them with Shelly TRVs.

The Spirits were causing too many problems with my Z-Wave network by causing delays which meant sensors often didn't repond straight away to turn lights on etc. The Shelly TRVs are an order of magnitude better. They have a 6500 mAh internal rechargeable battery via USB-C. They respond more or less imstantly and are highly controllable. It is easy to link them to an external sensor (link via MQTT). They offer target (temperature setpoint) and valve % control.

Amazing. Yes thatsynproblem too. Glad I asked. Off to buy some now!
Do I still use with your plugin?

siclark wrote:

... Do I still use with your plugin?

No (well not at the moment). I looked at supporting it but it would take a lot of effort to integrate it and it would make the plugin a bit messy. It would be better to have a specific new plugin to support these TRVs, I think?

In the meanwhile I am controlling these TRVs using Node Red 3 and MQTT via a Node Red dashboard which seems to work well.

I have also purchased some Shelly PLus H&T e-ink Temperature and Humidity sensors. Both the TRVs and the H&Ts can )an do in my case) communicate via MQTT.

autolog wrote:

In the meanwhile I am controlling these TRVs using Node Red 3 and MQTT via a Node Red dashboard which seems to work well.

I have also purchased some Shelly PLus H&T e-ink Temperature and Humidity sensors. Both the TRVs and the H&Ts can )an do in my case) communicate via MQTT.

After I get back from Oz in the New Year I will be looking at upgrading the Evohome TRV's, it seems that theEvohome plugin is not going to be updated to python 3 so that would stop me updating to the next Indigo upgrade and also I am sick of them not being able to update because the EU Evohome server is down, local control would be bliss!

Now you have played with them a bit what is your opinion, I used to like Shelly but 2 motion sensors died, never got on with the contact sensors and a UNI also died. Just wondering if the Gen 2 range is better.

autolog wrote:

siclark wrote:

... Do I still use with your plugin?

No (well not at the moment). I looked at supporting it but it would take a lot of effort to integrate it and it would make the plugin a bit messy. It would be better to have a specific new plugin to support these TRVs, I think?

In the meanwhile I am controlling these TRVs using Node Red 3 and MQTT via a Node Red dashboard which seems to work well.

I have also purchased some Shelly PLus H&T e-ink Temperature and Humidity sensors. Both the TRVs and the H&Ts can )an do in my case) communicate via MQTT.

Thanks. I would have to think how to control the Heatmiser thermostats that drive the boiler and zone valves and ideally have it connected in homekit so my wife can control the heating in single app rather than having to use several.

CliveS wrote:

... Now you have played with them a bit what is your opinion, I used to like Shelly but 2 motion sensors died, never got on with the contact sensors and a UNI also died. Just wondering if the Gen 2 range is better.

I can't really comment on the longevity as I haven't had them that long. I do like the web interface to control all the settings and like the fact that it is easy to link to MQTT. They also work with web sockets. I also like their responsiveness.

Probably tempting fate but at the moment they are working well. I would find it difficult to see how they could be improved software wise. I like that the battery is 6500 mAh and rechargeable via USB-C; so one could use a battery pack to recharge it and just plug it in without removing the TRV.

I might take the rose tinted spectacles off at some point; we'll see.

Jon how do you trigger the boiler when you use these? Do you set up triggers in Indigo to do what your plugin did automatically? I presume there is something obvious reported over MQTT from the TRV that indicates that the valve is open or its calling for heat?
My setup currently is 7 Spirit TRVs that rely on 3 different zone valves (controlled by Heatmiser thermostats via that plugin) to provide hot water to them.

@matt wondering if this warrants moving into a different thread as rather side tracking the Fibaro topic?

Hello,

Just bought a Fibaro Heat controller without checking if it was supported.
I see that it is on the list to be added.
Sadly it was not added on the latest release.
What would be the best way to use it while we wait for support?

Thanks

Gilles

How specifically is it not working?

What specific model ID/name is it?

And can you re-sync it and copy/paste the Event Log window results so we can see how specifically it is identifying itself?

Hi Matt,
Sorry for the late reply.
Most of te time the Heat controller won't react to the commands like raising or lowering the temp., or changing the mode.
The thermostat control also has fan controls which do not exist for a radiator.
The multilevel sensor also has no information which I guess is the external temp. sensor.

Thank you for your time.

Gilles

Log:
Z-Wave Debug intiatingSyncUI (timeout in 1500 seconds)
Z-Wave Syncing - started for "052 - Thermostat Living"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 39 01 01 40
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 08 21 04 85 04 40 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 32 (no inbound callback)
Z-Wave Debug . . getNodeNeighbors: nodeId 057, neighbors: 4, 9, 14, 19, 25, 27, 32, 35, 47, 56
Z-Wave Syncing - retrieved module neighbors list: 4, 9, 14, 19, 25, 27, 32, 35, 47, 56
Z-Wave Syncing - assigning return route to "057 - 052 - Thermostat Living"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 39 01 84
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD (no inbound callback)
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 057, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 39 24 96 12
Z-Wave Debug RCVD nodeInfoFrame: 01 22 00 49 84 39 1C 04 08 06 5E 86 8E 31 40 43 53 98 9F 55 56 59 5A 60 6C 71 72 75 80 70 81 7A 73 22 85 AA
Z-Wave Debug . . nodeInfoFrame: node 057, combined class list: 20v1 40v1 43v1 72v1 86v1 5Ev1 8Ev1 31v1 53v1 98v1 9Fv1 55v1 56v1 59v1 5Av1 60v1 6Cv1 71v1 75v1 80v1 70v1 81v1 7Av1 73v1 22v1 85v1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 39 02 72 04 25 97 1A
Z-Wave Debug RCVD requestManufactureInfo: 01 07 00 13 97 00 00 02 7E (node ACK)
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 39 08 72 05 01 0F 13 01 10 01 BE
Z-Wave Debug . . requestManufactureInfo: node 057, manufacturerId 010F, productId 13011001
Z-Wave Debug . . requestManufactureInfo: Fibaro System, General Thermostat (v2)
Z-Wave Syncing - retrieved manufacture and model names: Fibaro System - 010F, General Thermostat (v2) - 13011001
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 39 02 86 11 25 98 F4
Z-Wave Debug RCVD requestVersInfoGen: 01 07 00 13 98 00 00 02 71 (node ACK)
Z-Wave Debug RCVD requestVersInfoGen: 01 11 00 04 00 39 0B 86 12 03 04 3D 04 07 01 01 02 0A 7D
Z-Wave Debug . . requestVersInfoGen: node 057, protoVers 4.61, appVers 4.07
Z-Wave Syncing - retrieved protocol version 4.61, app version 4.07
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 39 03 86 13 31 25 99 C4
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 07 00 13 99 00 00 03 71 (node ACK)
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 39 04 86 14 31 05 6A
Z-Wave Debug . . requestVersInfoCmdClass: node 057, class command 31 using version 5
Z-Wave Debug . . requestVersInfoCmdClass: node 057, combined class list: 20v1 40v1 43v1 72v1 86v1 5Ev1 8Ev1 31v5 53v1 98v1 9Fv1 55v1 56v1 59v1 5Av1 60v1 6Cv1 71v1 75v1 80v1 70v1 81v1 7Av1 73v1 22v1 85v1
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 39 03 86 13 60 25 9A 96
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 07 00 13 9A 00 00 03 72 (node ACK)
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 39 04 86 14 60 04 3A
Z-Wave Debug . . requestVersInfoCmdClass: node 057, class command 60 using version 4
Z-Wave Debug . . requestVersInfoCmdClass: node 057, combined class list: 20v1 40v1 43v1 72v1 86v1 5Ev1 8Ev1 31v5 53v1 98v1 9Fv1 55v1 56v1 59v1 5Av1 60v4 6Cv1 71v1 75v1 80v1 70v1 81v1 7Av1 73v1 22v1 85v1
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 72v1 86v1 5Ev1 8Ev1 31v5 53v1 98v1 9Fv1 55v1 56v1 59v1 5Av1 60v4 6Cv1 71v1 75v1 80v1 70v1 81v1 7Av1 73v1 22v1 85v1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, battery, beaming, security, frequentWaking
Z-Wave Debug SENT requestMultiEndPointInfo: 01 09 00 13 39 02 60 07 25 9B 07
Z-Wave Debug RCVD requestMultiEndPointInfo: 01 07 00 13 9B 00 00 03 73 (node ACK)
Z-Wave Debug RCVD requestMultiEndPointInfo: 01 0B 00 04 00 39 05 60 08 00 02 00 A6
Z-Wave Debug . . requestMultiEndPointInfo: node 057, numEndPoints 2, sameClass False, notStatic False
Z-Wave Debug SENT requestMultiEndPointDetails: 01 0A 00 13 39 03 60 09 01 25 9C 0D
Z-Wave Debug RCVD requestMultiEndPointDetails: 01 07 00 13 9C 00 00 03 74 (node ACK)
Z-Wave Debug RCVD requestMultiEndPointDetails: 01 1A 00 04 00 39 14 60 0A 01 08 06 5E 8E 40 43 53 98 9F 59 6C 71 75 80 81 85 22 B9
Z-Wave Debug . . requestMultiEndPointDetails: node 057, endPoint 1, notStatic False, class hierarchy 08 : 06
Z-Wave Debug . . requestMultiEndPointDetails: node 057, combined multi-endpoint types: 1:(08 : 06)
Z-Wave Debug . . requestMultiEndPointDetails: node 057, combined multi-endpoint classes: 1:[5E 8E 40 43 53 98 9F 59 6C 71 75 80 81 85 22]
Z-Wave Debug SENT requestMultiEndPointDetails: 01 0A 00 13 39 03 60 09 02 25 9D 0F
Z-Wave Debug RCVD requestMultiEndPointDetails: 01 07 00 13 9D 00 00 02 74 (node ACK)
Z-Wave Debug RCVD requestMultiEndPointDetails: 01 16 00 04 00 39 10 60 0A 02 21 01 5E 8E 31 98 9F 59 6C 71 80 85 22 09
Z-Wave Debug . . requestMultiEndPointDetails: node 057, endPoint 2, notStatic False, class hierarchy 21 : 01
Z-Wave Debug . . requestMultiEndPointDetails: node 057, combined multi-endpoint types: 1:(08 : 06), 2:(21 : 01)
Z-Wave Debug . . requestMultiEndPointDetails: node 057, combined multi-endpoint classes: 1:[5E 8E 40 43 53 98 9F 59 6C 71 75 80 81 85 22], 2:[5E 8E 31 98 9F 59 6C 71 80 85 22]
Z-Wave Syncing - retrieved multi-endpoint types: 1:(08 : 06), 2:(21 : 01)
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[5E 8E 40 43 53 98 9F 59 6C 71 75 80 81 85 22], 2:[5E 8E 31 98 9F 59 6C 71 80 85 22]
Z-Wave Debug SENT requestAssociationGroupCount: 01 09 00 13 39 02 85 05 25 9E E5
Z-Wave Debug RCVD requestAssociationGroupCount: 01 07 00 13 9E 00 00 03 76 (node ACK)
Z-Wave Debug RCVD requestAssociationGroupCount: 01 09 00 04 00 39 03 85 06 01 4A
Z-Wave Debug . . requestAssociationGroupCount: node 057, group count: 1
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 39 03 85 02 01 25 9F E0
Z-Wave Debug RCVD requestAssociations: 01 07 00 13 9F 00 00 03 77 (node ACK)
Z-Wave Debug RCVD requestAssociations: 01 0C 00 04 00 39 06 85 03 01 01 00 01 4F
Z-Wave Debug . . requestAssociations: node 057, group: 1, num associations: 1, max associations: 1, replies left: 0
Z-Wave Debug . . requestAssociations: node 057, group: 1, associations: [1]
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Debug SENT requestClockInfo2: 01 09 00 13 39 02 81 05 25 A0 DF
Z-Wave Debug RCVD requestClockInfo2: 01 07 00 13 A0 00 00 02 49 (node ACK)
Z-Wave Debug RCVD requestClockInfo: 01 0A 00 04 00 39 04 81 06 ED 06 A0
Z-Wave Debug . . requestClockInfo: node 057, 13:06 day-of-week 7
Z-Wave Debug SENT setClock: 01 0B 00 13 39 04 81 04 ED 06 25 A1 30
Z-Wave Debug RCVD setClock: 01 07 00 13 A1 00 00 02 48 (node ACK)
Z-Wave Syncing - synced server clock to module (13:06, Sunday)
Z-Wave Debug SENT requestBatteryLevel2: 01 09 00 13 39 02 80 02 25 A2 DB
Z-Wave Debug RCVD requestBatteryLevel2: 01 07 00 13 A2 00 00 03 4A (node ACK)
Z-Wave Debug RCVD requestReply1: 01 0A 00 04 00 39 04 22 01 01 02 EC (hex)
Action Group daylight brighten 1%
Z-Wave Debug timeout waiting for reply from module (retrying)
Z-Wave Debug SENT requestBatteryLevel2: 01 09 00 13 39 02 80 02 25 A3 DA
Z-Wave Debug RCVD requestBatteryLevel2: 01 07 00 13 A3 00 00 7E 36 (node ACK)
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 39 03 80 03 5A 11
Z-Wave Debug . . requestBatteryLevel: node 057, level 90
Z-Wave Syncing - retrieved battery level of 90%
Z-Wave Syncing - complete
Z-Wave Debug SENT requestHvacMode: 01 09 00 13 39 02 40 02 25 A4 1D
Z-Wave Debug RCVD requestHvacMode: 01 07 00 13 A4 00 00 03 4C (node ACK)
Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
Z-Wave sent "052 - Thermostat Living" mode status request
Z-Wave Debug RCVD setHvacMode: 01 09 00 04 00 39 03 40 03 01 8A
Z-Wave Debug . . setHvacMode: node 057, endpoint None, value 1
Z-Wave received "052 - Thermostat Living" mode is heat
Z-Wave Debug SENT requestTempStatus: 01 09 00 13 39 02 31 04 25 A5 6B
Z-Wave Debug terminatingSyncUI
Z-Wave Debug RCVD requestTempStatus: 01 07 00 13 A5 00 00 03 4D (node ACK)
Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
Z-Wave sent "052 - Thermostat Living" temperature status request
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 39 06 31 05 01 22 00 D2 0D
Z-Wave Debug . . requestVarSensorStatus: node 057, endpoint None, type 1, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 21.0 °C (float: 21.000000)
Z-Wave received "052 - Thermostat Living" temperature update to 21.0 °C
Z-Wave Debug SENT requestSetpointVal: 01 0A 00 13 39 03 43 02 01 25 A6 1F
Z-Wave Debug RCVD requestSetpointVal: 01 07 00 13 A6 00 00 02 4F (node ACK)
Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
Z-Wave sent "052 - Thermostat Living" heat setpoint status request
Z-Wave Debug RCVD requestSetpointVal: 01 0C 00 04 00 39 06 43 03 01 22 00 A0 0B
Z-Wave Debug . . requestSetpointVal: node 057, endpoint None, type 1, raw value 2200...
Z-Wave Debug . . requestSetpointVal: 16.0 °C (float: 16.000000)
Z-Wave received "052 - Thermostat Living" heat setpoint is 16.0 °C
Z-Wave Debug SENT requestSetpointVal: 01 0A 00 13 39 03 43 02 02 25 A7 1D
Z-Wave Debug RCVD requestSetpointVal: 01 07 00 13 A7 00 00 02 4E (node ACK)
Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
Z-Wave sent "052 - Thermostat Living" cool setpoint status request
Z-Wave Debug RCVD requestSetpointVal: 01 0C 00 04 00 39 06 43 03 00 22 00 00 AA
Z-Wave Debug . . requestSetpointVal: node 057, endpoint None, type 0, raw value 2200...
Z-Wave Debug . . requestSetpointVal: 0.0 °C (float: 0.000000)
Z-Wave Debug SENT requestAlarmSensorStatus: 01 0D 00 13 39 06 60 0D 01 02 71 04 25 A8 48
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 07 00 13 A8 00 00 03 40 (node ACK)
Z-Wave Debug waiting up to 3.0 seconds for module reply after sending request
TRV Error '57' in module 'zwave_command_class_multi_channel.py', method '_interpret_cmd_encap'
Failing statement [line 106]: 'source_end_point_ui = self.parent.node_to_indigo_device[node][source_end_point][ZW_INDIGO_DEVICE_NAME]'
Z-Wave Debug timeout waiting for module reply after sending request (not critical)
Z-Wave sent "052 - Multilevel Sensor" status request
Z-Wave Debug SENT setMultiLevelValue: 01 0E 00 13 04 07 60 0D 01 05 26 01 1B 25 A9 38
Z-Wave Debug RCVD setMultiLevelValue: 01 07 00 13 A9 00 00 02 40 (node ACK)
Z-Wave sent "015 - White" brighten to 27
Z-Wave Debug SENT setMultiLevelValue: 01 0E 00 13 04 07 60 0D 01 03 26 01 1B 25 AA 3D
Z-Wave Debug RCVD setMultiLevelValue: 01 07 00 13 AA 00 00 02 43 (node ACK)
Z-Wave sent "015 - Green" brighten to 27
Z-Wave Debug SENT setMultiLevelValue: 01 0E 00 13 04 07 60 0D 01 02 26 01 1B 25 AB 3D
Z-Wave Debug RCVD setMultiLevelValue: 01 07 00 13 AB 00 00 03 43 (node ACK)
Z-Wave sent "015 - Red" brighten to 27
Z-Wave Debug SENT setMultiLevelValue: 01 0E 00 13 04 07 60 0D 01 04 26 01 1B 25 AC 3C
Z-Wave Debug RCVD setMultiLevelValue: 01 07 00 13 AC 00 00 02 45 (node ACK)
Z-Wave sent "015 - Blue" brighten to 27
Z-Wave Debug SENT setMultiLevelValue: 01 0A 00 13 04 03 26 01 1B 25 AD 55
Z-Wave Debug RCVD setMultiLevelValue: 01 07 00 13 AD 00 00 02 44 (node ACK)
Z-Wave sent "015 - Composite" brighten to 27
Z-Wave Debug SENT setHeatSetpoint: 01 0C 00 13 39 05 43 01 01 01 08 25 AE 1D
Z-Wave Debug RCVD setHeatSetpoint: 01 07 00 13 AE 00 00 83 C6 (node ACK)
Z-Wave Debug . . setHeatSetpoint: requeuing 3 unsolicited packets
Z-Wave sent "052 - Thermostat Living" change heat setpoint to 8.0°
Z-Wave Debug RCVD multiEndPointPacket: 01 0D 00 04 00 04 07 60 0D 02 02 26 03 1B A6
Z-Wave Debug . . multiEndPointPacket: node 004, endPoint 2
Z-Wave Debug RCVD requestDimmerStatus: 01 09 00 04 00 04 03 26 03 1B FF
Z-Wave Debug . . requestDimmerStatus: node 004, endpoint 2, value 27
Z-Wave Debug RCVD multiEndPointPacket: 01 0D 00 04 00 04 07 60 0D 03 03 26 03 1B A6
Z-Wave Debug . . multiEndPointPacket: node 004, endPoint 3
Z-Wave Debug RCVD requestDimmerStatus: 01 09 00 04 00 04 03 26 03 1B FF
Z-Wave Debug . . requestDimmerStatus: node 004, endpoint 3, value 27
Z-Wave Debug RCVD multiEndPointPacket: 01 0D 00 04 00 04 07 60 0D 04 04 26 03 1B A6
Z-Wave Debug . . multiEndPointPacket: node 004, endPoint 4
Z-Wave Debug RCVD requestDimmerStatus: 01 09 00 04 00 04 03 26 03 1B FF
Z-Wave Debug . . requestDimmerStatus: node 004, endpoint 4, value 27
Z-Wave Debug RCVD multiEndPointPacket: 01 0D 00 04 00 04 07 60 0D 05 05 26 03 1B A6
Z-Wave Debug . . multiEndPointPacket: node 004, endPoint 5
Z-Wave Debug RCVD requestDimmerStatus: 01 09 00 04 00 04 03 26 03 1B FF
Z-Wave Debug . . requestDimmerStatus: node 004, endpoint 5, value 27
Z-Wave Debug RCVD dimmerSetLevel: 01 09 00 04 00 04 03 20 03 1B CD
Z-Wave Debug . . dimmerSetLevel: node 004, endpoint None, value 27
Z-Wave Debug RCVD multiEndPointPacket: 01 0D 00 04 00 04 07 60 0D 01 01 26 03 1B A6
Z-Wave Debug . . multiEndPointPacket: node 004, endPoint 1
Z-Wave Debug RCVD requestDimmerStatus: 01 09 00 04 00 04 03 26 03 1B FF
Z-Wave Debug . . requestDimmerStatus: node 004, endpoint 1, value 27
Z-Wave Debug RCVD requestReply1: 01 09 00 04 00 39 03 22 02 00 E8 (hex)
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 04 06 31 05 04 22 00 A3 44
Z-Wave Debug . . requestVarSensorStatus: node 004, endpoint None, type 4, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 16.3 W (float: 16.300000)
Z-Wave Debug received "015 - Composite" power load to 16.3 W

Thanks, we'll look into adding it.

matt (support) wrote:

Thanks, we'll look into adding it.

I any help need is required for testing, please let me know!


Sent from my iPad using Tapatalk