(EDGE Driver-Mc): Z-Wave Edge Drivers and others with FIBARO devices:

Devices & Integrations Community Created Device Types
, ,
779

@Mariano_Colmenarejo

The new driver is throwing errors

2023-02-05T03:39:16.368738009+00:00 ERROR Fibaro Smart Implant BETA Fibaro Smart Implant thread encountered error: [string “st/dispatcher.lua”]:233: Error encountered while processing event for <ZwaveDevice: 90395e70-07a9-4915-a570-941b5930c937 [42] (Fibaro Smart Implant)>:
> arg1: {args={precision=1, scale=“CELSIUS”, sensor_type=“TEMPERATURE”, sensor_value=32.7, size=2}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“REPORT”, dst_channels={0}, encap=“NONE”, payload=“\x01\x22\x01\x47”, src_channel=7, version=1}
> [string “init.lua”]:124: attempt to perform arithmetic on a nil value (field ‘internalTempOffset’)

image
image2406×848 254 KB

And now it is no longer working at all…

I’m guessing this is because the value of “internalTempOffset” and “externalTenpOffset” are 0 which is a correct default… but probably not handled as a special case …

Please advise

Out of curiosity - is it possible to select an older driver version or does the infrastructure only support use of the latest ?

780

I changed the value of “internalTempOffset” and “externalTempOffset” too .1 degree (minimum allowed)

The error is done and the sensor is reporting again properly (with the offset)

781

A post was split to a new topic: [Edge drivers] Issue with default values in profile’s preferences

782

@sflamm

Are you try to create a virtual child thermostat for external temperature probe from preferences?

It would be useful to know if thermostat works correctly, in case someone wants to use it

783

@Mariano_Colmenarejo

FYI - I had let the driver run for quite a while… and the nil values never updated (error never vanished). The error only vanished when I entered a value …

I have not tried the thermostat capability yet. However I am interested - as the device will control a heater which I want to enable when the temperature falls below a level and disable when it reaches a level.

Is there some documentation I can read on how to use the thermometer? I noticed there are quite a few use cases supported …

784

If you have any question, tell me

785

@Mariano_Colmenarejo i am using zwave switch mc to control a greenwave powernode single socket, all works well except energy consumption, the graph is not displaying as i would expect, the graph also needs more dates added to lower graph as it is difficult to distinguish which days are which, is this something you could possibly look into please

Would it be possible to add a energy consumption reset button ?

Screenshot_20230205_171733_SmartThings
Screenshot_20230205_171733_SmartThings720×1361 102 KB

786

Hi @fido

This function is performed by the app with the events received. It is outside the control of the driver

The energy rest function is performed with a command from a routine.
You can create a routine to reset it periodically or create a scene to reset manually

Screenshot_20230106-121919
Screenshot_20230106-1219191023×2048 190 KB

1 Like
787

You have done sooo many great drivers and options and variables Mariano i simply had no idea the reset could be done by those methods, thank you

1 Like
788

@Mariano_Colmenarejo

There appears to be a problem with rules… when you try to include the device in a rule… the range it allows to be input is in Celsius even though the units displaying on the device are in Fahrenheit.
How to address this?

allowed units in rule - celsius only
allowed units in rule - celsius only591×1280 47.3 KB

As a result - no rules work… for example it reports 90F and a rule that fires at 35C automatically happens…

789

It must be a problem with the app or with the assignment of temperature units in your smartthings account.

The displays used by the driver are the stock tmeperatureMeasurement.

You can go to my.smartthings.com in your account settings to see what units you have assigned to it, although I don’t think this will help.

I have seen other users talking about similar problems, but I don’t know the solution

790

@Mariano_Colmenarejo

I have also noticed that it is not always returning the external temp sensor values… If I restart it … it sometimes works and sometimes does not

Right now it is stuck

image
image1125×2436 100 KB

It has stopped reporting external temp

2023-02-06T22:48:35.465005218+00:00 TRACE Fibaro Smart Implant BETA Found ZwaveDispatcher handler in zwave_smart_implant
2023-02-06T22:48:35.474819968+00:00 PRINT Fibaro Smart Implant BETA << Temperature_report_handler >>
2023-02-06T22:48:35.475584051+00:00 INFO Fibaro Smart Implant BETA <ZwaveDevice: 90395e70-07a9-4915-a570-941b5930c937 [42] (Hot Tub Temperature)> emitting event: {“attribute_id”:“temperature”,“capability_id”:“temperatureMeasurement”,“component_id”:“main”,“state”:{“unit”:“C”,“value”:29.200000000000003}}
2023-02-06T22:48:35.490465301+00:00 DEBUG Fibaro Smart Implant BETA Fibaro Smart Implant device thread event handled
2023-02-06T22:48:35.493933426+00:00 TRACE Fibaro Smart Implant BETA Received event with handler unnamed
2023-02-06T22:48:35.494413968+00:00 INFO Fibaro Smart Implant BETA <ZwaveDevice: 90395e70-07a9-4915-a570-941b5930c937 [42] (Hot Tub Temperature)> received Z-Wave command: {args={precision=1, scale=“CELSIUS”, sensor_type=“TEMPERATURE”, sensor_value=0.0, size=2}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“REPORT”, dst_channels={0}, encap=“NONE”, payload=“\x01\x22\x00\x00”, src_channel=8, version=1}
2023-02-06T22:48:35.501879884+00:00 TRACE Fibaro Smart Implant BETA Found ZwaveDispatcher handler in zwave_smart_implant
2023-02-06T22:48:35.503775593+00:00 PRINT Fibaro Smart Implant BETA << Temperature_report_handler >>
2023-02-06T22:48:35.504620301+00:00 INFO Fibaro Smart Implant BETA <ZwaveDevice: 90395e70-07a9-4915-a570-941b5930c937 [42] (Hot Tub Temperature)> emitting event: {“attribute_id”:“temperature”,“capability_id”:“temperatureMeasurement”,“component_id”:“externalTemp1”,“state”:{“unit”:“C”,“value”:0.1}}
2023-02-06T22:48:35.512280343+00:00 DEBUG Fibaro Smart Implant BETA Fibaro Smart Implant device thread event handled
2023-02-06T22:49:35.471314725+00:00 TRACE Fibaro Smart Implant BETA Received event with handler unnamed
2023-02-06T22:49:35.471999600+00:00 INFO Fibaro Smart Implant BETA <ZwaveDevice: 90395e70-07a9-4915-a570-941b5930c937 [42] (Hot Tub Temperature)> received Z-Wave command: {args={precision=1, scale=“CELSIUS”, sensor_type=“TEMPERATURE”, sensor_value=29.1, size=2}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“REPORT”, dst_channels={0}, encap=“NONE”, payload=“\x01\x22\x01\x23”, src_channel=7, version=1}
2023-02-06T22:49:35.475069017+00:00 TRACE Fibaro Smart Implant BETA Found ZwaveDispatcher handler in zwave_smart_implant
2023-02-06T22:49:35.477027267+00:00 PRINT Fibaro Smart Implant BETA << Temperature_report_handler >>
2023-02-06T22:49:35.477743100+00:00 INFO Fibaro Smart Implant BETA <ZwaveDevice: 90395e70-07a9-4915-a570-941b5930c937 [42] (Hot Tub Temperature)> emitting event: {“attribute_id”:“temperature”,“capability_id”:“temperatureMeasurement”,“component_id”:“main”,“state”:{“unit”:“C”,“value”:29.200000000000003}}
2023-02-06T22:49:35.499577850+00:00 DEBUG Fibaro Smart Implant BETA Fibaro Smart Implant device thread event handled
2023-02-06T22:49:35.503040350+00:00 TRACE Fibaro Smart Implant BETA Received event with handler unnamed
2023-02-06T22:49:35.503514892+00:00 INFO Fibaro Smart Implant BETA <ZwaveDevice: 90395e70-07a9-4915-a570-941b5930c937 [42] (Hot Tub Temperature)> received Z-Wave command: {args={precision=1, scale=“CELSIUS”, sensor_type=“TEMPERATURE”, sensor_value=0.0, size=2}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“REPORT”, dst_channels={0}, encap=“NONE”, payload=“\x01\x22\x00\x00”, src_channel=8, version=1}
2023-02-06T22:49:35.513316517+00:00 TRACE Fibaro Smart Implant BETA Found ZwaveDispatcher handler in zwave_smart_implant
2023-02-06T22:49:35.513767100+00:00 PRINT Fibaro Smart Implant BETA << Temperature_report_handler >>
2023-02-06T22:49:35.514574517+00:00 INFO Fibaro Smart Implant BETA <ZwaveDevice: 90395e70-07a9-4915-a570-941b5930c937 [42] (Hot Tub Temperature)> emitting event: {“attribute_id”:“temperature”,“capability_id”:“temperatureMeasurement”,“component_id”:“externalTemp1”,“state”:{“unit”:“C”,“value”:0.1}}
2023-02-06T22:49:35.523065433+00:00 DEBUG Fibaro Smart Implant BETA Fibaro Smart Implant device thread event handled
2023-02-06T22:50:35.471376774+00:00 TRACE Fibaro Smart Implant BETA Received event with handler unnamed
2023-02-06T22:50:35.472080482+00:00 INFO Fibaro Smart Implant BETA <ZwaveDevice: 90395e70-07a9-4915-a570-941b5930c937 [42] (Hot Tub Temperature)> received Z-Wave command: {args={precision=1, scale=“CELSIUS”, sensor_type=“TEMPERATURE”, sensor_value=29.1, size=2}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“REPORT”, dst_channels={0}, encap=“NONE”, payload=“\x01\x22\x01\x23”, src_channel=7, version=1}
2023-02-06T22:50:35.475164440+00:00 TRACE Fibaro Smart Implant BETA Found ZwaveDispatcher handler in zwave_smart_implant
2023-02-06T22:50:35.477118732+00:00 PRINT Fibaro Smart Implant BETA << Temperature_report_handler >>
2023-02-06T22:50:35.477825024+00:00 INFO Fibaro Smart Implant BETA <ZwaveDevice: 90395e70-07a9-4915-a570-941b5930c937 [42] (Hot Tub Temperature)> emitting event: {“attribute_id”:“temperature”,“capability_id”:“temperatureMeasurement”,“component_id”:“main”,“state”:{“unit”:“C”,“value”:29.200000000000003}}
2023-02-06T22:50:35.497598774+00:00 DEBUG Fibaro Smart Implant BETA Fibaro Smart Implant device thread event handled
2023-02-06T22:50:35.498311565+00:00 TRACE Fibaro Smart Implant BETA Received event with handler unnamed
2023-02-06T22:50:35.498973732+00:00 INFO Fibaro Smart Implant BETA <ZwaveDevice: 90395e70-07a9-4915-a570-941b5930c937 [42] (Hot Tub Temperature)> received Z-Wave command: {args={precision=1, scale=“CELSIUS”, sensor_type=“TEMPERATURE”, sensor_value=0.0, size=2}, cmd_class=“SENSOR_MULTILEVEL”, cmd_id=“REPORT”, dst_channels={0}, encap=“NONE”, payload=“\x01\x22\x00\x00”, src_channel=8, version=1}
2023-02-06T22:50:35.515181732+00:00 TRACE Fibaro Smart Implant BETA Found ZwaveDispatcher handler in zwave_smart_implant
2023-02-06T22:50:35.515951399+00:00 PRINT Fibaro Smart Implant BETA << Temperature_report_handler >>
2023-02-06T22:50:35.516745065+00:00 INFO Fibaro Smart Implant BETA <ZwaveDevice: 90395e70-07a9-4915-a570-941b5930c937 [42] (Hot Tub Temperature)> emitting event: {“attribute_id”:“temperature”,“capability_id”:“temperatureMeasurement”,“component_id”:“externalTemp1”,“state”:{“unit”:“C”,“value”:0.1}}

791

image
image892×676 32.9 KB

image
image1337×743 13.6 KB

What shoudl I do?

792

The device send temperature data, it is sending 0.0°c.
The driver in this has nothing to do, it only processes what the device sends to it.

You may have a connection failure with the probe or internal device.

You can try a factory reset of the device

793

Report to smartthings

794

Now this is mysterious… I did nothing except login to the ide.SmartThing.com and then a while later the device units changed to Fahrenheit…

Perhaps after the rule was there for a while… it propagated the right units …

image
image1125×2436 192 KB

795

I think I isolated it to EMF interference… I moved the cable away from a Chinese made power supply and … works again.

Will test thoroughly … goes to show there are sharp differences in power supply shielding standards.

796

@Mariano_Colmenarejo

Does it make sense for you to log an error of the feature is enabled and the Temp returned is 0? (Since that it is impossible)

Would help debugging / discovering issues for folks.

Again - thanks for all the help.

I will test the thermostat once I am sure the basics are all working (would hate to send you in a wild goose chase … so I will do it when I am sure )

797

Hi @John_K

This DTH is for a motion sensor not for dual switch

Are you try to perform a factory reset of switch

RESET TO DEFAULT
To reset the module to the factory default settings, perform the following steps:

  1. Ensure that the wall switch is off.
  2. Press and hold the Program Switch. While holding the switch, turn on the wall
    switch.
  3. The LED on the module will begin flashing, indicating that it is no longer included
    in a Z-Wave network.
798

(NEW RELEASE) Version of the Edge Driver Z-Wave Window Treatment Mc

  • At the request of a user and tested by him on a Fibaro roller shutter 2 (FGR-222), a function has been added to establish random or fixed Preset Position from routines or scenes.
  • With the Random option it can be activated for when you are on vacation for example.
  • Added custom capability “Window Shade Preset Value” with the following values:

image
image510×1000 39.7 KB

  • Added 2 preferences to set the minimum and maximum value for Random values. The default values are:
    • Minimum: 40%
    • Maximum: 90%

image
image510×1000 58.6 KB

How does it work?:

  • When you press the “Preset Position” button or activate it with a routine or scene then the shade or blind will go to the value defined in the custom capability “Window Shade Preset Value”

image
image510×1000 44.1 KB

  • That value can be set manually, with routines or scenes.

  • When the Random value is established, each time a set Preset Position command arrives, a new value is calculated randomly between the minimum and maximum values established in preferences.

roller
roller508×1121 103 KB

  • The function is available for all profiles that have the windowShadePreset capability, except for manufacturers Aeotec, qubino, Iblinds and springs, which have specific subdrivers that handle this capability. If any user of these models needs it and is willing to try it and send logs, then could try adding it.
  • The new version will be updated automatically, it may be necessary to clear the cache of the app to see the new profile.

Driver version

───────────────────────────────────────────────────
 Name         Z-Wave Window Treatment Mc
 Version      2023-02-09T20:26:37.678973198
───────────────────────────────────────────────────
1 Like